All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Schäfer" <gentryx@gmx.de>
To: Hans Reiser <reiser@namesys.com>
Cc: Jonathan Briggs <jbriggs@esoft.com>, reiserfs-list@namesys.com
Subject: Re: State of the Reiser4 FS
Date: Wed, 15 Mar 2006 22:25:54 +0100	[thread overview]
Message-ID: <20060315212554.GA17098@wintermute> (raw)
In-Reply-To: <44187C8D.5050105@namesys.com>

On 12:43 Wed 15 Mar     , Hans Reiser wrote:
> I am the reiserfs/reiser4 sub-maintainer.  So, if reiser4 works well,
> and is faster than any other Linux FS, and it is,  maintaining it over
> time is for me to worry about, not them. 

I feel this thread is about to trail off to shores we all know too
well. AFAICS we do have two completely different issues here: 

* The core maintainers want the whole code to adhere to certain
  standards. This doesn't have anything to do with performance
  etc. It's just for the fact that this standard is both, a sign of
  reliability and maintainability (even for the unlikely case that
  Namesys would disappear)

* Reiser4 doesn't adhere to some of these standards because they don't
  make much sense from a performance (and design) point of view. 

I think the short term solution should be to adapt Reiser4 to the
standard, but in the long run keep bugging the Linux people to change
some paradigms (as one of Linux' core advantages has always been the
ability and willingness to throw decayed code overboard).

When you think about it, both POV do make sense. It's just so sad this
whole debate has become much more a political than a style debate.

-Andreas


  reply	other threads:[~2006-03-15 21:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-14 10:41 State of the Reiser4 FS Avuton Olrich
2006-03-14 11:45 ` Vladimir V. Saveliev
2006-03-14 15:32   ` Clemens Eisserer
2006-03-15  7:14     ` Hans Reiser
2006-03-15  8:57       ` Andreas Schäfer
2006-03-15 18:29         ` Hans Reiser
2006-03-15 19:27           ` Andreas Schäfer
2006-03-15 21:08             ` Andreas Dilger
2006-03-16  0:58             ` 4k at a time only works well for an OS that does less per iteration than Linux does Hans Reiser
2006-03-15 19:45       ` State of the Reiser4 FS Jonathan Briggs
2006-03-15 20:43         ` Hans Reiser
2006-03-15 21:25           ` Andreas Schäfer [this message]
2006-03-15  8:45 ` Hans Reiser
2006-03-15 12:59   ` Avuton Olrich
2006-03-15 18:33     ` Hans Reiser
2006-03-26 11:27       ` 2.6.16 patch jp
2006-03-27 17:27         ` jp
2006-03-28 11:42           ` Vladimir V. Saveliev
2006-03-28 12:54             ` Tassilo Horn
2006-03-28 17:12               ` Danny Milosavljevic
2006-03-28 18:00                 ` Tassilo Horn
2006-03-28 23:22             ` Jake Maciejewski
2006-03-27 20:10         ` Marcus Furlong
2006-03-27 19:44           ` Tassilo Horn
2006-03-27 21:32             ` Marcus Furlong
2006-03-27 20:41               ` Tassilo Horn
2006-03-27 21:29               ` Tassilo Horn

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=20060315212554.GA17098@wintermute \
    --to=gentryx@gmx.de \
    --cc=jbriggs@esoft.com \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.