From: William Lee Irwin III <wli@holomorphy.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [rfc][patch] dynamic resizing dentry hash using RCU
Date: Sat, 24 Feb 2007 14:56:31 -0800 [thread overview]
Message-ID: <20070224225631.GA9222@holomorphy.com> (raw)
In-Reply-To: <20070224050937.GA16601@wotan.suse.de>
On Fri, Feb 23, 2007 at 08:24:44PM -0800, William Lee Irwin III wrote:
>> You would be better served by a data structure different from a hashtable.
On Sat, Feb 24, 2007 at 06:09:37AM +0100, Nick Piggin wrote:
> Out of curiosity, what better data structure do you have in mind for
> the dentry hash?
Per-directory indices of ->d_subdirs. Hash tries (spelled correctly)
and B+ trees hung off dentries corresponding to directories are
plausible. There are plenty of other possibilities; just do it on a
per-directory basis so you don't intermix children of different parents
in some boot-time -allocated global trainwreck and you're home free.
Benchmarking is probably needed to gauge which performs best.
-- wli
next prev parent reply other threads:[~2007-02-24 22:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 15:37 [rfc][patch] dynamic resizing dentry hash using RCU Nick Piggin
2007-02-23 16:31 ` Eric Dumazet
2007-02-24 1:08 ` Nick Piggin
2007-02-23 17:25 ` Zach Brown
2007-02-24 1:26 ` Nick Piggin
2007-02-24 2:07 ` Nick Piggin
2007-02-24 1:31 ` Michael K. Edwards
2007-02-24 1:52 ` Nick Piggin
2007-02-24 4:07 ` KAMEZAWA Hiroyuki
2007-02-24 5:15 ` Nick Piggin
2007-02-24 4:24 ` William Lee Irwin III
2007-02-24 5:09 ` Nick Piggin
2007-02-24 22:56 ` William Lee Irwin III [this message]
2007-02-25 0:56 ` David Miller
2007-02-25 2:15 ` William Lee Irwin III
2007-02-25 6:21 ` Paul E. McKenney
2007-03-05 4:11 ` David Miller
2007-03-05 4:27 ` Nick Piggin
2007-03-05 4:38 ` David Miller
2007-03-05 4:42 ` Nick Piggin
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=20070224225631.GA9222@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
/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.