From: Pavel Begunkov <asml.silence@gmail.com>
To: David Wei <dw@davidwei.uk>,
io-uring@vger.kernel.org, netdev@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH v3 3/3] io_uring/zcrx: share an ifq between rings
Date: Tue, 28 Oct 2025 15:22:13 +0000 [thread overview]
Message-ID: <4efc2d91-49df-4606-894e-92ac89c3ae9c@gmail.com> (raw)
In-Reply-To: <acb27d6b-5602-41c8-8fe5-4e88827713a4@davidwei.uk>
On 10/28/25 14:55, David Wei wrote:
> On 2025-10-27 03:20, Pavel Begunkov wrote:
>> On 10/26/25 17:34, David Wei wrote:
>>> Add a way to share an ifq from a src ring that is real i.e. bound to a
>>> HW RX queue with other rings. This is done by passing a new flag
>>> IORING_ZCRX_IFQ_REG_SHARE in the registration struct
>>> io_uring_zcrx_ifq_reg, alongside the fd of the src ring and the ifq id
>>> to be shared.
>>>
>>> To prevent the src ring or ifq from being cleaned up or freed while
>>> there are still shared ifqs, take the appropriate refs on the src ring
>>> (ctx->refs) and src ifq (ifq->refs).
>>>
>>> Signed-off-by: David Wei <dw@davidwei.uk>
>>> ---
>>> include/uapi/linux/io_uring.h | 4 ++
>>> io_uring/zcrx.c | 74 ++++++++++++++++++++++++++++++++++-
>>> 2 files changed, 76 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/io_uring/zcrx.c b/io_uring/zcrx.c
>>> index 569cc0338acb..7418c959390a 100644
>>> --- a/io_uring/zcrx.c
>>> +++ b/io_uring/zcrx.c
> [...]
>>> @@ -541,6 +541,67 @@ struct io_mapped_region *io_zcrx_get_region(struct io_ring_ctx *ctx,
>>> return ifq ? &ifq->region : NULL;
>>> }
>>> +static int io_share_zcrx_ifq(struct io_ring_ctx *ctx,
>>> + struct io_uring_zcrx_ifq_reg __user *arg,
>>> + struct io_uring_zcrx_ifq_reg *reg)
>>> +{
>>> + struct io_ring_ctx *src_ctx;
>>> + struct io_zcrx_ifq *src_ifq;
>>> + struct file *file;
>>> + int src_fd, ret;
>>> + u32 src_id, id;
>>> +
>>> + src_fd = reg->if_idx;
>>> + src_id = reg->if_rxq;
>>> +
>>> + file = io_uring_register_get_file(src_fd, false);
>>> + if (IS_ERR(file))
>>> + return PTR_ERR(file);
>>> +
>>> + src_ctx = file->private_data;
>>> + if (src_ctx == ctx)
>>> + return -EBADFD;
>>> +
>>> + mutex_unlock(&ctx->uring_lock);
>>> + io_lock_two_rings(ctx, src_ctx);
>>> +
>>> + ret = -EINVAL;
>>> + src_ifq = xa_load(&src_ctx->zcrx_ctxs, src_id);
>>> + if (!src_ifq)
>>> + goto err_unlock;
>>> +
>>> + percpu_ref_get(&src_ctx->refs);
>>> + refcount_inc(&src_ifq->refs);
>>> +
>>> + scoped_guard(mutex, &ctx->mmap_lock) {
>>> + ret = xa_alloc(&ctx->zcrx_ctxs, &id, NULL, xa_limit_31b, GFP_KERNEL);
>>> + if (ret)
>>> + goto err_unlock;
>>> +
>>> + ret = -ENOMEM;
>>> + if (xa_store(&ctx->zcrx_ctxs, id, src_ifq, GFP_KERNEL)) {
>>> + xa_erase(&ctx->zcrx_ctxs, id);
>>> + goto err_unlock;
>>> + }
>>
>> It's just xa_alloc(..., src_ifq, ...);
>>
>>> + }
>>> +
>>> + reg->zcrx_id = id;
>>> + if (copy_to_user(arg, reg, sizeof(*reg))) {
>>> + ret = -EFAULT;
>>> + goto err;
>>> + }
>>
>> Better to do that before publishing zcrx into ctx->zcrx_ctxs
>
> I can only do one of the two suggestions above. No valid id until
> xa_alloc() returns, so I either split xa_alloc()/xa_store() with
> copy_to_user() in between, or I do a single xa_alloc() and
> copy_to_user() after.
Makes sense, I'd do splitting then, at least this way it's
not exposing it to the user space for a brief moment.
--
Pavel Begunkov
prev parent reply other threads:[~2025-10-28 15:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 17:34 [PATCH v3 0/3] io_uring zcrx ifq sharing David Wei
2025-10-26 17:34 ` [PATCH v3 1/3] io_uring/rsrc: rename and export io_lock_two_rings() David Wei
2025-10-27 10:04 ` Pavel Begunkov
2025-10-28 14:54 ` David Wei
2025-10-28 15:19 ` Pavel Begunkov
2025-10-26 17:34 ` [PATCH v3 2/3] io_uring/zcrx: add refcount to struct io_zcrx_ifq David Wei
2025-10-26 17:34 ` [PATCH v3 3/3] io_uring/zcrx: share an ifq between rings David Wei
2025-10-27 10:20 ` Pavel Begunkov
2025-10-27 11:47 ` Pavel Begunkov
2025-10-27 15:10 ` David Wei
2025-10-28 14:55 ` David Wei
2025-10-28 15:22 ` Pavel Begunkov [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=4efc2d91-49df-4606-894e-92ac89c3ae9c@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=dw@davidwei.uk \
--cc=io-uring@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).