From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH liburing 1/1] io_uring: update buffer update feature testing
Date: Thu, 26 Aug 2021 08:41:13 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <de5fd2626bd4eabd0eec3eb8310888b4eb1a2539.1629976377.git.asml.silence@gmail.com>
On 8/26/21 5:13 AM, Pavel Begunkov wrote:
> IORING_FEAT_RSRC_TAGS came late, and it's the best way to check if a
> ring supports resource (i.e. buffer or file) tagging and dynamic buffer
> updates.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-08-26 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 11:13 [PATCH liburing 1/1] io_uring: update buffer update feature testing Pavel Begunkov
2021-08-26 14: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 \
[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