linux-kernel - Re: [ANNOUNCE] 3.0.1-rt8

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1312915646.1083.79.camel@twins>
Date:	Tue, 09 Aug 2011 20:47:26 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Fernando Lopez-Lezcano <nando@...ma.Stanford.EDU>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"Paul E. McKenney" <paulmck@...ibm.com>,
	linux-rt-users <linux-rt-users@...r.kernel.org>
Subject: Re: [ANNOUNCE] 3.0.1-rt8

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 ;-)
--
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/