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:	Thu, 09 Jun 2011 12:53:43 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Christoph Lameter <cl@...ux.com>
CC:	David Rientjes <rientjes@...gle.com>, tj@...nel.org,
	Eric Dumazet <eric.dumazet@...il.com>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>, mingo@...e.hu
Subject: Re: [slubllv7 04/17] x86: Add support for cmpxchg_double

On 6/1/11 8:25 PM, Christoph Lameter wrote:
> A simple implementation that only supports the word size and does not
> have a fallback mode (would require a spinlock).
>
> Add 32 and 64 bit support for cmpxchg_double. cmpxchg double uses
> the cmpxchg8b or cmpxchg16b instruction on x86 processors to compare
> and swap 2 machine words. This allows lockless algorithms to move more
> context information through critical sections.
>
> Set a flag CONFIG_CMPXCHG_DOUBLE to signal that support for double word
> cmpxchg detection has been build into the kernel. Note that each subsystem
> using cmpxchg_double has to implement a fall back mechanism as long as
> we offer support for processors that do not implement cmpxchg_double.
>
> Reviewed-by: H. Peter Anvin<hpa@...or.com>
> Cc: tj@...nel.org
> Signed-off-by: Christoph Lameter<cl@...ux.com>

Tejun, I'm going to queue this series for linux-next in the next few 
days. Could you either pick up this patch so I can pull from your tree 
or alternatively, is it OK to queue this through slab.git?

			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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ