From: Hans Reiser <reiser@namesys.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Reiserfs mail-list <Reiserfs-List@Namesys.COM>,
Reiserfs developers mail-list <Reiserfs-Dev@Namesys.COM>,
Linux Kernel Mailing List <Linux-Kernel@Vger.Kernel.ORG>
Subject: Re: new reiser4 snapshot
Date: Fri, 17 Oct 2003 22:51:53 +0400 [thread overview]
Message-ID: <3F903A49.4090007@namesys.com> (raw)
In-Reply-To: <16272.3551.934067.370680@laputa.namesys.com>
This snapshot fixes two fatal bugs, and improves performance. Nikita
can still make it crash, sigh, and we have discovered some unnecessary
seeks when replicating Mike Benoit's settings for bonnie++ that are due
to block allocation bugs. Sigh. We are probably still at least 2 weeks
away from code that we can seriously ask people to use. The performance
is good enough to be well worth using despite the allocation bugs, but
we don't like to ask people to use code we know how to crash.
--
Hans
prev parent reply other threads:[~2003-10-17 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 15:42 new reiser4 snapshot Nikita Danilov
2003-10-17 18:51 ` Hans Reiser [this message]
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=3F903A49.4090007@namesys.com \
--to=reiser@namesys.com \
--cc=Linux-Kernel@Vger.Kernel.ORG \
--cc=Nikita@Namesys.COM \
--cc=Reiserfs-Dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).