From: Peter Zijlstra <peterz@infradead.org>
To: Tejun Heo <htejun@gmail.com>
Cc: Gautham R Shenoy <ego@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Michael Ellerman <mpe@ellerman.id.au>,
Abdul Haleem <abdhalee@linux.vnet.ibm.com>,
Aneesh Kumar <aneesh.kumar@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com
Subject: Re: [PATCH 1/2] workqueue: Move wq_update_unbound_numa() to the beginning of CPU_ONLINE
Date: Tue, 21 Jun 2016 21:47:19 +0200 [thread overview]
Message-ID: <20160621194719.GU30154@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160621194356.GU3262@mtj.duckdns.org>
On Tue, Jun 21, 2016 at 03:43:56PM -0400, Tejun Heo wrote:
> On Tue, Jun 21, 2016 at 09:37:09PM +0200, Peter Zijlstra wrote:
> > Hurm.. So I've applied it, just to get this issue sorted, but I'm not
> > entirely sure I like it.
> >
> > I think I prefer ego's version because that makes it harder to get stuff
> > to run on !active,online cpus. I think we really want to be careful what
> > gets to run during that state.
>
> The original patch just did set_cpus_allowed one more time late enough
> so that the target kthread (in most cases) doesn't have to go through
> fallback rq selection afterwards. I don't know what the long term
> solution is but CPU_ONLINE callbacks should be able to bind kthreads
> to the new CPU one way or the other.
Fair enough; clearly I need to stare harder. In any case, patch is on
its way to sched/urgent.
next prev parent reply other threads:[~2016-06-21 19:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <573D9C2D.4020609@linux.vnet.ibm.com>
[not found] ` <20160526151137.GA26508@in.ibm.com>
2016-06-07 12:29 ` WARNING at kernel/sched/core.c:1166 while booting 4.6.0 mainline on ppc64le bare metal Abdul Haleem
2016-06-07 15:14 ` [PATCH 0/2] Fix CPU Online handling for unbounded worker threads Gautham R. Shenoy
2016-06-07 15:14 ` [PATCH 1/2] workqueue: Move wq_update_unbound_numa() to the beginning of CPU_ONLINE Gautham R. Shenoy
2016-06-15 15:53 ` Tejun Heo
2016-06-15 19:28 ` Gautham R Shenoy
2016-06-16 19:35 ` Tejun Heo
2016-06-21 14:12 ` Gautham R Shenoy
2016-06-21 15:36 ` Tejun Heo
2016-06-21 19:37 ` Peter Zijlstra
2016-06-21 19:43 ` Tejun Heo
2016-06-21 19:47 ` Peter Zijlstra [this message]
2016-06-22 5:15 ` Gautham R Shenoy
2016-06-24 9:00 ` [tip:sched/urgent] sched/core: Allow kthreads to fall back to online && !active cpus tip-bot for Tejun Heo
2016-06-07 15:14 ` [PATCH 2/2] workqueue:Fix affinity of an unbound worker of a node with 1 online CPU Gautham R. Shenoy
2016-06-08 6:03 ` Abdul Haleem
2016-06-14 11:22 ` Peter Zijlstra
2016-06-15 10:19 ` Gautham R Shenoy
2016-06-15 11:32 ` Peter Zijlstra
2016-06-15 12:50 ` Gautham R Shenoy
2016-06-15 13:14 ` Peter Zijlstra
2016-06-15 16:01 ` Tejun Heo
2016-06-16 12:11 ` Michael Ellerman
2016-06-16 12:45 ` Peter Zijlstra
2016-06-16 19:39 ` Tejun Heo
2016-06-17 1:49 ` Michael Ellerman
2016-07-15 5:27 ` Gautham R Shenoy
[not found] ` <57887507.911f240a.687de.08c5SMTPIN_ADDED_BROKEN@mx.google.com>
2016-07-15 12:10 ` Tejun Heo
2016-06-13 5:44 ` [PATCH 0/2] Fix CPU Online handling for unbounded worker threads Gautham R Shenoy
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=20160621194719.GU30154@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=ego@linux.vnet.ibm.com \
--cc=htejun@gmail.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=tglx@linutronix.de \
/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).