From: Hans Reiser <reiser@namesys.com>
To: Mike Benoit <ipso@snappymail.ca>
Cc: David Masover <ninja@slaphack.com>,
reiserfs-list@namesys.com, LKML <linux-kernel@vger.kernel.org>,
Alexander Zarochentcev <zam@namesys.com>,
vs <vs@thebsh.namesys.com>
Subject: Re: reiser4 status (correction)
Date: Fri, 21 Jul 2006 18:49:27 -0600 [thread overview]
Message-ID: <44C17617.5040303@namesys.com> (raw)
In-Reply-To: <1153514509.6659.41.camel@ipso.snappymail.ca>
Mike Benoit wrote:
>
>On top of that, I don't see how a repacker would help these work loads
>much as the files usually have a high churn rate.
>
I think Reiserfs is used on a lot more than squid servers. For them,
80% of files don't move for long periods of time is the usual industry
statistic....
prev parent reply other threads:[~2006-07-22 1:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 21:59 reiser4 status (correction) Hans Reiser
[not found] ` <44C043B5.3070501@slaphack.com>
2006-07-21 8:44 ` Hans Reiser
2006-07-21 19:13 ` David Masover
2006-07-21 20:41 ` Mike Benoit
2006-07-21 21:06 ` David Masover
2006-07-22 0:49 ` 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=44C17617.5040303@namesys.com \
--to=reiser@namesys.com \
--cc=ipso@snappymail.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=ninja@slaphack.com \
--cc=reiserfs-list@namesys.com \
--cc=vs@thebsh.namesys.com \
--cc=zam@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