From: Hans Reiser <reiser@namesys.com>
To: Thomas Graham <lkthomas@sml.dyndns.org>
Cc: reiserfs-list@namesys.com
Subject: Re: Final test on v4 reiserfs ?
Date: Mon, 23 Jun 2003 13:12:05 +0400 [thread overview]
Message-ID: <3EF6C465.6020703@namesys.com> (raw)
In-Reply-To: <53797.203.186.23.91.1056328735.squirrel@sml.dyndns.org>
Thomas Graham wrote:
>anyone did a final test yet ? what's known problem right now ?
>Thanks
>
>
>
>
Sigh, releasing by LinuxTag will be tight.
Current issues off the top of my head.
extent overwrite code writes data twice needlessly (no need to get more
exact, it is being fixed).
we need to steal on capture (that is, if a block is in a transaction
being committed, we need to copy it if another transaction wants it
rather than wait on the commit)
we need to figure out why experimental code written last week to order
filebodies by filenames isn't working.
I need to perform complete reading from beginning to end of all code.
Who knows what I will find.
All FIXMEs in the code need to get fixed.
delete performance needs to be fixed at least up to reiser3 levels.
It would be nice if CPU consumption could drop a bit, and it would be
nice to test on a highly smp machine.
It would be nice if our txnmgr code improved in regards to locking.
For us to (beta) release at LinuxTag three conditions have to be met:
1) I have to feel that I would choose to use it over V3 in regards to
performance.
2) We have to be unable to crash it inside Namesys using all of our
testing scripts.
3) I have to be sure that the right key assignment algorithm is chosen
as the default.
--
Hans
prev parent reply other threads:[~2003-06-23 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 0:38 Final test on v4 reiserfs ? Thomas Graham
2003-06-23 9:12 ` 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=3EF6C465.6020703@namesys.com \
--to=reiser@namesys.com \
--cc=lkthomas@sml.dyndns.org \
--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.