Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932207Ab0AEVBA (ORCPT ); Tue, 5 Jan 2010 16:01:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754929Ab0AEVA7 (ORCPT ); Tue, 5 Jan 2010 16:00:59 -0500 Received: from smtp1.linux-foundation.org ([140.211.169.13]:57979 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754505Ab0AEVA6 (ORCPT ); Tue, 5 Jan 2010 16:00:58 -0500 Date: Tue, 5 Jan 2010 13:00:18 -0800 (PST) From: Linus Torvalds X-X-Sender: torvalds@localhost.localdomain To: Peter Zijlstra cc: Christoph Lameter , Andi Kleen , KAMEZAWA Hiroyuki , Minchan Kim , "Paul E. McKenney" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "hugh.dickins" , Nick Piggin , Ingo Molnar Subject: Re: [RFC][PATCH 6/8] mm: handle_speculative_fault() In-Reply-To: Message-ID: References: <20100104182429.833180340@chello.nl> <20100104182813.753545361@chello.nl> <20100105092559.1de8b613.kamezawa.hiroyu@jp.fujitsu.com> <28c262361001042029w4b95f226lf54a3ed6a4291a3b@mail.gmail.com> <20100105134357.4bfb4951.kamezawa.hiroyu@jp.fujitsu.com> <20100105143046.73938ea2.kamezawa.hiroyu@jp.fujitsu.com> <20100105163939.a3f146fb.kamezawa.hiroyu@jp.fujitsu.com> <87wrzwbh0z.fsf@basil.nowhere.org> <1262723356.4049.11.camel@laptop> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 989 Lines: 23 On Tue, 5 Jan 2010, Linus Torvalds wrote: > > I think you need a "compare-and-exchange-2-separate-words" instruction > to make it work (not "cmpxchg8/16b" - literally two _different_ words). Btw, I might be misremembering - Andy was looking at various lockless algorithms too. Maybe the problem was the non-local space requirement. There were several spin-lock variants that would be improved if we could pass a cookie from the 'lock' to the 'unlock'. In fact, even the ticket locks would be improved by that, since we could then possibly do the unlock as a plain 'store' rather than an 'add', and keep the nex-owner cookie in a register over the lock rather than unlock by just incrementing it in the nasty lock cacheline. Linus -- 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/