From: Hans Reiser <reiser@namesys.com>
To: Robert Hulme <rob@robhulme.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Repacker and compression plugin
Date: Mon, 27 Mar 2006 23:25:47 -0800 [thread overview]
Message-ID: <4428E4FB.6020201@namesys.com> (raw)
In-Reply-To: <e50d039c0603261632m2021453bg33ba2e8fb98090d6@mail.gmail.com>
> Are there any estimates of when the repacker and compression plugins
> will be available / stable?
This depends on how long we remain distracted by Hellwig and company more than by how long they take to complete.
As soon as we go into the kernel, zam and vs focus on the compression plugin stabilization followed by working on the repacker. Neither of those tasks will take anywhere near as long as dealing with Hellwig's code changes (none of which benefit reiser4 much). Edward is working on the compression plugin, but it is a task that could much benefit from the senior guys helping him out with code audits and the like.
> Can anyone give me a feel for how reliable you consider the Reiser 4
> file system to be?
The users are more reliable sources than I am. They have more computers running Reiser4 than I do.
It was stable, the VFS changes destabilized it, it is back to being stable again, the next release that I hope goes out this week will help that some more by a smidgen.
There is however one thing that could reduce stability in that patch, which is that we have changed the write code to greatly reduce CPU usage by not doing things 4k at a time.
Robert Hulme wrote:
>Any of the Reiser devs have an answer to my questions? :-)
>
>--
>
>
next prev parent reply other threads:[~2006-03-28 7:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 22:27 Repacker and compression plugin Tom Reinhart
2006-03-26 17:31 ` Clemens Eisserer
2006-03-27 0:32 ` Robert Hulme
2006-03-27 18:54 ` Hans Reiser
2006-03-28 7:25 ` Hans Reiser [this message]
2006-03-28 14:31 ` Clemens Eisserer
2006-03-29 4:20 ` Peter van Hardenberg
-- strict thread matches above, loose matches on Subject: below --
2006-03-23 14:26 Robert Hulme
2006-03-23 15:08 ` Raymond A. Meijer
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=4428E4FB.6020201@namesys.com \
--to=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=rob@robhulme.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.