Re: [RFC][PATCH 3/4] use a rwsem for cpucontrol

2005-01-19 Thread Rusty Russell
On Wed, 2005-01-19 at 22:38 +0100, Dominik Brodowski wrote: > Currently, lock_cpu_hotplug serializes multiple calls to cpufreq->target() > on multiple CPUs even though that's unnecessary. Even further, it > serializes these calls with totally unrelated other parts of the kernel... > some ppc64

[RFC][PATCH 3/4] use a rwsem for cpucontrol

2005-01-19 Thread Dominik Brodowski
Currently, lock_cpu_hotplug serializes multiple calls to cpufreq->target() on multiple CPUs even though that's unnecessary. Even further, it serializes these calls with totally unrelated other parts of the kernel... some ppc64 event reporting, some cache management, and so on. In my opinion

[RFC][PATCH 3/4] use a rwsem for cpucontrol

2005-01-19 Thread Dominik Brodowski
Currently, lock_cpu_hotplug serializes multiple calls to cpufreq-target() on multiple CPUs even though that's unnecessary. Even further, it serializes these calls with totally unrelated other parts of the kernel... some ppc64 event reporting, some cache management, and so on. In my opinion locking

Re: [RFC][PATCH 3/4] use a rwsem for cpucontrol

2005-01-19 Thread Rusty Russell
On Wed, 2005-01-19 at 22:38 +0100, Dominik Brodowski wrote: Currently, lock_cpu_hotplug serializes multiple calls to cpufreq-target() on multiple CPUs even though that's unnecessary. Even further, it serializes these calls with totally unrelated other parts of the kernel... some ppc64 event