From: Chris Mason <mason@suse.com>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] reiserfs v3 fixes and features
Date: Tue, 06 Apr 2004 17:06:27 -0400 [thread overview]
Message-ID: <1081285587.30811.258.camel@watt.suse.com> (raw)
In-Reply-To: <200404062214.40259@WOLK>
On Tue, 2004-04-06 at 16:14, Marc-Christian Petersen wrote:
> On Tuesday 06 April 2004 20:03, Chris Mason wrote:
>
> Hi Chris,
>
> > If anyone is interested in experimenting with the block allocator stuff,
> > please let me know.
>
> I am :)
There are a few different sides to the block allocator work.
1) don't ruin what the current allocator is good at (desktop esp). A
sequential tree read of freshly copied data is really fast right now.
It could be a little better with some metadata readahead, I'm still
trying to safely revive that code.
The patch tries to keep performance for a full tree read by with the -o
packing_groups option. The basic idea is to reuse bitmap groups for new
subdirectories until the bitmap group is full. This is done by checking
to see how full a given part of the btree is.
2) Improve the fragmentation under multiple writers. With 20 writers,
the default allocator breaks down, fragmenting badly (20% or so). The
patch with -o alloc=skip_busy:dirid_groups on makes things sane (3%).
So, to help test, you need some way of measuring fragmentation and a
whole bunch of benchmarks. I like fibmap:
(http://www.informatik.uni-frankfurt.de/~loizides/reiserfs/fibmap.html)
But Andrew has a fragmentation tool in the ext2 cvs I think.
-chris
next prev parent reply other threads:[~2004-04-06 21:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 18:03 Chris Mason
2004-04-06 20:14 ` Marc-Christian Petersen
2004-04-06 21:06 ` Chris Mason [this message]
2004-04-07 2:00 ` Chris Wright
2004-04-07 13:19 ` Chris Mason
2004-04-07 14:37 ` Hans Reiser
2004-04-07 13:06 ` Yury Umanets
2004-04-07 13:25 ` Chris Mason
2004-04-08 7:22 ` Yury Umanets
2004-04-09 22:02 ` Oleg Drokin
2004-04-15 0:30 ` Chris Mason
2004-04-15 2:53 ` Hubert Chan
2004-04-15 11:37 ` Chris Mason
2004-04-15 12:12 ` Nikita Danilov
2004-04-16 18:54 ` Chris Mason
2004-04-16 19:47 ` Marc-Christian Petersen
2004-04-16 19:59 ` Chris Mason
2004-04-16 20:06 ` Marc-Christian Petersen
2004-04-16 20:26 ` Chris Mason
2004-04-16 20:39 ` Chris Mason
2004-04-16 20:44 ` Marc-Christian Petersen
2004-04-16 20:41 ` Marc-Christian Petersen
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=1081285587.30811.258.camel@watt.suse.com \
--to=mason@suse.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
/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
Powered by JetHome