From: Shriramana Sharma <jamadagni@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: Ext4 improvements
Date: Sun, 07 Jan 2007 16:13:21 +0530 [thread overview]
Message-ID: <45A0CEC9.5060306@gmail.com> (raw)
Please be patient with my ignorance if what I am asking is meaningless
in any way. I am not too technically knowledgeable about filesystem
internals but I am willing to learn. (I thought of posting to linux-ext4
but did not want to intrude within the technical threads with my layman
thread.)
From Wikipedia > ReiserFS article > Design section:
[quote]ext2 and other Berkeley FFS-like filesystems simply use a fixed
formula for computing inode locations, hence limiting the number of
files they may contain. Most such filesystems also store directories as
simple lists of entries, which makes directory lookups and updates
linear time operations and degrades performance on very large
directories. The single B+ tree design in ReiserFS avoids both of these
problems due to better scalability properties.[/quote]
So will ext4 avoid both of these problems just like ReiserFS? Does it
use a B+ tree? Or this "dancing B* tree" that Reiser4 is supposed to have?
Also: I found that a newly created ext3 partition uses 128 MB whereas a
new reiser3 partition uses only 32 MB. I assume that the 128 MB is the
space taken for the pre-allocated inodes or such. And I now come to know
that others have this problem much more serious on bigger filesystems -
[see comment 2 at
http://linux.wordpress.com/2006/09/27/suse-102-ditching-reiserfs-as-it-default-fs/].
If ext4 uses a B+ (or B*?) tree like ReiserFS then this space can be
reduced, right?
Thanks.
Shriramana Sharma.
P.S: Are there any recommended tutorials for learning filesystem basics?
P.P.S: I just put this post here because I want to convert from reiserfs
of uncertain future to ext4, which is time-tested.
next reply other threads:[~2007-01-09 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-07 10:43 Shriramana Sharma [this message]
2007-01-10 11:46 ` Ext4 improvements Erik Mouw
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=45A0CEC9.5060306@gmail.com \
--to=jamadagni@gmail.com \
--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).