From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Blunck Subject: Re: [RFC 2/3] BKL: remove from ext2 Date: Sat, 31 Oct 2009 13:24:30 +0100 Message-ID: <20091031122430.GA22999@T61.lan> References: <1254324604-20243-1-git-send-email-jblunck@suse.de> <1254324604-20243-3-git-send-email-jblunck@suse.de> <20091001180143.GA22497@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org To: Christoph Hellwig Return-path: Received: from charybdis-ext.suse.de ([195.135.221.2]:51516 "EHLO emea5-mh.id5.novell.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1757709AbZJaMY2 (ORCPT ); Sat, 31 Oct 2009 08:24:28 -0400 Content-Disposition: inline In-Reply-To: <20091001180143.GA22497@infradead.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Oct 01, Christoph Hellwig wrote: > On Wed, Sep 30, 2009 at 05:30:03PM +0200, Jan Blunck wrote: > > Remove the big kernel lock from ext2 and replace it with a per superblock > > mutex. > > Might be worth taking a look what the other ext brothers are doing in > that area and doing proper finer-grained locking? > Ext3/4 are taking lock_super() instead. But because of the comment for lock_super() I choose against that. I think a simple mutex should do the trick. Thanks, Jan