From: Pavel Machek <pavel@ucw.cz>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Mike Fedyk <mfedyk@matchmail.com>,
Ed Sweetman <ed.sweetman@wmich.edu>,
Alex Tomas <bzzz@tmi.comex.ru>,
linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] Re: [RFC] extents support for EXT3
Date: Fri, 5 Sep 2003 12:06:07 +0200 [thread overview]
Message-ID: <20030905100607.GA220@elf.ucw.cz> (raw)
In-Reply-To: <m18yp9r2uq.fsf@ebiederm.dsl.xmission.com>
Hi!
> > > you get no real slowdown as far as rough benchmarks are concerned,
> > > perhaps with a microbenchmark you would see one and also, doesn't it
> > > take up more space to save the extent info and such? Either way, all of
> > > it's real benefits occur on large files.
> >
> > IIRC, if your blocks are contiguous, you can save as soon as soon as the
> > file size goes above one block (witout extents, the first 12 blocks are
> > pointed to by what? I forget... :-/ )
>
> They are pointed to directly from the inode.
>
> In light of other concerns how reasonable is a switch to e2fsck that
> will remove extents so people can downgrade filesystems?
It is going to be non-trivial: downgrading filesystem will likely need
free space. And now: what happens when there's no free space?
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-09-05 10:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 8:22 [RFC] extents support for EXT3 Alex Tomas
2003-08-28 17:22 ` [Ext2-devel] " Mike Fedyk
2003-08-29 5:55 ` Alex Tomas
2003-08-28 18:12 ` Ed Sweetman
2003-08-29 5:59 ` Alex Tomas
2003-08-29 15:28 ` Ed Sweetman
2003-08-29 15:38 ` Alex Tomas
2003-08-29 15:52 ` Ed Sweetman
2003-08-29 16:10 ` Alex Tomas
2003-08-29 16:16 ` Alex Tomas
2003-08-29 16:20 ` Ed Sweetman
2003-08-29 16:34 ` Alex Tomas
2003-08-29 17:49 ` Ed Sweetman
2003-08-29 18:09 ` Alex Tomas
2003-08-29 19:55 ` Ed Sweetman
2003-08-29 21:39 ` [Ext2-devel] " Mike Fedyk
2003-08-29 22:25 ` Ed Sweetman
2003-08-29 23:17 ` Mike Fedyk
2003-08-31 20:25 ` Eric W. Biederman
2003-08-31 20:37 ` Alex Tomas
2003-09-05 10:06 ` Pavel Machek [this message]
2003-09-05 14:55 ` Eric W. Biederman
2003-08-30 9:09 ` Alex Tomas
2003-08-30 8:55 ` Alex Tomas
2003-08-30 10:13 ` Alex Tomas
2003-08-28 22:00 ` Ramón Rey Vicente
2003-08-29 6:04 ` Alex Tomas
2003-08-29 9:55 ` Ramón Rey Vicente
2003-09-06 0:19 ` jw schultz
2003-09-06 6:09 ` Alex Tomas
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=20030905100607.GA220@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=bzzz@tmi.comex.ru \
--cc=ebiederm@xmission.com \
--cc=ed.sweetman@wmich.edu \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.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).