From mboxrd@z Thu Jan 1 00:00:00 1970 From: Theodore Tso Subject: Re: [patch 00/27] [rfc] vfs scalability patchset Date: Sat, 25 Apr 2009 18:05:22 -0400 Message-ID: <20090425220522.GA10248@mit.edu> References: <20090425012020.457460929@suse.de> <20090425041829.GX8633@ZenIV.linux.org.uk> <20090425080143.GA29033@infradead.org> <20090425193133.GB8633@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Al Viro , Christoph Hellwig , npiggin@suse.de, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: "Eric W. Biederman" Return-path: Received: from THUNK.ORG ([69.25.196.29]:37006 "EHLO thunker.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751090AbZDYWFn (ORCPT ); Sat, 25 Apr 2009 18:05:43 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sat, Apr 25, 2009 at 01:29:01PM -0700, Eric W. Biederman wrote: > > I didn't trace it all of the way through but this comment in > ext3_remount fooled me: > > /* > * We have to unlock super so that we can wait for > * transactions. > */ > > Which was enough to think it might have been deliberate behavior so I figured > it was worth asking. It looked like the journal commit logic could have > been doing the blocking magic to wait on ongoing truncates and the like. Working on fixing this already for ext4. Once we're convinced it's right for ext4, we can backport the fixes for ext3. - Ted