lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sun, 27 Jan 2008 15:48:53 -0800
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Stefan Richter <stefanr@...6.in-berlin.de>,
	linux-kernel@...r.kernel.org
Subject: Re: preemptible RCU bug (was Re: [git pull] scheduler changes for v2.6.25)

On Sun, Jan 27, 2008 at 01:26:02PM +0100, Ingo Molnar wrote:
> 
> * Paul E. McKenney <paulmck@...ux.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@...ux.vnet.ibm.com>
> 
> This patch supplies help text for the "RCU implementation type"
> kernel configuration choice.
> 
> Reported-by: Stefan Richter <stefanr@...6.in-berlin.de>
> Signed-off-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> Signed-off-by: Ingo Molnar <mingo@...e.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"
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ