linux-kernel - Re: [this_cpu_xx V4 02/20] this_cpu: X86 optimized this

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

Date:	Sat, 03 Oct 2009 22:33:19 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Ingo Molnar <mingo@...e.hu>
CC:	cl@...ux-foundation.org, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, Tejun Heo <tj@...nel.org>,
	rusty@...tcorp.com.au
Subject: Re: [this_cpu_xx V4 02/20] this_cpu: X86 optimized this_cpu	operations

Hi,

Ingo Molnar wrote:
> * cl@...ux-foundation.org <cl@...ux-foundation.org> wrote:
> 
>> Basically the existing percpu ops can be used for this_cpu variants 
>> that allow operations also on dynamically allocated percpu data. 
>> However, we do not pass a reference to a percpu variable in. Instead a 
>> dynamically or statically allocated percpu variable is provided.
>>
>> Preempt, the non preempt and the irqsafe operations generate the same 
>> code. It will always be possible to have the requires per cpu 
>> atomicness in a single RMW instruction with segment override on x86.
>>
>> 64 bit this_cpu operations are not supported on 32 bit.
>>
>> Signed-off-by: Christoph Lameter <cl@...ux-foundation.org>
> 
> Acked-by: Ingo Molnar <mingo@...e.hu>

I haven't looked at the series in detail but AFAICT the SLUB patches 
depend on the x86 ones. Any suggestions how to get all this into 
linux-next? Should I make a topic branch in slab.git on top of -tip or 
something?

			Pekka
--
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/