From: Jens Axboe <axboe@kernel.dk>
To: Caleb Sander Mateos <csander@purestorage.com>
Cc: Keith Busch <kbusch@meta.com>,
io-uring@vger.kernel.org, ming.lei@redhat.com,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv3 1/1] io_uring: add support for IORING_SETUP_SQE_MIXED
Date: Thu, 25 Sep 2025 12:44:18 -0600 [thread overview]
Message-ID: <b11faaad-3142-4db9-b3e8-55b8785264b9@kernel.dk> (raw)
In-Reply-To: <CADUfDZpL2r2nhVDGZF07pDwNw-agxogo3hz2VDvJNvZK+h_Uug@mail.gmail.com>
On 9/25/25 12:21 PM, Caleb Sander Mateos wrote:
>>> +int io_uring_cmd128_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe)
>>> +{
>>> + if (!(req->ctx->flags & IORING_SETUP_SQE_MIXED))
>>> + return -EINVAL;
>>> + return io_uring_cmd_prep(req, sqe);
>>> +}
>>
>> Why isn't this just allowed for SQE128 as well? There should be no
>> reason to disallow explicitly 128b sqe commands in SQE128 mode, they
>> should work for any mode that supports 128b SQEs which is either
>> SQE_MIXED or SQE128?
>
> Not to mention, the check in io_init_req() should already have
> rejected a 128-byte operation on a non-IORING_SETUP_SQE_MIXED
> io_ring_ctx.
Yes good point, it should all be caught there, no need for any per-op
checking (or the separate prep handler).
--
Jens Axboe
next prev parent reply other threads:[~2025-09-25 18:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 15:12 [PATCHv3 0/3] Keith Busch
2025-09-24 15:12 ` [PATCHv3 1/3] Add support IORING_SETUP_SQE_MIXED Keith Busch
2025-09-24 20:20 ` Caleb Sander Mateos
2025-09-24 20:30 ` Keith Busch
2025-09-24 20:37 ` Caleb Sander Mateos
2025-09-24 15:12 ` [PATCHv3 1/1] io_uring: add support for IORING_SETUP_SQE_MIXED Keith Busch
2025-09-25 15:03 ` Jens Axboe
2025-09-25 18:21 ` Caleb Sander Mateos
2025-09-25 18:44 ` Jens Axboe [this message]
2025-09-24 15:12 ` [PATCHv3 2/3] Add nop testing " Keith Busch
2025-09-24 15:12 ` [PATCHv3 3/3] Add mixed sqe test for uring commands Keith Busch
2025-09-24 15:54 ` [PATCHv3 0/3] io_uring: mixed submission queue size support 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=b11faaad-3142-4db9-b3e8-55b8785264b9@kernel.dk \
--to=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=io-uring@vger.kernel.org \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=ming.lei@redhat.com \
/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