From: "Drew DeVault" <[email protected]>
To: "Pavel Begunkov" <[email protected]>, <[email protected]>
Cc: "noah" <[email protected]>, "Jens Axboe" <[email protected]>
Subject: Re: [PATCH] io_uring: add IORING_FEAT_FILES_SKIP feature flag
Date: Mon, 17 May 2021 19:25:14 -0400 [thread overview]
Message-ID: <CBFWQ64F7PWU.3EOQ3BQXFHZY7@taiga> (raw)
In-Reply-To: <[email protected]>
On Mon May 17, 2021 at 7:19 PM EDT, Pavel Begunkov wrote:
> On 5/17/21 8:22 PM, Drew DeVault wrote:
> > This signals that the kernel supports IORING_REGISTER_FILES_SKIP.
>
> #define IORING_FEAT_FILES_SKIP IORING_FEAT_NATIVE_WORKERS
>
> Maybe even solely in liburing. Any reason to have them separately?
> We keep compatibility anyway
What is the relationship between IORING_FEAT_NATIVE_WORKERS and
IORING_REGISTER_FILES_SKIP? Actually, what is NATIVE_WORKERS? The
documentation is sparse on this detail.
next prev parent reply other threads:[~2021-05-17 23:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 19:22 [PATCH] io_uring: add IORING_FEAT_FILES_SKIP feature flag Drew DeVault
2021-05-17 23:19 ` Pavel Begunkov
2021-05-17 23:25 ` Drew DeVault [this message]
2021-05-17 23:32 ` Pavel Begunkov
2021-05-17 23:33 ` Drew DeVault
2021-05-18 9:54 ` 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=CBFWQ64F7PWU.3EOQ3BQXFHZY7@taiga \
[email protected] \
[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