From: Daniel Jordan <daniel.m.jordan@oracle.com>
To: Hillf Danton <hdanton@sina.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Tejun Heo <tj@kernel.org>,
Lai Jiangshan <jiangshanlai@gmail.com>
Subject: Re: [RFC 1/4] workqueue: fix selecting cpu for queuing work
Date: Thu, 23 Jan 2020 17:37:43 -0500 [thread overview]
Message-ID: <20200123223743.pfcibulfsugpqbsc@ca-dmjordan1.us.oracle.com> (raw)
In-Reply-To: <20191211230735.r5xpmgwfjjkzxwaf@ca-dmjordan1.us.oracle.com>
On Wed, Dec 11, 2019 at 06:07:35PM -0500, Daniel Jordan wrote:
> [please cc maintainers]
>
> On Wed, Dec 11, 2019 at 06:59:19PM +0800, Hillf Danton wrote:
> > Round robin is needed only for unbound workqueue and wq_unbound_cpumask
> > has nothing to do with standard workqueues, so we have to select cpu in
> > case of WORK_CPU_UNBOUND also with workqueue type taken into account.
>
> Good catch. I'd include something like this in the changelog.
>
> Otherwise, work queued on a bound workqueue with WORK_CPU_UNBOUND might
> not prefer the local CPU if wq_unbound_cpumask is non-empty and doesn't
> include that CPU.
>
> With that you can add
>
> Reviewed-by: Daniel Jordan <daniel.m.jordan@oracle.com>
Any plans to repost this patch, Hillf? If not, I can do it while retaining
your authorship.
Adding back the context, which I forgot to keep when adding the maintainers.
> > Fixes: ef557180447f ("workqueue: schedule WORK_CPU_UNBOUND work on wq_unbound_cpumask CPUs")
> > Signed-off-by: Hillf Danton <hdanton@sina.com>
> > ---
> >
> > --- a/kernel/workqueue.c
> > +++ c/kernel/workqueue.c
> > @@ -1409,16 +1409,19 @@ static void __queue_work(int cpu, struct
> > if (unlikely(wq->flags & __WQ_DRAINING) &&
> > WARN_ON_ONCE(!is_chained_work(wq)))
> > return;
> > +
> > rcu_read_lock();
> > retry:
> > - if (req_cpu == WORK_CPU_UNBOUND)
> > - cpu = wq_select_unbound_cpu(raw_smp_processor_id());
> > -
> > /* pwq which will be used unless @work is executing elsewhere */
> > - if (!(wq->flags & WQ_UNBOUND))
> > - pwq = per_cpu_ptr(wq->cpu_pwqs, cpu);
> > - else
> > + if (wq->flags & WQ_UNBOUND) {
> > + if (req_cpu == WORK_CPU_UNBOUND)
> > + cpu = wq_select_unbound_cpu(raw_smp_processor_id());
> > pwq = unbound_pwq_by_node(wq, cpu_to_node(cpu));
> > + } else {
> > + if (req_cpu == WORK_CPU_UNBOUND)
> > + cpu = raw_smp_processor_id();
> > + pwq = per_cpu_ptr(wq->cpu_pwqs, cpu);
> > + }
> >
> > /*
> > * If @work was previously on a different pool, it might still be
> >
> >
next prev parent reply other threads:[~2020-01-23 22:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 10:46 [RFC 0/4] workqueue: fix selecting cpu for queuing work and cleanup Hillf Danton
2019-12-11 10:59 ` [RFC 1/4] workqueue: fix selecting cpu for queuing work Hillf Danton
2019-12-11 23:07 ` Daniel Jordan
2020-01-23 22:37 ` Daniel Jordan [this message]
2020-01-24 1:01 ` Hillf Danton
2019-12-11 11:12 ` [RFC 2/4] workqueue: use smp_processor_id() on " Hillf Danton
2019-12-11 11:22 ` [RFC 3/4] workqueue: reap dead pool workqueue " Hillf Danton
2019-12-11 23:25 ` Daniel Jordan
2019-12-12 2:28 ` Hillf Danton
2019-12-11 11:33 ` [RFC 4/4] workqueue: use integer for cpu " Hillf Danton
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=20200123223743.pfcibulfsugpqbsc@ca-dmjordan1.us.oracle.com \
--to=daniel.m.jordan@oracle.com \
--cc=hdanton@sina.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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;
as well as URLs for NNTP newsgroup(s).