Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762071AbZLPLPo (ORCPT ); Wed, 16 Dec 2009 06:15:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1762063AbZLPLPk (ORCPT ); Wed, 16 Dec 2009 06:15:40 -0500 Received: from fgwmail6.fujitsu.co.jp ([192.51.44.36]:42297 "EHLO fgwmail6.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762062AbZLPLPi (ORCPT ); Wed, 16 Dec 2009 06:15:38 -0500 X-SecurityPolicyCheck-FJ: OK by FujitsuOutboundMailChecker v1.3.1 Date: Wed, 16 Dec 2009 20:12:18 +0900 From: KAMEZAWA Hiroyuki To: Andi Kleen Cc: "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , cl@linux-foundation.org, "akpm@linux-foundation.org" , "mingo@elte.hu" , minchan.kim@gmail.com Subject: Re: [mm][RFC][PATCH 0/11] mm accessor updates. Message-Id: <20091216201218.42ff7f05.kamezawa.hiroyu@jp.fujitsu.com> In-Reply-To: <20091216104951.GD15031@basil.fritz.box> References: <20091216120011.3eecfe79.kamezawa.hiroyu@jp.fujitsu.com> <20091216101107.GA15031@basil.fritz.box> <20091216191312.f4655dac.kamezawa.hiroyu@jp.fujitsu.com> <20091216102806.GC15031@basil.fritz.box> <20091216193109.778b881b.kamezawa.hiroyu@jp.fujitsu.com> <20091216104951.GD15031@basil.fritz.box> Organization: FUJITSU Co. LTD. X-Mailer: Sylpheed 2.5.0 (GTK+ 2.10.14; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1352 Lines: 35 On Wed, 16 Dec 2009 11:49:51 +0100 Andi Kleen wrote: > On Wed, Dec 16, 2009 at 07:31:09PM +0900, KAMEZAWA Hiroyuki wrote: > > On Wed, 16 Dec 2009 11:28:06 +0100 > > Andi Kleen wrote: > > > > > > > Also the patches didn't fare too well in testing unfortunately. > > > > > > > > > > I suspect we'll rather need multiple locks split per address > > > > > space range. > > > > > > > > This set doesn't include any changes of the logic. Just replace all mmap_sem. > > > > I think this is good start point (for introducing another logic etc..) > > > > > > The problem is that for range locking simple wrapping the locks > > > in macros is not enough. You need more changes. > > > > > maybe. but removing scatterred mmap_sem from codes is the first thing to do. > > I think this removing itself will take 3 month or a half year. > > (So, I didn't remove mmap_sem and leave it as it is.) > > I suspect you would just need to change them again then. > Do you have alternative recommendation rather than wrapping all accesses by special functions ? Thanks, -Kame -- 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/