public inbox for [email protected]
 help / color / mirror / Atom feed
From: Zqiang <[email protected]>
To: Jens Axboe <[email protected]>, Muchun Song <[email protected]>
Cc: [email protected], [email protected],
	LKML <[email protected]>
Subject: Re: [PATCH] io-wq: Remove unnecessary rcu_read_lock/unlock() in raw spinlock critical section
Date: Wed, 27 Oct 2021 15:06:00 +0800	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>


On 2021/10/26 下午10:47, Jens Axboe wrote:
> On 10/26/21 4:32 AM, Muchun Song wrote:
>> On Tue, Oct 26, 2021 at 11:23 AM Zqiang <[email protected]> wrote:
>>> Due to raw_spin_lock/unlock() contains preempt_disable/enable() action,
>>> already regarded as RCU critical region, so remove unnecessary
>>> rcu_read_lock/unlock().
>>>
>>> Signed-off-by: Zqiang <[email protected]>
>>> ---
>>>   fs/io-wq.c | 2 --
>>>   1 file changed, 2 deletions(-)
>>>
>>> diff --git a/fs/io-wq.c b/fs/io-wq.c
>>> index cd88602e2e81..401be005d089 100644
>>> --- a/fs/io-wq.c
>>> +++ b/fs/io-wq.c
>>> @@ -855,9 +855,7 @@ static void io_wqe_enqueue(struct io_wqe *wqe, struct io_wq_work *work)
>>>          io_wqe_insert_work(wqe, work);
>>>          clear_bit(IO_ACCT_STALLED_BIT, &acct->flags);
>>>
>>> -       rcu_read_lock();
>> Add a comment like:
>> /* spin_lock can serve as an RCU read-side critical section. */
> Note that it's a raw spinlock. Honestly I'd probably prefer if we just leave
> it as-is. There are plans to improve the io-wq locking, and a rcu lock/unlock
> is pretty cheap.
>
> That said, if resend with a comment fully detailing why it's OK currently,
> then I'd be fine with that as well.
>
Thanks Jens Axboe, Muchun

  I  will  add a comment fully detailing and resend.




      reply	other threads:[~2021-10-27  7:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  3:23 [PATCH] io-wq: Remove unnecessary rcu_read_lock/unlock() in raw spinlock critical section Zqiang
2021-10-26 10:32 ` Muchun Song
2021-10-26 14:47   ` Jens Axboe
2021-10-27  7:06     ` Zqiang [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] \
    [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