From: Ed Tomlinson <tomlins@cam.org>
To: Andi Kleen <ak@suse.de>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] New dcache / inode hash tuning patch
Date: Sat, 1 Mar 2003 07:34:44 -0500 [thread overview]
Message-ID: <200303010734.45441.tomlins@cam.org> (raw)
In-Reply-To: <20030301090839.GA11997@wotan.suse.de>
On March 1, 2003 04:08 am, Andi Kleen wrote:
> > I wonder what would happen if you reordered the chains moving a 'found'
> > dentry to the front of the chain? If this could be done without
> > excessive locking it might help keep hot entries quickly accessable.
> > This operation should be cheaper given you are using hlists.
>
> You would need to fetch a spinlock for LRU, while the current lookup
> runs completely lockless.
You would have to lock the chain IF the dentry was not at the head. Would
be interesting to see if this locking would hurt much - since hot
dentries would not require a lock...
Ed
next prev parent reply other threads:[~2003-03-01 12:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030226164904.GA21342@wotan.suse.de.suse.lists.linux.kernel>
[not found] ` <b3m5sd$1ad$1@penguin.transmeta.com.suse.lists.linux.kernel>
2003-02-28 8:34 ` [PATCH] New dcache / inode hash tuning patch Andi Kleen
2003-02-28 10:27 ` [Lse-tech] " Paul Menage
2003-02-28 10:40 ` Andi Kleen
2003-02-28 18:47 ` Linus Torvalds
2003-02-28 18:59 ` Andi Kleen
2003-03-01 0:49 ` Jan Harkes
2003-03-01 1:17 ` Andi Kleen
2003-03-01 4:31 ` Ed Tomlinson
2003-03-01 9:08 ` Andi Kleen
2003-03-01 12:34 ` Ed Tomlinson [this message]
2003-03-01 18:34 ` Linus Torvalds
2003-02-26 16:49 Andi Kleen
2003-02-27 23:10 ` Linus Torvalds
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=200303010734.45441.tomlins@cam.org \
--to=tomlins@cam.org \
--cc=ak@suse.de \
--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