public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0.1-rt8
Date: Tue, 9 Aug 2011 18:08:37 -0700	[thread overview]
Message-ID: <20110810010837.GC2737@linux.vnet.ibm.com> (raw)
In-Reply-To: <1312915646.1083.79.camel@twins>

On Tue, Aug 09, 2011 at 08:47:26PM +0200, Peter Zijlstra wrote:
> 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 ;-)

You mean my experience at the tail end of 3.0 -wasn't- being put
on trial?  ;-)

							Thanx, Paul

  reply	other threads:[~2011-08-10  1:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05 21:44 [ANNOUNCE] 3.0.1-rt8 Peter Zijlstra
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 15:28         ` Tim Sander
2011-08-11 12:41       ` Peter Zijlstra
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:39           ` Peter Zijlstra
2011-08-11 17:08             ` Tim Sander
2011-08-11 18:05           ` Peter Zijlstra
2011-08-12  8:59             ` Tim Sander
2011-08-11 10:45   ` Peter Zijlstra
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
2011-08-10  1:08     ` Paul E. McKenney [this message]
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=20110810010837.GC2737@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=nando@ccrma.Stanford.EDU \
    --cc=peterz@infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox