From: "Paul E. McKenney" <paulmck@kernel.org>
To: Lai Jiangshan <jiangshanlai@gmail.com>
Cc: "Zhang, Qiang" <qiang.zhang@windriver.com>,
Tejun Heo <tj@kernel.org>, Tejun Heo <htejun@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] workqueue: Remove rcu_read_lock/unlock() in workqueue_congested()
Date: Thu, 18 Feb 2021 07:17:32 -0800 [thread overview]
Message-ID: <20210218151732.GR2743@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <CAJhGHyDE18PwQtS_W-aZA4Z6SAX3ZiCr6bA1Gqpu=XMN2n724w@mail.gmail.com>
On Thu, Feb 18, 2021 at 11:04:00AM +0800, Lai Jiangshan wrote:
> +CC Paul
>
>
> On Wed, Feb 17, 2021 at 7:58 PM <qiang.zhang@windriver.com> wrote:
> >
> > From: Zqiang <qiang.zhang@windriver.com>
> >
> > The RCU read critical area already by preempt_disable/enable()
> > (equivalent to rcu_read_lock_sched/unlock_sched()) mark, so remove
> > rcu_read_lock/unlock().
>
> I think we can leave it which acks like document, especially
> workqueue_congested() is not performance crucial. Either way
> is Ok for me.
If the rcu_read_lock() is removed, should there be a comment saying that
it interacts with synchronize_rcu()? Just in case one of the real-time
guys figures out a way to get the job done without disabling preemption...
Thanx, Paul
> If it needs to be changed, please also do the same for
> rcu_read_lock() in wq_watchdog_timer_fn().
>
> And __queue_work() and try_to_grab_pending() also use local_irq_save()
> and rcu_read_lock() at the same time, but I don't know will these
> local_irq_save() be changed to raw_local_irq_save() in PREEMPT_RT.
>
>
> >
> > Signed-off-by: Zqiang <qiang.zhang@windriver.com>
> > ---
> > kernel/workqueue.c | 2 --
> > 1 file changed, 2 deletions(-)
> >
> > diff --git a/kernel/workqueue.c b/kernel/workqueue.c
> > index 0d150da252e8..c599835ad6c3 100644
> > --- a/kernel/workqueue.c
> > +++ b/kernel/workqueue.c
> > @@ -4540,7 +4540,6 @@ bool workqueue_congested(int cpu, struct workqueue_struct *wq)
> > struct pool_workqueue *pwq;
> > bool ret;
> >
> > - rcu_read_lock();
> > preempt_disable();
> >
> > if (cpu == WORK_CPU_UNBOUND)
> > @@ -4553,7 +4552,6 @@ bool workqueue_congested(int cpu, struct workqueue_struct *wq)
> >
> > ret = !list_empty(&pwq->delayed_works);
> > preempt_enable();
> > - rcu_read_unlock();
> >
> > return ret;
> > }
> > --
> > 2.25.1
> >
next prev parent reply other threads:[~2021-02-18 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 11:58 qiang.zhang
2021-02-18 3:04 ` Lai Jiangshan
2021-02-18 15:17 ` Paul E. McKenney [this message]
2021-02-22 9:13 ` 回复: " Zhang, Qiang
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=20210218151732.GR2743@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=htejun@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qiang.zhang@windriver.com \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®