Re: [PATCH 1/6] hotplug: Optimize {get,put}_online_cpus()

2013-10-10 Thread Paul E. McKenney
On Thu, Oct 10, 2013 at 01:06:16PM +0200, Oleg Nesterov wrote: > On 10/09, Andrew Morton wrote: > > > > On Tue, 08 Oct 2013 12:25:06 +0200 Peter Zijlstra > > wrote: > > > > > The current implementation of get_online_cpus() is global of nature > > > and thus not suited for any kind of common usage

Re: [PATCH 1/6] hotplug: Optimize {get,put}_online_cpus()

2013-10-10 Thread Oleg Nesterov
On 10/09, Andrew Morton wrote: > > On Tue, 08 Oct 2013 12:25:06 +0200 Peter Zijlstra > wrote: > > > The current implementation of get_online_cpus() is global of nature > > and thus not suited for any kind of common usage. > > > > Re-implement the current recursive r/w cpu hotplug lock such that t

Re: [PATCH 1/6] hotplug: Optimize {get,put}_online_cpus()

2013-10-09 Thread Andrew Morton
On Tue, 08 Oct 2013 12:25:06 +0200 Peter Zijlstra wrote: > The current implementation of get_online_cpus() is global of nature > and thus not suited for any kind of common usage. > > Re-implement the current recursive r/w cpu hotplug lock such that the > read side locks are as light as possible.

Re: [PATCH 1/6] hotplug: Optimize {get,put}_online_cpus()

2013-10-08 Thread Rik van Riel
On 10/08/2013 06:25 AM, Peter Zijlstra wrote: Reviewed-by: Rik van Riel -- All rights reversed -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Plea

[PATCH 1/6] hotplug: Optimize {get,put}_online_cpus()

2013-10-08 Thread Peter Zijlstra
The current implementation of get_online_cpus() is global of nature and thus not suited for any kind of common usage. Re-implement the current recursive r/w cpu hotplug lock such that the read side locks are as light as possible. The current cpu hotplug lock is entirely reader biased; but since r