public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>, linux-kernel@vger.kernel.org
Subject: Re: preemptible RCU bug (was Re: [git pull] scheduler changes for v2.6.25)
Date: Sun, 27 Jan 2008 15:48:53 -0800	[thread overview]
Message-ID: <20080127234853.GA10148@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080127122602.GA17293@elte.hu>

On Sun, Jan 27, 2008 at 01:26:02PM +0100, Ingo Molnar wrote:
> 
> * Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> 
> > > Sorry, no help available for this option yet.
> > 
> > Good catch!!!
> > 
> > This patch supplies help text for the "RCU implementation type" kernel 
> > configuration choice.
> 
> thanks applied to sched.git. (see the patch below - the config option is 
> in init/Kconfig in mainline, not in kernel/Kconfig.preempt)

Ah missed that -- thank you for retargeting the patch.

							Thanx, Paul

> 	Ingo
> 
> ------------->
> Subject: RCU: add help text for "RCU implementation type"
> From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> 
> This patch supplies help text for the "RCU implementation type"
> kernel configuration choice.
> 
> Reported-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> ---
> 
>  init/Kconfig |    8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> Index: linux/init/Kconfig
> ===================================================================
> --- linux.orig/init/Kconfig
> +++ linux/init/Kconfig
> @@ -779,6 +779,14 @@ config PREEMPT_NOTIFIERS
>  choice
>  	prompt "RCU implementation type:"
>  	default CLASSIC_RCU
> +	help
> +	  This allows you to choose either the classic RCU implementation
> +	  that is designed for best read-side performance on non-realtime
> +	  systems, or the preemptible RCU implementation for best latency
> +	  on realtime systems.  Note that some kernel preemption modes
> +	  will restrict your choice.
> +
> +	  Select the default if you are unsure.
> 
>  config CLASSIC_RCU
>  	bool "Classic RCU"

      reply	other threads:[~2008-01-27 23:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-25 20:37 [git pull] scheduler changes for v2.6.25 Ingo Molnar
2008-01-26 19:19 ` preemptible RCU bug (was Re: [git pull] scheduler changes for v2.6.25) Stefan Richter
2008-01-27 11:05   ` Paul E. McKenney
2008-01-27 11:16     ` Stefan Richter
2008-01-27 12:26     ` Ingo Molnar
2008-01-27 23:48       ` Paul E. McKenney [this message]

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=20080127234853.GA10148@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=stefanr@s5r6.in-berlin.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