Re: [PATCH 1/3] clockevents: Use an atomic RCU notifier forclockevents

[Thomas Gleixner]

On Mon, 29 Aug 2011, Andi Kleen wrote:

> From: Andi Kleen <ak@xxxxxxxxxxxxxxx>
> 
> Use an atomic_notifier instead of a raw_notifier for the clockevents
> notification.
> 
> This avoids a global lock in the idle path, is a scalability
> problem. With this patch we don't have a global lock anymore
> at least on systems with an always running timer.

And why is that code called on a system with an always running local
apic timer at all? The broadcast horror is explicitely only for those
systems with wreckaged hardware.
 
Either the patch makes no sense or the changelog or both.

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/