public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	peterz@infradead.org, akpm@linux-foundation.org,
	benh@kernel.crashing.org, fweisbec@gmail.com, ak@linux.intel.com,
	tim.c.chen@linux.intel.com
Subject: Re: [GIT PULL rcu/urgent] Banishing kthreads
Date: Fri, 17 Jun 2011 07:58:38 -0700	[thread overview]
Message-ID: <20110617145838.GA3312@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110617145723.GA3261@linux.vnet.ibm.com>

On Fri, Jun 17, 2011 at 07:57:23AM -0700, Paul E. McKenney wrote:
> Hello, Ingo,
> 
> This pull request banishes RCU kthreads in the RCU_BOOST=n case,
> in response to popular demand.  There are two commits in this
> series:
> 
> 1.	Minimal patch that #ifdefs out the kthread code.
> 
> 2.	Code-movement patch that puts the code #ifdefed out above
> 	under existing #ifdefs in kernel/rcutree_plugin.h.
> 
> These changes are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git rcu/urgent

This time with the correct request-pull info.  :-/

 							Thanx, Paul


------------------->

Paul E. McKenney (2):
      rcu: use softirq instead of kthreads except when RCU_BOOST=y
      rcu: Move RCU_BOOST #ifdefs to header file

 kernel/rcutree.c        |  382 ++-----------------------------------------
 kernel/rcutree.h        |   13 ++-
 kernel/rcutree_plugin.h |  419 +++++++++++++++++++++++++++++++++++++++++++++--
 kernel/rcutree_trace.c  |   32 +++-
 4 files changed, 456 insertions(+), 390 deletions(-)

  reply	other threads:[~2011-06-17 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17 14:57 [GIT PULL rcu/urgent] Banishing kthreads Paul E. McKenney
2011-06-17 14:58 ` Paul E. McKenney [this message]
2011-06-18 19:48 ` Ingo Molnar

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=20110617145838.GA3312@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tim.c.chen@linux.intel.com \
    --cc=torvalds@linux-foundation.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