From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Subject: Re: [PATCH for-next 0/4] io_uring/zc fix and improvements
Date: Mon, 25 Jul 2022 09:49:04 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Mon, 25 Jul 2022 10:52:02 +0100, Pavel Begunkov wrote:
> It mainly fixes net/zc memory accounting error handling and then makes
> it more consistent with registered buffers mem accounting.
>
> Pavel Begunkov (4):
> io_uring/net: improve io_get_notif_slot types
> io_uring/net: checks errors of zc mem accounting
> io_uring/net: make page accounting more consistent
> io_uring/net: use unsigned for flags
>
> [...]
Applied, thanks!
[1/4] io_uring/net: improve io_get_notif_slot types
commit: cb309ae49da7a7c28f0051deea13970291134fac
[2/4] io_uring/net: checks errors of zc mem accounting
commit: 2e32ba5607ee2b668baa8831dd74f7cc867a1f7e
[3/4] io_uring/net: make page accounting more consistent
commit: 6a9ce66f4d0872861e0bbc67eee6ce5dca5dd886
[4/4] io_uring/net: use unsigned for flags
commit: 293402e564a7391f38541c7694e736f5fde20aea
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-07-25 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 9:52 [PATCH for-next 0/4] io_uring/zc fix and improvements Pavel Begunkov
2022-07-25 9:52 ` [PATCH for-next 1/4] io_uring/net: improve io_get_notif_slot types Pavel Begunkov
2022-07-25 9:52 ` [PATCH for-next 2/4] io_uring/net: checks errors of zc mem accounting Pavel Begunkov
2022-07-25 9:52 ` [PATCH for-next 3/4] io_uring/net: make page accounting more consistent Pavel Begunkov
2022-07-25 9:52 ` [PATCH for-next 4/4] io_uring/net: use unsigned for flags Pavel Begunkov
2022-07-25 15:49 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=165876414435.1092384.12025756909582912011.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox