From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Subject: Re: [RFC v1 0/3] introduce io_uring querying
Date: Wed, 27 Aug 2025 09:35:17 -0600 [thread overview]
Message-ID: <271e1f16-3651-4bb7-a2e1-ef447d37ba8c@kernel.dk> (raw)
In-Reply-To: <cover.1756300192.git.asml.silence@gmail.com>
On 8/27/25 7:21 AM, Pavel Begunkov wrote:
> Introduce a versatile interface to query auxilary io_uring parameters.
> It will be used to close a couple of API gaps, but in this series can
> only tell what request and register opcodes, features and setup flags
> are available. It'll replace IORING_REGISTER_PROBE but with a much
> more convenient interface. Patch 3 for API description.
>
> Can be tested with:
>
> https://github.com/isilence/liburing.git io_uring/query-v1
>
> Note: RFC as I've got a last minute uapi adjustment I want to try.
Nice, was actually just dabbling in this yesterday, there are some
half assed patches here:
https://git.kernel.dk/cgit/linux/log/?h=io_uring-features
Your patch I had the identical one of, but moved it to a separate header
instead for adding more limits.
But I like your query style better than Yet Another
struct-with-resv-fields. I think that direction is good for sure.
--
Jens Axboe
next prev parent reply other threads:[~2025-08-27 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 13:21 [RFC v1 0/3] introduce io_uring querying Pavel Begunkov
2025-08-27 13:21 ` [RFC v1 1/3] io_uring: add helper for *REGISTER_SEND_MSG_RING Pavel Begunkov
2025-08-27 13:21 ` [RFC v1 2/3] io_uring: add macro for features and valid setup flags Pavel Begunkov
2025-08-27 13:21 ` [RFC v1 3/3] io_uring: introduce io_uring querying Pavel Begunkov
2025-08-27 18:04 ` Gabriel Krisman Bertazi
2025-08-27 19:45 ` Pavel Begunkov
2025-08-27 15:35 ` Jens Axboe [this message]
2025-08-27 16:51 ` [RFC v1 0/3] " Pavel Begunkov
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=271e1f16-3651-4bb7-a2e1-ef447d37ba8c@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@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