From: Mike Fedyk <mfedyk@matchmail.com>
To: Chris Mason <mason@suse.com>
Cc: reiserfs-list@namesys.com
Subject: Re: [Fwd: Re: [OT] block allocation algorithm [Was] Re: heavily fragmented file system.. How to defrag it on-line??]
Date: Thu, 25 Mar 2004 16:06:33 -0800 [thread overview]
Message-ID: <40637409.5040007@matchmail.com> (raw)
In-Reply-To: <1080258953.2828.3.camel@watt.suse.com>
Chris Mason wrote:
> On Thu, 2004-03-25 at 18:17, Mike Fedyk wrote:
>
>>Hi guys,
>>
>>Reiser3 has worse fragmentation than ext3 in this test case. Reiser4
>>was better, but it had a bad worst case and still wasn't as good as xfs.
>>
>>I'm especially interested in getting reiser3 to produce fewer fragments
>>in this test.
>>
>>Comments?
>
>
> There's a great deal of room for improvement in the reiser3 block
> allocator. I've got patches against 2.4.x that make it much smarter by
> trying to spread large files apart from each other but keep small files
> (and small directories) close together.
>
> Those are on hold until the logging and acls are done and in, but if
> people want to play around with porting them I can send you a copy.
If I knew more than Shell and Perl, I'd take you up on that offer.
Maybe in ~6 months. Lurking on the kernel lists really teaches you a
lot. :-D
Mike
next prev parent reply other threads:[~2004-03-26 0:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 23:17 [Fwd: Re: [OT] block allocation algorithm [Was] Re: heavily fragmented file system.. How to defrag it on-line??] Mike Fedyk
2004-03-25 23:55 ` Chris Mason
2004-03-26 0:06 ` Mike Fedyk [this message]
2004-03-26 16:46 ` Hans Reiser
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=40637409.5040007@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=mason@suse.com \
--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.