public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Chris Mason <mason@suse.com>, Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org, reiserfs-list@namesys.com,
	akpm@osdl.org
Subject: Re: I oppose Chris and Jeff's patch to add an unnecessary additional namespace to ReiserFS
Date: Tue, 27 Apr 2004 14:07:40 -0400	[thread overview]
Message-ID: <408EA16C.4030102@pobox.com> (raw)
In-Reply-To: <408E9F42.2080804@namesys.com>

Hans Reiser wrote:
> Christoph Hellwig wrote:
> 
>>> Did you notice that V4 blows XFS and ReiserFS V3 away in 
>>> benchmarks?    That is what I have been doing for 3 years....
>>>
>>> See www.namesys.com for details.
>>>   
>>
>>
>> see www.microsoft.com why Windows is much better than Linux.  Yeah, 
>> thanks.
>>  
>>
> Ask the users whether their laptops, etc.,  seem to go a lot faster with 
> V4.  They seem to be pretty happy with it.
> 
> V4 fixed all of V3's serious performance flaws, and totally obsoletes 
> it.    I am very happy with it.


For the present thread, this is irrelevant, as the irreverent responses 
hinted at:

Regardless of _any_ features or fixes in V4, reiserfs V3 will be used in 
production system for years.  Minor feature additions to an existing 
filesystem make it far easier for kernel engineers and sysadmins to 
assess the impact on their systems -- which is typically of less impact 
than switching to a new filesystem.

	Jeff




  parent reply	other threads:[~2004-04-27 18:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23 19:54 [PATCH] reiserfs v3 patches for 2.6.6-rc2 Chris Mason
2004-04-26 16:59 ` I oppose Chris and Jeff's patch to add an unnecessary additional namespace to ReiserFS Hans Reiser
2004-04-26 17:31   ` Chris Mason
2004-04-26 18:15     ` Hans Reiser
2004-04-26 19:12       ` Mark Hahn
2004-04-26 19:13       ` Chris Mason
2004-04-26 20:40         ` Matthias Andree
2004-04-26 22:20           ` Chris Wright
2004-04-26 23:20           ` Andrew Morton
2004-04-27 17:35           ` Hans Reiser
2004-04-27 18:00       ` Markus   Törnqvist
2004-04-26 19:33   ` Christoph Hellwig
2004-04-27 17:29     ` Hans Reiser
2004-04-27 17:34       ` Christoph Hellwig
2004-04-27 17:58         ` Hans Reiser
2004-04-27 18:04           ` Christoph Hellwig
2004-04-28  0:10             ` Stefan Traby
2004-04-27 18:07           ` Jeff Garzik [this message]
2004-04-28  5:51           ` Meelis Roos
2004-04-30 16:14           ` David Masover
2004-05-02  4:14           ` Rob Landley
2004-04-26 19:56   ` Matt H.

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=408EA16C.4030102@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.com \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=torvalds@osdl.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