From: wangdi <di.wang@whamcloud.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org,
Jinshan Xiong <jinshan.xiong@whamcloud.com>
Subject: [LSF/MM TOPIC] Parallelize file operation (like creation, unlink) under large shared directory
Date: Sat, 21 Jan 2012 12:54:42 -0800 [thread overview]
Message-ID: <4F1B2612.7020001@whamcloud.com> (raw)
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.
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.
Thanks
WangDi
next reply other threads:[~2012-01-21 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 20:54 wangdi [this message]
2012-01-22 13:55 ` [LSF/MM TOPIC] Parallelize file operation (like creation, unlink) under large shared directory Boaz Harrosh
2012-01-22 20:31 ` wangdi
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=4F1B2612.7020001@whamcloud.com \
--to=di.wang@whamcloud.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