From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
"Dave Jones" <davej@redhat.com>,
reiserfs-dev@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: [STACK] >3k call path in reiserfs
Date: Fri, 11 Jun 2004 13:46:45 -0400 [thread overview]
Message-ID: <1086976005.10973.364.camel@watt.suse.com> (raw)
In-Reply-To: <40C9DE9F.90901@namesys.com>
On Fri, 2004-06-11 at 12:32, Hans Reiser wrote:
> Reiser4 is going to obsolete V3 in a few weeks. V3 will be retained for
> compatibility reasons only, as V4 blows it away in performance.
>
This would be the conservative release management you were talking about
before, right? It's going to take a considerable amount of time for v4
to obsolete v3, because it will take a considerable amount of time for
v4 to become stable under the wide range of conditions that filesystems
get used.
Please don't misunderstand this as a statement against v4, I would love
to see it be 1000x as fast as every other FS. I'm only asking for some
kind of realism in the expectations you give the users.
-chris
next prev parent reply other threads:[~2004-06-11 17:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 12:22 Jörn Engel
2004-06-09 12:31 ` Chris Mason
2004-06-09 16:53 ` Chris Mason
2004-06-09 17:06 ` Hans Reiser
2004-06-09 17:15 ` Chris Mason
2004-06-09 18:04 ` Hans Reiser
2004-06-09 18:20 ` Dave Jones
2004-06-09 23:40 ` Hans Reiser
2004-06-10 22:35 ` Jörn Engel
2004-06-11 2:49 ` Hans Reiser
2004-06-11 7:03 ` Arjan van de Ven
2004-06-11 13:46 ` Jörn Engel
2004-06-11 16:32 ` Hans Reiser
2004-06-11 16:50 ` Jörn Engel
2004-06-11 17:08 ` Paul Wagland
2004-06-11 17:46 ` Chris Mason [this message]
2004-06-11 18:07 ` Hans Reiser
2004-06-11 14:31 ` Timothy Miller
2004-06-11 14:42 ` Jörn Engel
2004-06-09 17:28 ` Jörn Engel
2004-06-09 18:09 ` Hans Reiser
2004-06-09 18:34 ` Jörn Engel
2004-06-09 23:42 ` Hans Reiser
2004-06-11 13:49 ` Jörn Engel
2004-06-11 16:34 ` Hans Reiser
2004-06-09 18:48 ` Chris Mason
2004-06-09 18:53 ` Jörn Engel
2004-06-09 23:44 ` Hans Reiser
2004-06-10 9:08 ` Vladimir Saveliev
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=1086976005.10973.364.camel@watt.suse.com \
--to=mason@suse.com \
--cc=davej@redhat.com \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=reiserfs-dev@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®