linux-kernel - Re: Remove hotplug cpu crap from cpufreq.

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] [day] [month] [year] [list]

Date:	Fri, 3 Nov 2006 03:10:34 +0530
From:	Dipankar Sarma <dipankar@...ibm.com>
To:	Linus Torvalds <torvalds@...l.org>
Cc:	Andrew Morton <akpm@...l.org>, Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Gautham Shenoy <ego@...ibm.com>
Subject: Re: Remove hotplug cpu crap from cpufreq.

On Thu, Nov 02, 2006 at 11:30:20AM -0800, Linus Torvalds wrote:
> 
> 
> On Fri, 3 Nov 2006, Dipankar Sarma wrote:
> > 
> > IMO, the right thing to do would be to convert lock_cpu_hotplug() to
> > a get_cpu_hotplug()/put_cpu_hotplug() type semantics and use a more
> > scalable implementation underneath (as opposed to a global
> > semaphore/mutex).
> 
> Yes, I think Gautham's patch-series basically did exactly that, no? Except 
> it kept the old name.

Yes, atleast that is the idea - turn it into a scalable refcount model
as opposed to a global lock.

Thanks
Dipankar
-
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/