From: Matthew Wilcox <willy@debian.org>
To: linux-fsdevel@vger.kernel.org, Alexander Viro <viro@math.psu.edu>
Subject: Re: inode rwlock instead of semaphore
Date: Sun, 2 Feb 2003 17:42:15 +0000 [thread overview]
Message-ID: <20030202174215.G21040@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030202100155.A18636@schatzie.adilger.int>; from adilger@clusterfs.com on Sun, Feb 02, 2003 at 10:01:55AM -0700
On Sun, Feb 02, 2003 at 10:01:55AM -0700, Andreas Dilger wrote:
> I'm wondering why we use a semaphore to lock directories on lookups instead
> of a rwlock? This would allow parallel lookups on directory entries instead
> of single threading. We have a need for directories with millions of files
> in them, and being able to start parallel lookups would be a big performance
> boost I think.
You mean a rwsem, not a rwlock, I assume? How about starvation issues?
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-02-02 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-02 17:01 inode rwlock instead of semaphore Andreas Dilger
2003-02-02 17:42 ` Matthew Wilcox [this message]
2003-02-02 22:32 ` Andrew Morton
2003-02-03 13:13 ` Jan Hudec
2003-02-03 17:47 ` Andreas Dilger
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=20030202174215.G21040@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.