From: Jens Axboe <axboe@kernel.dk>
To: Nathan Chancellor <nathan@kernel.org>
Cc: io-uring@vger.kernel.org, csander@purestorage.com,
Keith Busch <kbusch@meta.com>, Keith Busch <kbusch@kernel.org>,
llvm@lists.linux.dev
Subject: Re: [PATCHv6] io_uring: add support for IORING_SETUP_SQE_MIXED
Date: Wed, 22 Oct 2025 07:34:22 -0600 [thread overview]
Message-ID: <4ea25979-4fc2-4db7-8656-6c262af2cbee@kernel.dk> (raw)
In-Reply-To: <20251022120030.GA148714@ax162>
On 10/22/25 6:00 AM, Nathan Chancellor wrote:
> On Tue, Oct 21, 2025 at 04:02:28PM -0600, Jens Axboe wrote:
>>
>> On Thu, 16 Oct 2025 11:09:38 -0700, Keith Busch wrote:
>>> Normal rings support 64b SQEs for posting submissions, while certain
>>> features require the ring to be configured with IORING_SETUP_SQE128, as
>>> they need to convey more information per submission. This, in turn,
>>> makes ALL the SQEs be 128b in size. This is somewhat wasteful and
>>> inefficient, particularly when only certain SQEs need to be of the
>>> bigger variant.
>>>
>>> [...]
>>
>> Applied, thanks!
>>
>> [1/1] io_uring: add support for IORING_SETUP_SQE_MIXED
>> commit: 31dc41afdef21f264364288a30013b538c46152e
>
> This needs a pretty obvious fix up as clang points out:
>
> io_uring/fdinfo.c:103:22: error: variable 'sqe' is uninitialized when used here [-Werror,-Wuninitialized]
> 103 | opcode = READ_ONCE(sqe->opcode);
> | ^~~
>
> I would have sent a formal patch but since it is at the top, I figured
> it would get squashed anyways.
Indeed - I'll fold this in. Keith, can you add an fdinfo test case for
mixed as well?
--
Jens Axboe
next prev parent reply other threads:[~2025-10-22 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 18:09 [PATCHv6] io_uring: add support for IORING_SETUP_SQE_MIXED Keith Busch
2025-10-21 22:02 ` Jens Axboe
2025-10-22 12:00 ` Nathan Chancellor
2025-10-22 13:34 ` Jens Axboe [this message]
2025-10-22 13:53 ` Keith Busch
2025-10-22 13:56 ` Jens Axboe
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=4ea25979-4fc2-4db7-8656-6c262af2cbee@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=llvm@lists.linux.dev \
--cc=nathan@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