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 0:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 21:59 reiser4 status (correction) Hans Reiser
2006-07-21 3:02 ` David Masover
2006-07-21 8:44 ` Hans Reiser
2006-07-21 10:17 ` Sarath Menon
2006-07-21 19:13 ` David Masover
2006-07-21 20:41 ` Mike Benoit
2006-07-21 21:06 ` David Masover
2006-07-21 21:37 ` Mike Benoit
2006-07-21 22:29 ` Andreas Schäfer
2006-07-21 22:45 ` David Masover
2006-07-21 23:06 ` Andreas Schäfer
2006-07-22 20:07 ` Maciej Sołtysiak
2006-07-21 22:40 ` David Masover
2006-07-21 23:53 ` Mike Benoit
2006-07-22 2:48 ` David Masover
2006-07-22 5:53 ` Hans Reiser
2006-07-22 8:55 ` Mike Benoit
2006-07-22 12:34 ` David Masover
2006-07-22 19:56 ` Mike Benoit
2006-07-22 20:37 ` David Masover
2006-07-23 6:19 ` Hans Reiser
2006-07-22 15:40 ` portage tree (Was: Re: reiser4 status (correction)) Christian Trefzer
2006-07-23 5:50 ` Hans Reiser
2006-07-24 15:12 ` wiki entry (Was: Re: portage tree) Christian Trefzer
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 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.