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] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 4 Jun 2012 21:06:22 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	paulmck@...ux.vnet.ibm.com
Cc:	Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Alessio Igor Bogani <abogani@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Avi Kivity <avi@...hat.com>,
	Chris Metcalf <cmetcalf@...era.com>,
	Christoph Lameter <cl@...ux.com>,
	Daniel Lezcano <daniel.lezcano@...aro.org>,
	Geoff Levand <geoff@...radead.org>,
	Gilad Ben Yossef <gilad@...yossef.com>,
	Hakan Akkan <hakanakkan@...il.com>,
	Kevin Hilman <khilman@...com>,
	Max Krasnyansky <maxk@...lcomm.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Stephen Hemminger <shemminger@...tta.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Sven-Thorsten Dietrich <thebigcorporation@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 0/2] rcu: Extended quiescent state for adaptive nohz

2012/6/4 Paul E. McKenney <paulmck@...ux.vnet.ibm.com>:
> On Mon, Jun 04, 2012 at 02:08:26PM +0200, fweisbec@...il.com wrote:
>> From: Frederic Weisbecker <fweisbec@...il.com>
>>
>> Paul, Ingo,
>>
>> This is a rebase of the nohz cpusets RCU APIs on top of Paul's latest
>> -rcu (rcu/core) branch.
>>
>> I have only built tested it yet, I need to do a full rebase of my
>> tree to test it in practice. But I wanted to show you how it looks
>> like first.
>>
>> I also wonder if we can set that to a tree somewhere. Ingo suggested
>> to set up a tree on -tip to apply the uncontroversial part of nohz
>> cpusets patches and iterate from there. I think it would accelerate
>> everything if we start doing that.
>
> It would probably be best to put these two in the -rcu set in order to
> avoid conflicts with possible further RCU_FAST_NO_HZ work.  I could
> push this to -tip early, if that would help.

But then these APIs are going to be upstream on 3.6
Is that ok for you even if they don't have any upstream user?
We can ifdef it.
--
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