linux-kernel - 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 1 Jan 2009 13:42:58 +1030
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Christoph Lameter <cl@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	catalin.marinas@....com, akpm@...ux-foundation.org,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [RFC] cpualloc: improvements to per-cpu allocation

On Thursday 01 January 2009 11:33:00 Christoph Lameter wrote:
> 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.

I'm on the fence, but you've convinced me.  I'll put this in linux-next,
and if there's no damage, I'll push to Linus.  The actual conversions I'll
send via the maintainers though.

These patches have been around for a while, and though they've been polished
a little more in the last week or so the changes were mainly cosmetic.

Thanks,
Rusty.
--
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/