From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id q1L4x6WW144681 for ; Mon, 20 Feb 2012 22:59:07 -0600 Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by cuda.sgi.com with ESMTP id pkMoMTASY5YVukDp for ; Mon, 20 Feb 2012 20:59:05 -0800 (PST) Date: Tue, 21 Feb 2012 15:58:11 +1100 From: Dave Chinner Subject: Re: [PATCH 1/8] xfs: use per-filesystem I/O completion workqueues Message-ID: <20120221045811.GJ3592@dastard> References: <20120221003824.415885674@bombadil.infradead.org> <20120221003906.124899527@bombadil.infradead.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20120221003906.124899527@bombadil.infradead.org> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Christoph Hellwig Cc: xfs@oss.sgi.com On Mon, Feb 20, 2012 at 07:38:25PM -0500, Christoph Hellwig wrote: > The new concurrency managed workqueues are cheap enough that we can create > per-filesystem instead of global workqueues. This allows us to remove the > trylock or defer scheme on the ilock, which is not helpful once we have > outstanding log reservations until finishing a size update. > > Also allow the default concurrency on this workqueues so that I/O completions > blocking on the ilock for one inode do not block process for another inode. > > Signed-off-by: Christoph Hellwig Looks good. Reviewed-by: Dave Chinner -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs