public inbox for [email protected]
 help / color / mirror / Atom feed
From: Muchun Song <[email protected]>
To: Zqiang <[email protected]>
Cc: Jens Axboe <[email protected]>,
	[email protected], [email protected],
	LKML <[email protected]>
Subject: Re: [PATCH] io-wq: Remove unnecessary rcu_read_lock/unlock() in raw spinlock critical section
Date: Tue, 26 Oct 2021 18:32:38 +0800	[thread overview]
Message-ID: <CAMZfGtUXq=nQyijktRaP7xp=sAmVCryTjU4Jo5Z=ufed8arnKQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>

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. */

With that.

Reviewed-by: Muchun Song <[email protected]>

Thanks.

>         do_create = !io_wqe_activate_free_worker(wqe, acct);
> -       rcu_read_unlock();
>
>         raw_spin_unlock(&wqe->lock);
>
> --
> 2.17.1
>

  reply	other threads:[~2021-10-26 10:33 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 [this message]
2021-10-26 14:47   ` Jens Axboe
2021-10-27  7:06     ` Zqiang

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='CAMZfGtUXq=nQyijktRaP7xp=sAmVCryTjU4Jo5Z=ufed8arnKQ@mail.gmail.com' \
    [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