From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH liburing] man/io_uring_enter.2: add notes about direct open/accept
Date: Tue, 31 Aug 2021 14:04:02 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <e4b7c0f9b585307ac542470c535ef54e419157e0.1630439510.git.asml.silence@gmail.com>
On 8/31/21 1:52 PM, Pavel Begunkov wrote:
> Add a few lines describing openat/openat2/accept bypassing normal file
> tables and installing files right into the fixed file table.
>
> Signed-off-by: Pavel Begunkov <[email protected]>
> ---
> man/io_uring_enter.2 | 36 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
>
> diff --git a/man/io_uring_enter.2 b/man/io_uring_enter.2
> index 9ccedef..52a5e13 100644
> --- a/man/io_uring_enter.2
> +++ b/man/io_uring_enter.2
> @@ -511,6 +511,18 @@ field. See also
> .BR accept4(2)
> for the general description of the related system call. Available since 5.5.
>
> +If the
> +.I file_index
> +field is set to a non-negative number, the file won't be installed into the
> +normal file table as usual but will be placed into the fixed file table at index
> +.I file_index - 1.
> +In this case, instead of returning a file descriptor, the result will contain
> +0 on success or an error. If there is already a file registered at this index,
I don't think non-negative is correct, it has to be set to a positive
number. non-negative would include 0, which isn't correct.
Should also include a note on if these types of file are used, they
won't work in anything but io_uring. That's obvious to us, but should be
noted that they then only live within the realm of the ring itself, not
the system as a whole.
--
Jens Axboe
next prev parent reply other threads:[~2021-08-31 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 19:52 [PATCH liburing] man/io_uring_enter.2: add notes about direct open/accept Pavel Begunkov
2021-08-31 20:04 ` Jens Axboe [this message]
2021-08-31 20:07 ` 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 \
[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