public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: "Paul E. McKenney" <paul.mckenney@linaro.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rcu: Advise most users not to enable RCU user mode
Date: Wed, 10 Oct 2012 17:50:04 -0700	[thread overview]
Message-ID: <20121011005004.GL2495@linux.vnet.ibm.com> (raw)
In-Reply-To: <1349912908-11814-1-git-send-email-fweisbec@gmail.com>

On Thu, Oct 11, 2012 at 01:48:28AM +0200, Frederic Weisbecker wrote:
> Discourage distros from enabling CONFIG_RCU_USER_QS
> because it brings overhead for no benefits yet.
> 
> It's not a useful feature on its own until we can
> fully run an adaptive tickless kernel.

Queued, hopefully for 3.7, thank you!

							Thanx, Paul

> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> ---
>  init/Kconfig |   12 ++++++++++++
>  1 files changed, 12 insertions(+), 0 deletions(-)
> 
> diff --git a/init/Kconfig b/init/Kconfig
> index c26b8a1..89093e1 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -451,6 +451,12 @@ config RCU_USER_QS
>  	  excluded from the global RCU state machine and thus doesn't
>  	  to keep the timer tick on for RCU.
> 
> +	  Unless you want to hack and help the development of the full
> +	  tickless feature, you shouldn't enable this option. It adds
> +	  unnecessary overhead.
> +
> +	  If unsure say N
> +
>  config RCU_USER_QS_FORCE
>  	bool "Force userspace extended QS by default"
>  	depends on RCU_USER_QS
> @@ -459,6 +465,12 @@ config RCU_USER_QS_FORCE
>  	  test this feature that treats userspace as an extended quiescent
>  	  state until we have a real user like a full adaptive nohz option.
> 
> +	  Unless you want to hack and help the development of the full
> +	  tickless feature, you shouldn't enable this option. It adds
> +	  unnecessary overhead.
> +
> +	  If unsure say N
> +
>  config RCU_FANOUT
>  	int "Tree-based hierarchical RCU fanout value"
>  	range 2 64 if 64BIT
> -- 
> 1.7.5.4
> 


      reply	other threads:[~2012-10-11  0:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10 23:48 [PATCH] rcu: Advise most users not to enable RCU user mode Frederic Weisbecker
2012-10-11  0:50 ` 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=20121011005004.GL2495@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.mckenney@linaro.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