From: Keith Busch <kbusch@meta.com>
To: <io-uring@vger.kernel.org>, <axboe@kernel.dk>, <csander@purestorage.com>
Cc: Keith Busch <kbusch@kernel.org>
Subject: [PATCHv5 0/1] io_uring: mixed submission queue entries sizes
Date: Mon, 13 Oct 2025 11:00:06 -0700 [thread overview]
Message-ID: <20251013180011.134131-2-kbusch@meta.com> (raw)
In-Reply-To: <20251013180011.134131-1-kbusch@meta.com>
From: Keith Busch <kbusch@kernel.org>
Resending to the correct mailing list.
Changes from v3:
- Allowed 128b opcodes on both big and mixed SQ's
- Added additional comments for clarity
- Commit message fixups
- Moved the uring specific entry size fucntion to the uring code.
Keith Busch (1):
io_uring: add support for IORING_SETUP_SQE_MIXED
include/uapi/linux/io_uring.h | 8 ++++++++
io_uring/fdinfo.c | 34 +++++++++++++++++++++++++++-------
io_uring/io_uring.c | 35 +++++++++++++++++++++++++++++++----
io_uring/io_uring.h | 14 ++------------
io_uring/opdef.c | 26 ++++++++++++++++++++++++++
io_uring/opdef.h | 2 ++
io_uring/register.c | 2 +-
io_uring/uring_cmd.c | 17 +++++++++++++++--
8 files changed, 112 insertions(+), 26 deletions(-)
--
2.47.3
next prev parent reply other threads:[~2025-10-13 18:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 18:00 [PATCHv5 0/4] liburing: support for mix sized sqe's Keith Busch
2025-10-13 18:00 ` Keith Busch [this message]
2025-10-13 18:00 ` [PATCHv5 1/1] io_uring: add support for IORING_SETUP_SQE_MIXED Keith Busch
2025-10-14 22:33 ` Caleb Sander Mateos
2025-10-15 2:03 ` Keith Busch
2025-10-16 18:06 ` Keith Busch
2025-10-13 18:00 ` [PATCHv5 1/4] liburing: provide uring_cmd prep function Keith Busch
2025-10-19 16:24 ` Caleb Sander Mateos
2025-10-21 16:45 ` Keith Busch
2025-10-13 18:00 ` [PATCHv5 2/4] Add support IORING_SETUP_SQE_MIXED Keith Busch
2025-10-13 18:00 ` [PATCHv5 3/4] Add nop testing for IORING_SETUP_SQE_MIXED Keith Busch
2025-10-13 18:00 ` [PATCHv5 4/4] Add mixed sqe test for uring commands Keith Busch
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=20251013180011.134131-2-kbusch@meta.com \
--to=kbusch@meta.com \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=io-uring@vger.kernel.org \
--cc=kbusch@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