Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261951AbVANKrm (ORCPT ); Fri, 14 Jan 2005 05:47:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261949AbVANKrl (ORCPT ); Fri, 14 Jan 2005 05:47:41 -0500 Received: from colin2.muc.de ([193.149.48.15]:36103 "HELO colin2.muc.de") by vger.kernel.org with SMTP id S261948AbVANKre (ORCPT ); Fri, 14 Jan 2005 05:47:34 -0500 Date: 14 Jan 2005 11:47:32 +0100 Date: Fri, 14 Jan 2005 11:47:32 +0100 From: Andi Kleen To: Nick Piggin Cc: clameter@sgi.com, Andrew Morton , torvalds@osdl.org, hugh@veritas.com, linux-mm@kvack.org, linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, benh@kernel.crashing.org Subject: Re: page table lock patch V15 [0/7]: overview II Message-ID: <20050114104732.GB72915@muc.de> References: <41E5BC60.3090309@yahoo.com.au> <20050113031807.GA97340@muc.de> <20050113180205.GA17600@muc.de> <20050114043944.GB41559@muc.de> <1105678742.5402.109.camel@npiggin-nld.site> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1105678742.5402.109.camel@npiggin-nld.site> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 582 Lines: 13 > I have a question for the x86 gurus. We're currently using the lock > prefix for set_64bit. This will lock the bus for the RMW cycle, but > is it a prerequisite for the atomic 64-bit store? Even on UP? An atomic 64bit store doesn't need a lock prefix. A cmpxchg will need to though. Note that UP kernels define LOCK to nothing. -Andi - 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/