public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: [BK][PATCH] Reiser4, will double Linux FS performance, pleaseapply
Date: Fri, 1 Nov 2002 04:36:12 +0000 (UTC)	[thread overview]
Message-ID: <apt0bs$3sg$1@penguin.transmeta.com> (raw)
In-Reply-To: 3DC1D9D0.684326AC@digeo.com

In article <3DC1D9D0.684326AC@digeo.com>,
Andrew Morton  <akpm@digeo.com> wrote:
>
>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.

Andrew, that's not necessarily a _good_ feature. 

Journaling is _not_ a great idea.  There are other approaches to
handling atomicity than journaling, like phase trees, that give
equivalent atomicity guarantees without having to write out extra stuff,
or even impose a very strict ordering between data and meta-data.

I didn't read the reiser papers yet, but from Hans' description it
sounds like reiser4 gives all the guarantees ext3 does with ordered
writes, _and_ they get good performance. 

(In fact, from the description it sounds like it gives _more_ guarantees
than even ext3 with ordered writes, in that it gives transactional
behaviour for arbitrary writes. Maybe I should read the paper).

		Linus

  parent reply	other threads:[~2002-11-01  4:30 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-05 21:39     ` reiser
2002-11-01  1:27 ` Hans Reiser
2002-11-01  1:33   ` Andrew Morton
2002-11-01  1:44     ` Dieter Nützel
2002-11-01  4:36     ` Linus Torvalds [this message]
2002-11-01 10:59       ` Nikita Danilov
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-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-05  7:30 ` reiser
2002-11-05  8:28   ` Alexander Zarochentcev
2002-11-05  9:29   ` Andreas Dilger
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-05  8:44 ` reiser
2002-11-05  8:49   ` Alexander Zarochentcev
2002-11-05 21:08 ` reiser
     [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
  -- strict thread matches above, loose matches on Subject: below --
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='apt0bs$3sg$1@penguin.transmeta.com' \
    --to=torvalds@transmeta.com \
    --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