From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762529AbXEKQTk (ORCPT ); Fri, 11 May 2007 12:19:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759642AbXEKQTb (ORCPT ); Fri, 11 May 2007 12:19:31 -0400 Received: from smtp1.linux-foundation.org ([65.172.181.25]:49607 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759631AbXEKQTa (ORCPT ); Fri, 11 May 2007 12:19:30 -0400 Date: Fri, 11 May 2007 09:17:44 -0700 From: Andrew Morton To: Peter Zijlstra Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Oleg Nesterov , Ingo Molnar , Thomas Gleixner , Nick Piggin Subject: Re: [PATCH 2/2] mm: change mmap_sem over to the scalable rw_mutex Message-Id: <20070511091744.236e8409.akpm@linux-foundation.org> In-Reply-To: <20070511132321.984615201@chello.nl> References: <20070511131541.992688403@chello.nl> <20070511132321.984615201@chello.nl> X-Mailer: Sylpheed 2.4.1 (GTK+ 2.8.17; x86_64-unknown-linux-gnu) 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 On Fri, 11 May 2007 15:15:43 +0200 Peter Zijlstra wrote: > - down_write(¤t->mm->mmap_sem); > + rw_mutex_write_lock(¤t->mm->mmap_lock); y'know, this is such an important lock and people have had such problems with it and so many different schemes and ideas have popped up that I'm kinda thinking that we should wrap it: write_lock_mm(struct mm_struct *mm); write_unlock_mm(struct mm_struct *mm); read_lock_mm(struct mm_struct *mm); read_unlock_mm(struct mm_struct *mm); so that further experimentations become easier?