From: Jens Axboe <axboe@kernel.dk>
To: David Wei <dw@davidwei.uk>,
io-uring@vger.kernel.org, netdev@vger.kernel.org
Cc: Pavel Begunkov <asml.silence@gmail.com>
Subject: Re: [PATCH v2 3/5] io_uring/zcrx: share an ifq between rings
Date: Sat, 25 Oct 2025 17:41:15 -0600 [thread overview]
Message-ID: <f1fa5543-c637-435d-a189-5d942b1c7ebc@kernel.dk> (raw)
In-Reply-To: <20251025191504.3024224-4-dw@davidwei.uk>
On 10/25/25 1:15 PM, David Wei wrote:
> @@ -541,6 +541,74 @@ struct io_mapped_region *io_zcrx_get_region(struct io_ring_ctx *ctx,
> return ifq ? &ifq->region : NULL;
> }
>
> +static int io_proxy_zcrx_ifq(struct io_ring_ctx *ctx,
> + struct io_uring_zcrx_ifq_reg __user *arg,
> + struct io_uring_zcrx_ifq_reg *reg)
> +{
> + struct io_zcrx_ifq *ifq, *src_ifq;
> + struct io_ring_ctx *src_ctx;
> + 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 || src_ifq->proxy)
> + goto err_unlock;
> +
> + percpu_ref_get(&src_ctx->refs);
> + refcount_inc(&src_ifq->refs);
> +
> + ifq = kzalloc(sizeof(*ifq), GFP_KERNEL);
This still needs a:
if (!ifq)
handle error
addition, like mentioned for v1. Would probably make sense to just
assume that everything is honky dory and allocate it upfront/early, and
just kill it in the error path. Would probably help remove one of the
goto labels.
> + ifq->proxy = src_ifq;
For this, since the ifq is shared and reference counted, why don't they
just point at the same memory here? Would avoid having this ->proxy
thing and just skipping to that in other spots where the actual
io_zcrx_ifq is required?
--
Jens Axboe
next prev parent reply other threads:[~2025-10-25 23:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 19:14 [PATCH v2 0/5] io_uring zcrx ifq sharing David Wei
2025-10-25 19:15 ` [PATCH v2 1/5] io_uring/rsrc: rename and export io_lock_two_rings() David Wei
2025-10-25 19:15 ` [PATCH v2 2/5] io_uring/zcrx: add refcount to struct io_zcrx_ifq David Wei
2025-10-25 23:37 ` Jens Axboe
2025-10-26 4:10 ` David Wei
2025-10-25 19:15 ` [PATCH v2 3/5] io_uring/zcrx: share an ifq between rings David Wei
2025-10-25 23:41 ` Jens Axboe [this message]
2025-10-26 4:12 ` David Wei
2025-10-26 13:16 ` Jens Axboe
2025-10-26 13:43 ` Jens Axboe
2025-10-26 15:06 ` David Wei
2025-10-25 19:15 ` [PATCH v2 4/5] io_uring/zcrx: redirect io_recvzc on proxy ifq to src ifq David Wei
2025-10-25 19:15 ` [PATCH v2 5/5] io_uring/zcrx: free proxy ifqs David Wei
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=f1fa5543-c637-435d-a189-5d942b1c7ebc@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--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