From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>,
[email protected], [email protected]
Subject: Re: [PATCH 5.11] io_uring: share fixed_file_refs b/w multiple rsrcs
Date: Wed, 18 Nov 2020 14:11:18 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <b5c57cd24e98a4fae8d9fd186983e053d9e52f37.1605729389.git.asml.silence@gmail.com>
On 11/18/20 12:57 PM, Pavel Begunkov wrote:
> Double fixed files for splice/tee are done in a nasty way, it takes 2
> ref_node refs, and during the second time it blindly overrides
> req->fixed_file_refs hoping that it haven't changed. That works because
> all that is done under iouring_lock in a single go but is error-prone.
>
> Bind everything explicitly to a single ref_node and take only one ref,
> with current ref_node ordering it's guaranteed to keep all files valid
> awhile the request is inflight.
>
> That's mainly a cleanup + preparation for generic resource handling,
> but also saves pcpu_ref get/put for splice/tee with 2 fixed files.
LGTM, applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-11-18 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[email protected]>
2020-11-18 19:57 ` [PATCH 5.11] io_uring: share fixed_file_refs b/w multiple rsrcs Pavel Begunkov
2020-11-18 21:11 ` 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] \
[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