All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"Paul E. McKenney" <paulmck@us.ibm.com>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0.1-rt8
Date: Tue, 09 Aug 2011 20:47:26 +0200	[thread overview]
Message-ID: <1312915646.1083.79.camel@twins> (raw)
In-Reply-To: <4E417D12.70608@localhost>

On Tue, 2011-08-09 at 11:31 -0700, Fernando Lopez-Lezcano wrote:
> Hmmm, what are reasonable values for CONFIG_RCU_BOOST_PRIO and 
> CONFIG_RCU_BOOST_DELAY? (or at least what are you using?).

I'm using the defaults, since I haven't actually got a workload besides
compiling kernels ;-)

Changing these values is very much workload dependent, the PRIO should
be high enough not to cause memory starvation, but low enough not to
disrupt anything important, and thus completely dependent on you
favourite RT workload.

The same goes for the DELAY, too long and you run out of memory, too
short and you get more overhead, depends on your workload, your machine
memory size etc..

Paul should of course be put on trial for giving us these knobs, but
seeing where they come from I totally understand they exist ;-)

  reply	other threads:[~2011-08-09 18:47 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05 21:44 [ANNOUNCE] 3.0.1-rt8 Peter Zijlstra
2011-08-08 13:55 ` rcu stalls running 3.0.1-rt8 Mike Galbraith
2011-08-08 23:10   ` Paul E. McKenney
2011-08-09  1:14     ` Mike Galbraith
2011-08-09 15:13 ` [ANNOUNCE] 3.0.1-rt8 - Regression to 3.0-rt7 Tim Sander
2011-08-11  9:43   ` Peter Zijlstra
2011-08-11 11:30     ` Tim Sander
2011-08-11 12:02       ` Peter Zijlstra
2011-08-11 12:52         ` Tim Sander
2011-08-11 12:52           ` Tim Sander
2011-08-11 15:28         ` Tim Sander
2011-08-11 15:28           ` Tim Sander
2011-08-11 12:41       ` Peter Zijlstra
2011-08-11 16:04         ` Tim Sander
2011-08-11 16:04           ` Tim Sander
2011-08-11 16:14           ` Peter Zijlstra
2011-08-11 16:22             ` Tim Sander
2011-08-11 16:41               ` Tim Sander
2011-08-11 16:41                 ` Tim Sander
2011-08-11 16:39           ` Peter Zijlstra
2011-08-11 17:08             ` Tim Sander
2011-08-11 17:08               ` Tim Sander
2011-08-11 18:05           ` Peter Zijlstra
2011-08-11 18:05             ` Peter Zijlstra
2011-08-12  8:59             ` Tim Sander
2011-08-12  8:59               ` Tim Sander
2011-08-11 10:45   ` Peter Zijlstra
2011-08-11 15:36     ` Tim Sander
2011-08-11 15:36       ` Tim Sander
2011-08-09 18:31 ` [ANNOUNCE] 3.0.1-rt8 Fernando Lopez-Lezcano
2011-08-09 18:47   ` Peter Zijlstra [this message]
2011-08-10  1:08     ` Paul E. McKenney
2011-08-10  1:07   ` 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=1312915646.1083.79.camel@twins \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=nando@ccrma.Stanford.EDU \
    --cc=paulmck@us.ibm.com \
    --cc=tglx@linutronix.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 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.