From: Jens Axboe <axboe@kernel.dk>
To: Xiaoguang Wang <xiaoguang.wang@linux.alibaba.com>,
io-uring@vger.kernel.org
Cc: joseph.qi@linux.alibaba.com
Subject: Re: [PATCH] io_uring: don't hold fixed_file_data's lock when registering files
Date: Wed, 2 Sep 2020 08:13:44 -0600 [thread overview]
Message-ID: <a8417eac-3349-cc82-7f13-cb00fa34617b@kernel.dk> (raw)
In-Reply-To: <20200902113256.6620-1-xiaoguang.wang@linux.alibaba.com>
On 9/2/20 5:32 AM, Xiaoguang Wang wrote:
> While registering new files by IORING_REGISTER_FILES, there're not
> valid fixed_file_ref_node at the moment, so it's unnecessary to hold
> fixed_file_data's lock when registering files.
Even if that were the case (I haven't looked too closely at it yet),
it would a) need a big comment explaining why, and b) some justification
on why this would be a change we'd want to make.
On b, are you seeing any tangible differences with this?
--
Jens Axboe
next prev parent reply other threads:[~2020-09-02 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 11:32 [PATCH] io_uring: don't hold fixed_file_data's lock when registering files Xiaoguang Wang
2020-09-02 14:13 ` Jens Axboe [this message]
2020-09-03 4:35 ` Xiaoguang Wang
2020-09-03 11:40 ` Jens Axboe
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=a8417eac-3349-cc82-7f13-cb00fa34617b@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=xiaoguang.wang@linux.alibaba.com \
/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