From: Nikita Danilov <Nikita@Namesys.COM>
To: bzzz@tmi.comex.ru
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] parallel directory operations
Date: Tue, 8 Jul 2003 17:29:33 +0400 [thread overview]
Message-ID: <16138.51005.54300.297204@laputa.namesys.com> (raw)
In-Reply-To: <874r1xuehd.fsf@gw.home.net>
bzzz@tmi.comex.ru writes:
> >>>>> Nikita Danilov (ND) writes:
>
>
> ND> By taking this approach one step further you may just add a semaphore
> ND> into struct dentry and take it instead of directory ->i_sem. I think
> ND> Alexander Viro tried something similar in the past, but it slowed down
> ND> common case when there is no concurrent access to the directory.
>
> it's not semaphore. locks are created on demand to protect part of directory.
> we can't have a lots of semaphores allocated statically for each part of
> each directory.
>
> BTW, all of this have to be enabled by 'pdirops' ext3's mount option. so, things
> don't slow down w/o this option.
I am talking about "dynamic locks" taken in fs/namei.c. Have you
measured how your patch affects single-threaded case?
>
Nikita.
next prev parent reply other threads:[~2003-07-08 13:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wuetukpa.fsf@gw.home.net.suse.lists.linux.kernel>
2003-07-08 11:26 ` Andi Kleen
2003-07-08 15:28 ` bzzz
2003-07-08 11:46 ` Andi Kleen
2003-07-08 15:50 ` bzzz
2003-07-08 12:11 ` Andi Kleen
2003-07-08 16:17 ` Alex Tomas
2003-07-08 13:11 ` Nikita Danilov
2003-07-08 17:15 ` bzzz
2003-07-08 13:29 ` Nikita Danilov [this message]
2003-07-08 17:38 ` Alex Tomas
2003-07-08 17:22 ` Andreas Dilger
2003-07-08 19:26 ` Andi Kleen
2003-07-08 15:01 Alex Tomas
2005-02-19 17:57 Alex Tomas
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=16138.51005.54300.297204@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=bzzz@tmi.comex.ru \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®