From: Alex Tomas <alex@clusterfs.com>
To: Matt Mackall <mpm@selenic.com>
Cc: alex@clusterfs.com, ext2-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] extents,delayed allocation,mballoc for ext3
Date: Wed, 14 Apr 2004 16:05:18 +0400 [thread overview]
Message-ID: <m3llkyojcx.fsf@bzzz.home.net> (raw)
In-Reply-To: <20040414040101.GO1175@waste.org> (Matt Mackall's message of "Tue, 13 Apr 2004 23:01:02 -0500")
>>>>> Matt Mackall (MM) writes:
MM> I'm going to assume that there's no way for ext3 without extents
MM> support to mount such a filesystem, so I think this means changing the
MM> FS name. Is there a simple migration path to extents for existing filesystems?
yeah. you're right. I see no way to make it backward-compatible. in fact,
I haven't think much about name. probably you're right again and this
"ext3 on steroids" should have another name.
MM> Similar questions here.
no. this one is backward-compatible and usual ext3 will run ok.
btw, I think it possible to implement few routines that could allow
to exploit delayed allocation and multiblock allocator patches w/o
introducing extents. the most visible effect of the extents is much
faster truncate.
MM> You might also mention that on-disk format issues such as endian
MM> layout are not finalized.
yep. thanks for notice.
next prev parent reply other threads:[~2004-04-14 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 19:28 alex
2004-04-14 4:01 ` Matt Mackall
2004-04-14 12:05 ` Alex Tomas [this message]
2004-04-19 19:47 ` [Ext2-devel] " Stephen C. Tweedie
2004-04-20 22:05 ` Matt Mackall
2004-04-14 12:10 ` Alex Tomas
2004-04-14 17:49 ` [Ext2-devel] " Mingming Cao
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=m3llkyojcx.fsf@bzzz.home.net \
--to=alex@clusterfs.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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
Powered by JetHome