From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail190.messagelabs.com (mail190.messagelabs.com [216.82.249.51]) by kanga.kvack.org (Postfix) with ESMTP id 75B13600580 for ; Thu, 7 Jan 2010 15:14:12 -0500 (EST) Date: Thu, 7 Jan 2010 12:13:28 -0800 (PST) From: Linus Torvalds Subject: Re: [RFC][PATCH 6/8] mm: handle_speculative_fault() In-Reply-To: Message-ID: References: <20100104182429.833180340@chello.nl> <20100104182813.753545361@chello.nl> <20100105054536.44bf8002@infradead.org> <20100105192243.1d6b2213@infradead.org> <1262884960.4049.106.camel@laptop> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org To: Christoph Lameter Cc: Peter Zijlstra , Arjan van de Ven , "Paul E. McKenney" , KAMEZAWA Hiroyuki , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "minchan.kim@gmail.com" , "hugh.dickins" , Nick Piggin , Ingo Molnar List-ID: On Thu, 7 Jan 2010, Linus Torvalds wrote: > > Again, it doesn't matter. Old or new - if some other thread looks up the > vma, either is fine. Btw, don't get me wrong. That patch may compile (I checked it), but I am not in any way claiming that it is anything else than a total throw-away "this is something we could look at doing" suggestion. For example, I'm not at all wedded to using 'mm->page_table_lock': I in fact wanted to use a per-vma lock, but I picked a lock we already had. The fact that picking a lock we already had also means that it serializes page table updates (sometimes) is actually a downside, not a good thing. So the patch was meant to get people thinking about alternatives, rather than anything else. The point being that there are things we can play with on mmap_sem, that don't involve getting rid of it - just being a bit more aggressive in how we use it. Linus -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org