From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [LSF/MM TOPIC] Parallelize file operation (like creation, unlink) under large shared directory Date: Sun, 22 Jan 2012 20:39:36 +0000 Message-ID: <20120122203936.GE23916@ZenIV.linux.org.uk> References: <4F1B2612.7020001@whamcloud.com> <4F1C1556.7010908@panasas.com> <4F1C7223.3040301@whamcloud.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Boaz Harrosh , lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org, Jinshan Xiong To: wangdi Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:46209 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752350Ab2AVUjn (ORCPT ); Sun, 22 Jan 2012 15:39:43 -0500 Content-Disposition: inline In-Reply-To: <4F1C7223.3040301@whamcloud.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sun, Jan 22, 2012 at 12:31:31PM -0800, wangdi wrote: > We actually already implemented this for ext4, and we saw a lot performance improvement(at least 30% improvements for open/create in a single directory)for lustre stack, > but we want to make this improvement accessible through the VFS. Probably XFS and Btrfs could also benefit from this. You do realize that i_mutex locking is relied upon for protection of a lot of stuff besides the obvious (i.e. on-disk directory contents)? I'm not saying that it's hopeless, but it's highly non-trivial; the things like rmdir/mount races, access to ->d_parent/->d_name in a lot of code, etc. need to be taken care of and it is a _lot_ of code review to deal with - just to verify the correctness of such changes.