All of lore.kernel.org
 help / color / mirror / Atom feed
From: mjt@nysv.org
To: Hans Reiser <reiser@namesys.com>
Cc: Russell Treleaven <rtreleaven@chantrynetworks.com>,
	ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: Reiser4 status as of this weekend
Date: Sun, 16 May 2004 01:10:17 +0300	[thread overview]
Message-ID: <20040515221017.GL1232@nysv.org> (raw)
In-Reply-To: <40A68F75.2030306@namesys.com>

On Sat, May 15, 2004 at 02:45:25PM -0700, Hans Reiser wrote:

>Some users are saying that it is rock solid (please contradict dear 
>readers).  We the developers can use iozone to make it crash by mmapping 

I haven't had problems for a long time.

Then again, I haven't used iozone ever.

>well structured for managing memory under that circumstance.   The clean 
>fix for that for reiser4 given the way the Linux design is,  is 
>substantial work to do right, and is in progress.  We currently have a 
>fix that costs performance, and are fixing the performance issue (which 
>is fixable but requires code....).

Would you say this is the biggest issue?
What about NFS?

>We would probably have it ready to ship this week, but Nikita is leaving 
>Namesys after having done a great job here for way too little pay, and 

!!!
This is terrible news... I'm sorry, I'm at a loss of words...

Nikita, hope to see you on IRC still and thanks for all the great
work and the help you've given me and everyone else.

Best of luck.

>that means we need to have him and Saveliev spend a full week doing a 
>code review before he goes, and Zam and I are busy earning the next 
>month payroll money by doing work for digeo, and such is the free 
>software "business".  Sigh.

This may be a tactless question, but what about the grant for implementing
views? It was insufficient?

Have you also considered making it easier for the community to write code?
I'm not talking about write-access handed liberally to bitkeeper, but
maybe some coding guide and stuff could be more prominently available?

>So, stay tuned, and check again in two weeks.

Best of luck to the rest of you too.

-- 
mjt


  parent reply	other threads:[~2004-05-15 22:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <003a01c4377d$d653eac0$7d02a8c0@toronto.chantrynetworks.com>
2004-05-15 21:45 ` Reiser4 status as of this weekend Hans Reiser
2004-05-15 21:56   ` Redeeman
2004-05-15 22:10   ` mjt [this message]
2004-05-16 17:30     ` Hans Reiser
2004-05-19 19:50       ` mjt
2004-05-20  9:39         ` Vladimir Saveliev
2004-05-20 17:37           ` Hans Reiser
2004-05-20  9:45         ` Matthias Andree
2004-05-15 23:27   ` Christian
2004-05-16  0:07     ` David Masover

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=20040515221017.GL1232@nysv.org \
    --to=mjt@nysv.org \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=rtreleaven@chantrynetworks.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.