From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [PATCH liburing 1/1] man: clarifications about direct open/accept
Date: Thu, 17 Mar 2022 20:40:57 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <4b6736f6da309756027b00f3b294417eb1832506.1647530578.git.asml.silence@gmail.com>
On Thu, 17 Mar 2022 15:23:34 +0000, Pavel Begunkov wrote:
> Direct open/accept replaces files for slots that are taken, so it's not
> necessary to use sparse file tables. Update on that, mention the
> replacing mechanism, and add a note about possible compitability issues
> for raw io_uring API users.
>
>
Applied, thanks!
[1/1] man: clarifications about direct open/accept
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-03-18 2:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 15:23 [PATCH liburing 1/1] man: clarifications about direct open/accept Pavel Begunkov
2022-03-18 2:40 ` 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=164757125702.111082.18333308307485650186.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