public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Ed Sweetman <ed.sweetman@wmich.edu>
Cc: 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, 29 Aug 2003 14:39:40 -0700	[thread overview]
Message-ID: <20030829213940.GC3846@matchmail.com> (raw)
In-Reply-To: <3F4FAFA2.4080202@wmich.edu>

On Fri, Aug 29, 2003 at 03:55:14PM -0400, Ed Sweetman wrote:
> I would not recommend using the patch for system directories only 
> because it leaves you with no way to rescue the system and does very 
> little in the way of performance for those directories. Ext3 is 
> backwards compatible with ext2, this patch seemingly breaks that. 
> Because of that it doesn't seem to be ext3 anymore, rather a one way 
> compatibility with ext3 with a purely large media bias.

Do you get any slowdown with the extents on small files though?

The plan is to add extent reading code to the three other stable trees so
that at the very least you could have read-only access to the extent based
ext2/3.

Remember, if the implementation of journaling hadn't have been so extensive,
we wouldn't have an ext3, but ext2 with journaling (and called ext2).

So what this will be is ext2 format with extents, and with (ext3) or without
journaling (ext2).

And this is planned for 2.7, so if anything goes into 2.6, it'll be
read-only support of extents.

  reply	other threads:[~2003-08-29 21:39 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                       ` Mike Fedyk [this message]
2003-08-29 22:25                         ` [Ext2-devel] " 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
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=20030829213940.GC3846@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=bzzz@tmi.comex.ru \
    --cc=ed.sweetman@wmich.edu \
    --cc=ext2-devel@lists.sourceforge.net \
    --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