From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Subject: Re: [PATCH 5.19] io_uring: keep sendrecv flags in ioprio
Date: Thu, 30 Jun 2022 08:56:38 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <06ab196021be1b5463879f637e080ac2c67ec91e.1656591720.git.asml.silence@gmail.com>
On Thu, 30 Jun 2022 13:25:57 +0100, Pavel Begunkov wrote:
> We waste a u64 SQE field for flags even though we don't need as many
> bits and it can be used for something more useful later. Store io_uring
> specific send/recv flags in sqe->prio instead of ->addr2.
>
>
Applied, thanks!
[1/1] io_uring: keep sendrecv flags in ioprio
commit: 29c1ac230e6056b26846c66881802b581a78ad72
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-06-30 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 12:25 [PATCH 5.19] io_uring: keep sendrecv flags in ioprio Pavel Begunkov
2022-06-30 14:56 ` 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=165660099886.535553.15967708433061545664.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