From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: bzzz@tmi.comex.ru, linux-kernel@vger.kernel.org,
ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] Re: [RFC] file extents for EXT3
Date: Mon, 11 Aug 2003 09:43:04 -0700 [thread overview]
Message-ID: <20030811094304.10369817.rddunlap@osdl.org> (raw)
In-Reply-To: <3F3791C8.4090903@pobox.com>
On Mon, 11 Aug 2003 08:53:28 -0400 Jeff Garzik <jgarzik@pobox.com> wrote:
| Alex Tomas wrote:
| > hello all!
| >
| > there are several problems with old good method ext2/ext3
| > use to store map of block for an inode. for example, ext3's
| > truncate is quite slow. I think extents could solve this
| > and some other troubles. so ...
| >
| >
| > in fact, design is taken from htree modern ext2/ext3 uses. in constrast with
| > htree, it isn't backward-compatible.
|
| Neat. I really like extents, and think this is the best long-term
| approach. Apparently the ext3 maintainers do, too, because tytso/sct's
| "ext roadmap" paper publishing a while ago describes extents, too. (I
| wish I had a URL for that)
like this? http://www.usenix.org/publications/library/proceedings/usenix02/tech/freenix/tso.html
--
~Randy For Linux-2.6, see:
http://www.kernel.org/pub/linux/kernel/people/davej/misc/post-halloween-2.5.txt
prev parent reply other threads:[~2003-08-11 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 7:41 [RFC] file extents for EXT3 Alex Tomas
2003-08-11 12:53 ` Jeff Garzik
2003-08-11 15:55 ` Andreas Dilger
2003-08-11 16:23 ` Jeff Garzik
2003-08-12 9:33 ` Rob Landley
2003-08-12 15:14 ` Andreas Dilger
2003-08-12 21:09 ` Rob Landley
2003-08-13 4:32 ` [Ext2-devel] " Theodore Ts'o
2003-08-14 16:41 ` James Antill
2003-08-11 16:43 ` Randy.Dunlap [this message]
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=20030811094304.10369817.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=bzzz@tmi.comex.ru \
--cc=ext2-devel@lists.sourceforge.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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).