From: Pavel Begunkov <asml.silence@gmail.com>
To: Caleb Sander Mateos <csander@purestorage.com>,
Jens Axboe <axboe@kernel.dk>
Cc: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] io_uring/net: use REQ_F_IMPORT_BUFFER for send_zc
Date: Tue, 25 Mar 2025 13:30:59 +0000 [thread overview]
Message-ID: <8b22d0df-f0ea-4667-b161-0ca42f03a232@gmail.com> (raw)
In-Reply-To: <20250324151123.726124-1-csander@purestorage.com>
On 3/24/25 15:11, Caleb Sander Mateos wrote:
> Instead of a bool field in struct io_sr_msg, use REQ_F_IMPORT_BUFFER to
> track whether io_send_zc() has already imported the buffer. This flag
> already serves a similar purpose for sendmsg_zc and {read,write}v_fixed.
>
> Signed-off-by: Caleb Sander Mateos <csander@purestorage.com>
> Suggested-by: Pavel Begunkov <asml.silence@gmail.com>
> ---
> include/linux/io_uring_types.h | 5 ++++-
> io_uring/net.c | 8 +++-----
> 2 files changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/include/linux/io_uring_types.h b/include/linux/io_uring_types.h
> index c17d2eedf478..699e2c0895ae 100644
> --- a/include/linux/io_uring_types.h
> +++ b/include/linux/io_uring_types.h
> @@ -583,11 +583,14 @@ enum {
> REQ_F_BUFFERS_COMMIT = IO_REQ_FLAG(REQ_F_BUFFERS_COMMIT_BIT),
> /* buf node is valid */
> REQ_F_BUF_NODE = IO_REQ_FLAG(REQ_F_BUF_NODE_BIT),
> /* request has read/write metadata assigned */
> REQ_F_HAS_METADATA = IO_REQ_FLAG(REQ_F_HAS_METADATA_BIT),
> - /* resolve padded iovec to registered buffers */
> + /*
> + * For vectored fixed buffers, resolve iovec to registered buffers.
> + * For SEND_ZC, whether to import buffers (i.e. the first issue).
> + */
> REQ_F_IMPORT_BUFFER = IO_REQ_FLAG(REQ_F_IMPORT_BUFFER_BIT),
> };
>
> typedef void (*io_req_tw_func_t)(struct io_kiocb *req, io_tw_token_t tw);
>
> diff --git a/io_uring/net.c b/io_uring/net.c
> index c87af980b98e..b221abe2600e 100644
> --- a/io_uring/net.c
> +++ b/io_uring/net.c
> @@ -75,11 +75,10 @@ struct io_sr_msg {
> unsigned nr_multishot_loops;
> u16 flags;
> /* initialised and used only by !msg send variants */
> u16 buf_group;
> bool retry;
> - bool imported; /* only for io_send_zc */
> void __user *msg_control;
> /* used only for send zerocopy */
> struct io_kiocb *notif;
> };
>
> @@ -1305,12 +1304,11 @@ int io_send_zc_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe)
> struct io_ring_ctx *ctx = req->ctx;
> struct io_kiocb *notif;
>
> zc->done_io = 0;
> zc->retry = false;
> - zc->imported = false;
> - req->flags |= REQ_F_POLL_NO_LAZY;
> + req->flags |= REQ_F_POLL_NO_LAZY | REQ_F_IMPORT_BUFFER;
This function is shared with sendmsg_zc, so if we set it here,
it'll trigger io_import_reg_vec() in io_sendmsg_zc() even for
non register buffer request.
>
> if (unlikely(READ_ONCE(sqe->__pad2[0]) || READ_ONCE(sqe->addr3)))
> return -EINVAL;
> /* we don't support IOSQE_CQE_SKIP_SUCCESS just yet */
> if (req->flags & REQ_F_CQE_SKIP)
> @@ -1447,12 +1445,12 @@ int io_send_zc(struct io_kiocb *req, unsigned int issue_flags)
> if (unlikely(!sock))
> return -ENOTSOCK;
> if (!test_bit(SOCK_SUPPORT_ZC, &sock->flags))
> return -EOPNOTSUPP;
>
> - if (!zc->imported) {
> - zc->imported = true;
> + if (req->flags & REQ_F_IMPORT_BUFFER) {
> + req->flags &= ~REQ_F_IMPORT_BUFFER;
> ret = io_send_zc_import(req, issue_flags);
> if (unlikely(ret))
> return ret;
> }
>
--
Pavel Begunkov
next prev parent reply other threads:[~2025-03-25 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 15:11 [PATCH] io_uring/net: use REQ_F_IMPORT_BUFFER for send_zc Caleb Sander Mateos
2025-03-25 13:30 ` Pavel Begunkov [this message]
2025-03-25 14:39 ` Caleb Sander Mateos
2025-03-26 9:52 ` Pavel Begunkov
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=8b22d0df-f0ea-4667-b161-0ca42f03a232@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@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