From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: Linux 2.6.35 Date: Mon, 2 Aug 2010 05:05:42 -0400 Message-ID: <20100802090542.GA32322@infradead.org> References: <20100802023322.GA19164@dastard> <20100802055834.GB19164@dastard> <20100802075537.GC7841@amd> <20100802082428.GA23135@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Dave Chinner , linux-fsdevel@vger.kernel.org, Linus Torvalds , Linux Kernel Mailing List To: Nick Piggin Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:46813 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752233Ab0HBJFq (ORCPT ); Mon, 2 Aug 2010 05:05:46 -0400 Content-Disposition: inline In-Reply-To: <20100802082428.GA23135@infradead.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Mon, Aug 02, 2010 at 04:24:28AM -0400, Christoph Hellwig wrote: > .36. I'd much rather see the inode_lock scaling or the lockless path > walk going in before, but I haven't checked how complicated the > reordering would be. The lockless path walk also is only rather > theoretically useful until we do ACL checks lockless as we're having > ACLs enabled pretty much everywhere at least in the distros. >>From a quick look it seems like the inode_lock splitup can easily be moved forward, and it would help us with doing some work on the writeback side. The problem is that it would need rebasing ontop of both the vfs and writeback (aka block) trees.