From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [PATCH 1/1] io_uring: rearrange opdef flags by use pattern
Date: Wed, 26 Feb 2025 16:41:32 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <ef03b6ce4a0c2a5234cd4037fa07e9e4902dcc9e.1740602793.git.asml.silence@gmail.com>
On Wed, 26 Feb 2025 20:46:34 +0000, Pavel Begunkov wrote:
> Keep all flags that we use in the generic req init path close together.
> That saves a load for x86 because apparently some compilers prefer
> reading single bytes.
>
>
Applied, thanks!
[1/1] io_uring: rearrange opdef flags by use pattern
commit: 047fa0ba8f1bed6b1c5d88e31c4fd187de16dbc1
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-02-26 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 20:46 [PATCH 1/1] io_uring: rearrange opdef flags by use pattern Pavel Begunkov
2025-02-26 23:41 ` Jens Axboe [this message]
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=174061329293.2398862.7714536188928920487.b4-ty@kernel.dk \
[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