From: Jan Kara <jack@suse.cz>
To: linux-ext4@vger.kernel.org
Subject: Enabling h-trees too early?
Date: Wed, 19 Sep 2007 17:07:15 +0200 [thread overview]
Message-ID: <20070919150715.GH9232@duck.suse.cz> (raw)
Hi,
I was just wondering: Currently we start to build h-tree in a directory
already when the size of directory exceeds one block. But honestly, it does
not seem to make much sence to use this feature until the directory is much
larger (I'd say at least 16 or 32 KB). It actually slows down some
operations like deleting the whole directory, etc. So what is the reason
for starting building the tree so early? Just the simplicity of building it
when the directory is just one block large?
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next reply other threads:[~2007-09-19 14:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 15:07 Jan Kara [this message]
2007-09-19 17:02 ` Enabling h-trees too early? Andreas Dilger
2007-09-19 18:24 ` Theodore Tso
2007-09-20 13:33 ` Jan Kara
2007-09-20 14:28 ` Theodore Tso
2007-09-20 14:58 ` Jan Kara
2007-09-20 15:14 ` Theodore Tso
2007-09-20 16:19 ` Jan Kara
2007-09-20 17:02 ` Theodore Tso
2007-09-21 13:49 ` Jan Kara
2007-09-21 9:02 ` Andi Kleen
2007-09-21 11:45 ` Theodore Tso
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=20070919150715.GH9232@duck.suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).