From: tytso@mit.edu
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [BK PATCH] Add ext3 indexed directory (htree) support
Date: Wed, 02 Oct 2002 05:11:59 -0400 [thread overview]
Message-ID: <E17wfXz-0000CK-00@think.thunk.org> (raw)
Hi Linus,
I believe the ext3 indexed directory (htree) patches are ready
for integration into the 2.5 tree at this point. Please pull them from:
bk://extfs.bkbits.net/for-linus-htree-2.5
Patches against 2.5.40 and 2.4.19 are available from:
http://thunk.org/tytso/linux/ext3-dxdir/patch-ext3-dxdir-2.5.40
and
http://thunk.org/tytso/linux/ext3-dxdir/patch-ext3-dxdir-2.4.19-4
This patch significantly increases the speed of using large directories
in ext3, in a completely backwards and forwards compatible
fashion. Creating 100,000 files in a single directory took 38 minutes
without directory indexing... and 11 seconds with the directory indexing
turned on.
Since the last time I've submitted this changeset to you, it's received
additional testing from the LKML list, and we've fixed few bugs in both
the kernel code and in e2fsprogs (please use e2fsprogs 1.30-WIP-0930
from sourceforge). In addition, the code paths are essentially
unchanged if the directory indexing filesystem feature flag is disabled.
Hence, this is a low risk patch to apply.
As before, existing filesystems can be updated to use directory indexing
by using the command "tune2fs -O dir_index /dev/hdXXX", and existing
large directories can be indexed by using the command "e2fsck -fD
/dev/hdXXX".
- Ted
fs/ext3/Makefile | 2
fs/ext3/dir.c | 299 +++++++++-
fs/ext3/file.c | 3
fs/ext3/hash.c | 215 +++++++
fs/ext3/namei.c | 1333 ++++++++++++++++++++++++++++++++++++++++-----
fs/ext3/super.c | 6
include/linux/ext3_fs.h | 86 ++
include/linux/ext3_fs_sb.h | 2
include/linux/ext3_jbd.h | 2
include/linux/rbtree.h | 1
lib/rbtree.c | 16
11 files changed, 1827 insertions(+), 138 deletions(-)
next reply other threads:[~2002-10-02 9:07 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 9:11 tytso [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-25 20:03 [BK PATCH] Add ext3 indexed directory (htree) support tytso
2002-09-25 20:34 ` Andreas Dilger
2002-09-25 20:41 ` Dave Jones
2002-09-25 21:08 ` Andreas Dilger
2002-09-25 21:34 ` Theodore Ts'o
2002-09-25 22:54 ` Jeff Garzik
2002-09-25 23:29 ` Theodore Ts'o
2002-09-25 23:45 ` Ryan Cumming
2002-09-26 3:27 ` Theodore Ts'o
2002-09-26 5:23 ` Ryan Cumming
2002-09-26 5:57 ` Theodore Ts'o
2002-09-26 6:22 ` Ryan Cumming
2002-09-26 14:05 ` Theodore Ts'o
2002-09-26 6:25 ` Ryan Cumming
2002-09-26 11:25 ` Daniel Egger
2002-09-26 7:41 ` Ryan Cumming
2002-09-26 13:23 ` Theodore Ts'o
2002-09-26 15:42 ` Theodore Ts'o
2002-09-26 19:08 ` Ryan Cumming
2002-09-26 19:51 ` Horst von Brand
2002-09-26 19:59 ` Ryan Cumming
2002-09-26 22:04 ` Theodore Ts'o
2002-09-26 22:53 ` Ryan Cumming
2002-09-26 23:57 ` Theodore Ts'o
2002-09-27 1:00 ` Ryan Cumming
2002-09-27 3:24 ` Theodore Ts'o
2002-09-27 4:12 ` Andreas Dilger
2002-09-27 7:55 ` Ryan Cumming
2002-09-28 1:20 ` Ryan Cumming
2002-09-28 1:46 ` Ryan Cumming
2002-09-28 14:13 ` Theodore Ts'o
2002-09-28 14:18 ` Theodore Ts'o
2002-09-28 22:35 ` Ryan Cumming
2002-09-28 22:30 ` Ryan Cumming
2002-09-25 23:31 ` Daniel Egger
2002-09-26 0:32 ` Randy.Dunlap
2002-09-26 0:50 ` Aaron Lehmann
2002-09-26 3:28 ` Theodore Ts'o
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=E17wfXz-0000CK-00@think.thunk.org \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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;
as well as URLs for NNTP newsgroup(s).