From: Hans Reiser <reiser@namesys.com>
To: Aaron Lehmann <aaronl@vitelus.com>
Cc: Nikita Danilov <Nikita@Namesys.COM>,
"Stephen C. Tweedie" <sct@redhat.com>,
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: ext3 throughput woes on certain (possibly heavily fragmented) files
Date: Sat, 07 Sep 2002 02:05:12 +0400 [thread overview]
Message-ID: <3D792698.4010401@namesys.com> (raw)
In-Reply-To: 20020906210214.GA25666@vitelus.com
Aaron Lehmann wrote:
>On Fri, Sep 06, 2002 at 09:22:22PM +0400, Hans Reiser wrote:
>
>
>>I think I prefer that we implement a repacker for reiser4 though, as
>>that, combined with delayed allocation, will be a balanced and thorough
>>solution.
>>
>>
>
>How does current ReiserFS fare against extreme fragmentation? What
>about XFS? Without trying to risk a flamewar, what Linux filesystems
>are the most preventive of fragmentation?
>
>The filesystem could make a huge difference on a machine like a mail
>server...
>
>
>
>
Sometimes it is best to confess that one does not have the expertise
appropriate for answering a question. Someone on our mailing list
studied it carefully though. Perhaps they can comment.
Hans
next prev parent reply other threads:[~2002-09-06 22:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 9:24 ext3 throughput woes on certain (possibly heavily fragmented) files Aaron Lehmann
2002-09-06 16:06 ` Stephen C. Tweedie
2002-09-06 17:14 ` Nikita Danilov
2002-09-06 17:22 ` Hans Reiser
2002-09-06 21:02 ` Aaron Lehmann
2002-09-06 22:05 ` Hans Reiser [this message]
2002-09-06 17:24 ` Stephen C. Tweedie
2002-09-16 22:39 ` Simon Kirby
2002-09-17 16:53 ` Andreas Dilger
2002-09-17 21:55 ` jw schultz
-- strict thread matches above, loose matches on Subject: below --
2002-09-16 18:00 Peter Niemayer
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=3D792698.4010401@namesys.com \
--to=reiser@namesys.com \
--cc=Nikita@Namesys.COM \
--cc=aaronl@vitelus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=sct@redhat.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