netdev - Re: [RFC] cpualloc: improvements to per-cpu allocation

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 31 Dec 2008 19:03:00 -0600 (CST)
From:	Christoph Lameter <cl@...ux-foundation.org>
To:	Rusty Russell <rusty@...tcorp.com.au>
cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	catalin.marinas@....com, akpm@...ux-foundation.org,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Subject: Re: [RFC] cpualloc: improvements to per-cpu allocation

On Thu, 1 Jan 2009, Rusty Russell wrote:

> I don't think it's a problem.  You still can't use them directly (this
> wording was not meant to imply that), but you can now hand their addresses
> to per_cpu_ptr() etc.  So zero-based x86-64 should Just Work.

Ok so this is going to be merged for 2.6.29? Its a good cleanup and a step
forward to our goals.


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html