From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: Andrew Morton <akpm@digeo.com>, Hans Reiser <reiser@namesys.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Oleg Drokin <green@namesys.com>,
zam@namesys.com, umka <umka@thebsh.namesys.com>
Subject: Re: [BK][PATCH] Reiser4, will double Linux FS performance, pleaseapply
Date: Fri, 1 Nov 2002 02:44:44 +0100 [thread overview]
Message-ID: <200211010244.44970.Dieter.Nuetzel@hamburg.de> (raw)
In-Reply-To: <3DC1D9D0.684326AC@digeo.com>
Am Freitag, 1. November 2002 02:33 schrieb Andrew Morton:
> Hans Reiser wrote:
> > Well, if we are only 2.5 times as fast for writes as ext3 after your
> > patch is applied, I'll still feel good.;-)
>
> whupping ext3's butt on write performance isn't very hard, really ;)
>
> But it should be done based on "feature equivalency". By default,
> ext3 uses ordered data writes. Data is written to disk before
> the metadata to which that data refers is committed to journal.
>
> It would be questionable to compare a metadata-only journalling
> approach to ext3 with data=journal or data=ordered.
As I understood it Reiser4 would have that from the beginning.
It is all new and not ReiserFS v3 which get this with Chris's data-logging
patches delayed for 2.4.21/2.5.45+.
Plugins for encryption, ACLs, etc are in the works.
-Dieter
next prev parent reply other threads:[~2002-11-01 1:38 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 21:23 [BK][PATCH] Reiser4, will double Linux FS performance, please apply Hans Reiser
2002-10-31 22:34 ` Dieter Nützel
2002-10-31 22:47 ` Hans Reiser
2002-11-01 1:17 ` [BK][PATCH] Reiser4, will double Linux FS performance, pleaseapply Andrew Morton
2002-11-01 1:27 ` Andrew Morton
2002-11-01 1:27 ` Hans Reiser
2002-11-01 1:33 ` Andrew Morton
2002-11-01 1:44 ` Dieter Nützel [this message]
2002-11-01 1:55 ` Hans Reiser
2002-11-01 10:23 ` Tomas Szepe
2002-11-01 17:19 ` Alexander Zarochentcev
2002-11-02 13:24 ` Tomas Szepe
2002-11-04 11:00 ` Nikita Danilov
2002-11-04 19:56 ` Andreas Dilger
2002-11-05 7:30 ` reiser
2002-11-05 8:28 ` Alexander Zarochentcev
2002-11-05 8:44 ` reiser
2002-11-05 8:49 ` Alexander Zarochentcev
2002-11-05 21:08 ` reiser
2002-11-05 9:29 ` Andreas Dilger
2002-11-05 21:39 ` reiser
2002-11-05 9:59 ` Tomas Szepe
2002-11-05 10:08 ` Alexander Zarochentcev
2002-11-05 10:23 ` Tomas Szepe
2002-11-05 10:46 ` Nikita Danilov
2002-11-02 13:38 ` Tomas Szepe
2002-11-04 12:02 ` Nikita Danilov
2002-11-04 17:10 ` Tomas Szepe
2002-11-04 17:53 ` Nikita Danilov
2002-11-04 18:10 ` Tomas Szepe
2002-11-01 4:36 ` Linus Torvalds
2002-11-01 10:59 ` Nikita Danilov
[not found] <877555917@toto.iv>
2002-11-05 23:09 ` Peter Chubb
2002-11-06 1:33 ` reiser
2002-11-06 14:25 ` Daniel Egger
2002-11-07 17:19 ` Pavel Machek
2002-11-07 16:58 ` Bill Davidsen
2002-11-06 18:37 Tom Reinhart
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=200211010244.44970.Dieter.Nuetzel@hamburg.de \
--to=dieter.nuetzel@hamburg.de \
--cc=akpm@digeo.com \
--cc=green@namesys.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=umka@thebsh.namesys.com \
--cc=zam@namesys.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
all inboxes | Powered by JetHome®