From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Christoph Lameter <cl@gentwo.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, mingo@kernel.org,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, rostedt@goodmis.org,
dhowells@redhat.com, edumazet@google.com, dvhart@linux.intel.com,
fweisbec@gmail.com, oleg@redhat.com, dave.hansen@intel.com,
ak@linux.intel.com, umgwanakikbuti@gmail.com
Subject: Re: [PATCH tip/core/rcu] Reduce overhead of cond_resched() checks for RCU
Date: Mon, 23 Jun 2014 09:45:29 -0700 [thread overview]
Message-ID: <20140623164529.GE4603@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1406230848540.2892@gentwo.org>
On Mon, Jun 23, 2014 at 08:51:08AM -0500, Christoph Lameter wrote:
> On Mon, 23 Jun 2014, Peter Zijlstra wrote:
>
> > On the topic of these threads; I recently noticed RCU grew a metric ton
> > of them, I found some 75 rcu kthreads on my box, wth up with that?
>
> Would kworker threads work for rcu? That would also avoid the shifting
> around of RCU threads for NOHZ configurations (which seems to have to be
> done manually right now). The kworker subsystem work that allows
> restriction to non NOHZ hardware threads would then also allow the
> shifting of the rcu threads which would simplify the whole endeavor.
Short term, I am planning to use a different method to automate the
binding of the rcuo kthreads to housekeeping CPUs, but longer term,
it might well make a lot of sense to move to workqueues and the kworker
threads.
Thanx, Paul
next prev parent reply other threads:[~2014-06-23 16:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-21 2:59 [PATCH tip/core/rcu] Reduce overhead of cond_resched() checks for RCU Paul E. McKenney
2014-06-21 4:29 ` Josh Triplett
2014-06-21 6:06 ` Paul E. McKenney
2014-06-23 13:53 ` Christoph Lameter
2014-06-23 15:26 ` Paul E. McKenney
2014-06-23 6:26 ` Peter Zijlstra
2014-06-23 13:33 ` Paul E. McKenney
2014-06-23 13:51 ` Christoph Lameter
2014-06-23 16:45 ` Paul E. McKenney [this message]
2014-06-23 15:49 ` Andi Kleen
2014-06-23 16:43 ` Paul E. McKenney
2014-06-23 17:19 ` Andi Kleen
2014-06-23 17:42 ` Paul E. McKenney
2014-06-23 16:55 ` Dave Hansen
2014-06-23 17:16 ` Paul E. McKenney
2014-06-23 17:34 ` Dave Hansen
2014-06-23 17:17 ` Dave Hansen
2014-06-23 18:09 ` Paul E. McKenney
2014-06-23 23:30 ` Dave Hansen
2014-06-24 0:15 ` Paul E. McKenney
2014-06-24 0:20 ` Dave Hansen
2014-06-24 0:39 ` Paul E. McKenney
2014-06-24 16:18 ` Dave Hansen
2014-06-24 20:43 ` Dave Hansen
2014-06-24 21:15 ` Paul E. McKenney
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=20140623164529.GE4603@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=dave.hansen@intel.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.