linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: "Anonymous Remailer (austria)" <mixmaster@remailer.privacy.at>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext5
Date: Wed, 10 Feb 2010 16:50:28 -0500	[thread overview]
Message-ID: <20100210215028.GD739@thunk.org> (raw)
In-Reply-To: <fe37fadb578fb9a3df9c878f8b9e9c3e@remailer.privacy.at>

On Wed, Feb 10, 2010 at 12:40:05AM +0100, Anonymous Remailer (austria) wrote:
> 
> will there be ext5? ext4 works just fine so far. but it could be
> even more faster. otherwise i have to jump to btrfs (when it's
> done).

We currently don't have any plans for an "ext5".  There might be some
new features that might gradually trickle into ext4; for example
there's someone who I may be mentoring who is interested in working on
an idea I've had to add read-only compression to ext4.  (Actually, the
design I've sketched out makes 90% of the work be file system
independent, so it's something that could be retrofitted into other
filesystems: xfs, btrfs, etc.)

The benchmarks I've seen don't show that btrfs is that much faster;
for some workloads its faster, for others its slower.  Of course,
there may be some file system tuning that still remains to be done,
both for btrfs and ext4, that may change the performance numbers
slightly.

The main reason why I suspect people will be interested in btrfs is to
because of some of its features (i.e., file system level snapshots,
data level checksums, etc.) that are unlikely to show up in ext4.  I
also suspect that btrfs will take a while to mature, as all file
systems do.  ZFS for example took good five years to development, and
perhaps another 3-4 before people started really trusting it for
critical production uses.

Regards,

						- Ted

  reply	other threads:[~2010-02-10 21:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09 23:40 ext5 Anonymous Remailer (austria)
2010-02-10 21:50 ` tytso [this message]
2010-02-11  3:38   ` ext5 Manish Katiyar
2010-02-11  4:30     ` ext5 tytso
2010-02-11 17:55       ` ext5 Jan Kara
2010-02-11 19:31         ` ext5 tytso
2010-02-11  5:18   ` ext5 Ron Johnson
2010-02-11  6:44     ` ext5 tytso
2010-02-11 16:49       ` ext5 Ron Johnson
2010-02-11 21:41       ` ext5 Goswin von Brederlow
2010-02-12  4:47         ` ext5 Ron Johnson
2010-02-12 16:02           ` ext5 tytso

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=20100210215028.GD739@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mixmaster@remailer.privacy.at \
    /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).