From: Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
To: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
Subject: Re: How does NILFS2 handle directory management
Date: Thu, 24 Sep 2009 17:49:09 +0900 [thread overview]
Message-ID: <87hbusbud6.wl%jir@sekiba.com> (raw)
In-Reply-To: <20090914102731.GA154-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
Hi,
At Mon, 14 Sep 2009 12:27:31 +0200,
Reinoud Zandijk wrote:
> > I think it should be considered along with ext3 approach.
>
> What is is the ext3 approach? What is different compared to ext2? And is it
> really such a big improvement? Will it complicate directory reading/writing
> more?
ext3 approach is a hashed index for file names, stored on disk.
So it always costs constant time to lookup the block filename stored.
The point is that this hashed index extension preserve backward compatibility,
which means that code which does not know about hashed index still be
able to read the directory entry as usual.
The improvement of this was significant compared with ext2.
I re-put up the following benchmark results.
http://plaza18.mbn.or.jp/~moriban/linux/img/FileSystemBenchmarkResults-01-03.png
# There may be more reliable benchmark result, but I cound't find it.
There are some documents for further information if you are interested in.
- A Directory Index for Ext2
http://ols.fedoraproject.org/OLS/Reprints-2002/phillips-reprint.pdf
- [RFC] Ext2 Directory Index - File Structure
http://lwn.net/2001/0412/a/index-format.php3
- [rfc] Near-constant time directory index for Ext2
http://search.luky.org/linux-kernel.2001/msg00117.html
thanks,
regards,
--
Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
next prev parent reply other threads:[~2009-09-24 8:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 19:16 How does NILFS2 handle directory management Prasenjit Giri
[not found] ` <2324ff2b0909101216q31dad1a8y43ea0f229923a0c3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-10 19:26 ` Reinoud Zandijk
[not found] ` <20090910192619.GA1263-bVHBekiX4bNgoMqBc1r0ESegHCQxtGRMHZ5vskTnxNA@public.gmane.org>
2009-09-11 1:21 ` Ryusuke Konishi
[not found] ` <20090911.102118.69189169.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-09-11 3:48 ` Jiro SEKIBA
[not found] ` <873a6u16qy.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2009-09-11 4:13 ` Ryusuke Konishi
2009-09-11 3:58 ` Prasenjit Giri
[not found] ` <2324ff2b0909102058g1ee407fco3f2482b4732dacca-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-11 6:23 ` Ryusuke Konishi
2009-09-11 5:22 ` Reinoud Zandijk
[not found] ` <20090911052213.GA24899-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2009-09-11 6:44 ` Ryusuke Konishi
[not found] ` <20090911.154452.43227079.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-09-14 10:27 ` Reinoud Zandijk
[not found] ` <20090914102731.GA154-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2009-09-24 8:49 ` Jiro SEKIBA [this message]
[not found] ` <87hbusbud6.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2009-09-25 12:21 ` Reinoud Zandijk
[not found] ` <20090925122109.GD6624-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2009-09-25 15:47 ` Ryusuke Konishi
[not found] ` <20090926.004730.113223425.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-09-25 16:23 ` Reinoud Zandijk
[not found] ` <20090925162334.GA14945-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2009-09-26 1:16 ` Ryusuke Konishi
[not found] ` <20090926.101634.31873031.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-09-27 22:10 ` Reinoud Zandijk
[not found] ` <20090927221049.GA14618-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2009-09-27 23:03 ` Jiro SEKIBA
2009-09-27 11:34 ` Jiro SEKIBA
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=87hbusbud6.wl%jir@sekiba.com \
--to=jir-hfpbi5wx9j54eiagz67ipq@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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