From: wangdi <di.wang@whamcloud.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
Jinshan Xiong <jinshan.xiong@whamcloud.com>
Subject: Re: [LSF/MM TOPIC] Parallelize file operation (like creation, unlink) under large shared directory
Date: Sun, 22 Jan 2012 12:31:31 -0800 [thread overview]
Message-ID: <4F1C7223.3040301@whamcloud.com> (raw)
In-Reply-To: <4F1C1556.7010908@panasas.com>
On 01/22/2012 05:55 AM, Boaz Harrosh wrote:
> On 01/21/2012 10:54 PM, wangdi wrote:
>> Single directory performance is a critical in some use cases. For
>> example the multiple application threads might create hundreds of
>> thousands of files in a single directory simultaneously within a short
>> window of time.
>>
> read NFSD here ;-)
>
>> Currently, both filename lookup and file system modifying operations
>> (such as create and unlink) are protected with a single lock for the
>> entire directory. It might be useful to remove this lock, so multiple
>> application threads can access the directory simultaneously.
>>
> I agree about create, unlink, and so on. But don't we have some lockless
> look up in place since a few Kernels ago?
The lockless lookup is only for lookups in the dcache and not in the backing filesystem, which is serialized by i_mutex in the VFS(real_lookup).
> But yes the topic is very interesting, though I'd suspect its hard to
> implement.
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.
Thanks
WangDi
>> Thanks
>> WangDi
>>
> Thanks
> Boaz
next prev parent reply other threads:[~2012-01-22 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 20:54 [LSF/MM TOPIC] Parallelize file operation (like creation, unlink) under large shared directory wangdi
2012-01-22 13:55 ` Boaz Harrosh
2012-01-22 20:31 ` wangdi [this message]
2012-01-22 20:39 ` Al Viro
2012-01-22 21:17 ` wangdi
2012-01-24 8:53 ` Dave Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F1C7223.3040301@whamcloud.com \
--to=di.wang@whamcloud.com \
--cc=bharrosh@panasas.com \
--cc=jinshan.xiong@whamcloud.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox