From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, Pavel Begunkov <asml.silence@gmail.com>
Cc: Dylan Yudaken <dyudaken@gmail.com>
Subject: Re: [PATCH 0/3] deduplicate send and senmsg zc issue handlers
Date: Mon, 23 Feb 2026 06:47:17 -0700 [thread overview]
Message-ID: <177185443745.636584.13271111585602295059.b4-ty@kernel.dk> (raw)
In-Reply-To: <cover.1771240334.git.asml.silence@gmail.com>
On Mon, 16 Feb 2026 11:45:52 +0000, Pavel Begunkov wrote:
> There is a bunch of code duplicated between send_zc and senmsg_zc,
> let's consolidate the functions.
>
> Note: it's based on top of Dylan's patch removing buf/len accounting.
>
> Pavel Begunkov (3):
> io_uring/zctx: rename flags var for more clarity
> io_uring/zctx: move vec regbuf import into io_send_zc_import
> io_uring/zctx: unify zerocopy issue variants
>
> [...]
Applied, thanks!
[1/3] io_uring/zctx: rename flags var for more clarity
commit: 7e401209e5c2c88293798ba8275e117b994669ea
[2/3] io_uring/zctx: move vec regbuf import into io_send_zc_import
commit: 694fd02b36056400ab4090a741c2b52c14d167c0
[3/3] io_uring/zctx: unify zerocopy issue variants
commit: 80435d1743ac33199debcddd4df511ada79bbe8c
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2026-02-23 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 11:45 [PATCH 0/3] deduplicate send and senmsg zc issue handlers Pavel Begunkov
2026-02-16 11:45 ` [PATCH 1/3] io_uring/zctx: rename flags var for more clarity Pavel Begunkov
2026-02-16 11:45 ` [PATCH 2/3] io_uring/zctx: move vec regbuf import into io_send_zc_import Pavel Begunkov
2026-02-16 11:45 ` [PATCH 3/3] io_uring/zctx: unify zerocopy issue variants Pavel Begunkov
2026-02-16 16:35 ` [PATCH 0/3] deduplicate send and senmsg zc issue handlers Jens Axboe
2026-02-23 13:47 ` 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=177185443745.636584.13271111585602295059.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=dyudaken@gmail.com \
--cc=io-uring@vger.kernel.org \
/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