From: Ming Lei <[email protected]>
To: Jens Axboe <[email protected]>
Cc: io-uring <[email protected]>,
Pavel Begunkov <[email protected]>,
[email protected]
Subject: Re: [PATCH RFC] io_uring: extend io_uring_sqe flags bits
Date: Fri, 1 Nov 2024 10:12:25 +0800 [thread overview]
Message-ID: <ZyQ5CcwfLhaASvMz@fedora> (raw)
In-Reply-To: <[email protected]>
On Thu, Oct 31, 2024 at 03:22:18PM -0600, Jens Axboe wrote:
> In hindsight everything is clearer, but it probably should've been known
> that 8 bits of ->flags would run out sooner than later. Rather than
> gobble up the last bit for a random use case, add a bit that controls
> whether or not ->personality is used as a flags2 argument. If that is
> the case, then there's a new IOSQE2_PERSONALITY flag that tells io_uring
> which personality field to read.
>
> While this isn't the prettiest, it does allow extending with 15 extra
> flags, and retains being able to use personality with any kind of
> command. The exception is uring cmd, where personality2 will overlap
> with the space set aside for SQE128. If they really need that, then that
The space is the 1st `short` for uring_cmd, instead of SQE128 only.
Also it is overlapped with ->optval and ->addr3, so just wondering why not
use ->__pad2?
Another ways is to use __pad2 for sqe2_flags for non-uring_cmd, and for
uring_cmd, use its top 16 as sqe2_flags, this way does work, but it is
just a bit ugly to use.
Thanks,
Ming
next prev parent reply other threads:[~2024-11-01 2:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 21:22 [PATCH RFC] io_uring: extend io_uring_sqe flags bits Jens Axboe
2024-11-01 2:12 ` Ming Lei [this message]
2024-11-01 2:42 ` Ming Lei
2024-11-01 13:59 ` Jens Axboe
2024-11-01 14:34 ` Ming Lei
2024-11-01 14:42 ` Jens Axboe
2024-11-01 15:01 ` Ming Lei
2024-11-01 15:04 ` Jens Axboe
2024-11-01 16:55 ` Pavel Begunkov
2024-11-01 16:58 ` Jens Axboe
2024-11-01 13:58 ` Jens Axboe
2024-11-01 16:59 ` Pavel Begunkov
2024-11-01 17:05 ` 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=ZyQ5CcwfLhaASvMz@fedora \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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