From: David Wei <dw@davidwei.uk>
To: io-uring@vger.kernel.org, netdev@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>, Pavel Begunkov <asml.silence@gmail.com>
Subject: [PATCH v4 0/8] io_uring zcrx ifq sharing
Date: Tue, 28 Oct 2025 10:46:31 -0700 [thread overview]
Message-ID: <20251028174639.1244592-1-dw@davidwei.uk> (raw)
Each ifq is bound to a HW RX queue with no way to share this across
multiple rings. It is possible that one ring will not be able to fully
saturate an entire HW RX queue due to userspace work. There are two ways
to handle more work:
1. Move work to other threads, but have to pay context switch overhead
and cold caches.
2. Add more rings with ifqs, but HW RX queues are a limited resource.
This patchset add a way for multiple rings to share the same underlying
src ifq that is bound to a HW RX queue. Rings with shared ifqs can issue
io_recvzc on zero copy sockets, just like the src ring.
Userspace are expected to create rings in separate threads and not
processes, such that all rings share the same address space. This is
because the sharing and synchronisation of refill rings is purely done
in userspace with no kernel involvement e.g. dst rings do not mmap the
refill ring. Also, userspace must distribute zero copy sockets steered
into the same HW RX queue across rings sharing the ifq.
v4:
- lock rings in seq instead of both
- drop export io_lock_two_rings()
- break circular ref between ifq and ring ctx
- remove io_shutdown_zcrx_ifqs()
- copy reg struct to user before writing ifq to ctx->zcrx_ctxs
v3:
- drop ifq->proxy
- use dec_and_test to clean up ifq
v2:
- split patch
David Wei (8):
io_uring/memmap: remove unneeded io_ring_ctx arg
io_uring/memmap: refactor io_free_region() to take user_struct param
io_uring/rsrc: refactor io_{un}account_mem() to take {user,mm}_struct
param
io_uring/zcrx: add io_zcrx_ifq arg to io_zcrx_free_area()
io_uring/zcrx: add user_struct and mm_struct to io_zcrx_ifq
io_uring/zcrx: move io_unregister_zcrx_ifqs() down
io_uring/zcrx: add refcount to ifq and remove ifq->ctx
io_uring/zcrx: share an ifq between rings
include/uapi/linux/io_uring.h | 4 +
io_uring/io_uring.c | 11 +--
io_uring/kbuf.c | 4 +-
io_uring/memmap.c | 20 ++---
io_uring/memmap.h | 2 +-
io_uring/register.c | 6 +-
io_uring/rsrc.c | 26 +++---
io_uring/rsrc.h | 6 +-
io_uring/zcrx.c | 149 ++++++++++++++++++++++++----------
io_uring/zcrx.h | 8 +-
10 files changed, 149 insertions(+), 87 deletions(-)
--
2.47.3
next reply other threads:[~2025-10-28 17:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 17:46 David Wei [this message]
2025-10-28 17:46 ` [PATCH v4 1/8] io_uring/memmap: remove unneeded io_ring_ctx arg David Wei
2025-10-28 17:46 ` [PATCH v4 2/8] io_uring/memmap: refactor io_free_region() to take user_struct param David Wei
2025-10-28 17:46 ` [PATCH v4 3/8] io_uring/rsrc: refactor io_{un}account_mem() to take {user,mm}_struct param David Wei
2025-10-28 17:46 ` [PATCH v4 4/8] io_uring/zcrx: add io_zcrx_ifq arg to io_zcrx_free_area() David Wei
2025-10-28 17:46 ` [PATCH v4 5/8] io_uring/zcrx: add user_struct and mm_struct to io_zcrx_ifq David Wei
2025-10-28 17:46 ` [PATCH v4 6/8] io_uring/zcrx: move io_unregister_zcrx_ifqs() down David Wei
2025-10-28 17:46 ` [PATCH v4 7/8] io_uring/zcrx: add refcount to ifq and remove ifq->ctx David Wei
2025-10-29 15:22 ` Pavel Begunkov
2025-10-29 16:16 ` Pavel Begunkov
2025-10-30 15:24 ` Pavel Begunkov
2025-10-28 17:46 ` [PATCH v4 8/8] io_uring/zcrx: share an ifq between rings 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=20251028174639.1244592-1-dw@davidwei.uk \
--to=dw@davidwei.uk \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--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