Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S937906AbWLGBJE (ORCPT ); Wed, 6 Dec 2006 20:09:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S937905AbWLGBJD (ORCPT ); Wed, 6 Dec 2006 20:09:03 -0500 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:38388 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S937903AbWLGBJB (ORCPT ); Wed, 6 Dec 2006 20:09:01 -0500 Date: Wed, 06 Dec 2006 17:09:11 -0800 (PST) Message-Id: <20061206.170911.45496956.davem@davemloft.net> To: viro@ftp.linux.org.uk Cc: torvalds@osdl.org, clameter@sgi.com, rmk+lkml@arm.linux.org.uk, dhowells@redhat.com, akpm@osdl.org, linux-arm-kernel@lists.arm.linux.org.uk, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org Subject: Re: [PATCH] WorkStruct: Implement generic UP cmpxchg() where an arch doesn't support it From: David Miller In-Reply-To: <20061206190828.GE4587@ftp.linux.org.uk> References: <20061206190828.GE4587@ftp.linux.org.uk> X-Mailer: Mew version 4.2 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 822 Lines: 22 From: Al Viro Date: Wed, 6 Dec 2006 19:08:28 +0000 > On Wed, Dec 06, 2006 at 11:05:22AM -0800, Linus Torvalds wrote: > > > > > > On Wed, 6 Dec 2006, Christoph Lameter wrote: > > > > > > I'd really appreciate a cmpxchg that is generically available for > > > all arches. It will allow lockless implementation for various performance > > > criticial portions of the kernel. > > > > I suspect ARM may have been the last one without one, no? > > No. sparc32 doesn't have one, for instance. That's correct. It has an atomic swap, but not a cmpxchg. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/