From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christoph Hellwig <hch@infradead.org>
Subject: Re: VFS scalability git tree
Date: Tue, 14 Sep 2010 18:26:12 -0400
Message-ID: <20100914222612.GA23871@infradead.org>
References: <20100722190100.GA22269@amd>
 <20100730091226.GA10437@amd>
 <1280795279.3966.47.camel@localhost.localdomain>
 <20100803054400.GA7398@amd>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
To: Nick Piggin <npiggin@suse.de>
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <20100803054400.GA7398@amd>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

Nick,

what's the plan for going ahead with the VFS scalability work?  We're
pretty late in the 2.6.36 cycle now and it would be good to get the next
batch prepared and reivew so that it can get some testing in -next.

As mentioned before my preference would be the inode lock splitup and
related patches - they are relatively simple and we're already seeing
workloads where inode_lock really hurts in the writeback code.