From: camis <camis@mweb.co.za>
To: reiserfs-list@namesys.com
Subject: Re: reiserfs v3 patches updated
Date: Tue, 06 Apr 2004 20:29:05 +0200 [thread overview]
Message-ID: <4072F6F1.3090806@mweb.co.za> (raw)
In-Reply-To: <200404061838.05099.christian.mayrhuber@gmx.net>
> Seem to run fine so far with
> rw,noatime,nodiratime,acl,user_xattr,data=ordered,alloc=skip_busy:dirid_groups,packing_groups
Has anyone done any throughput/benchmarks for the various
new patches/code?
>The block allocator improvements is our attempt to reduce
>fragmentation. The patch defaults to the regular 2.6.5 block allocator,
>but has options documented at the top of the patch that allow grouping
>of blocks by packing locality or object id. It also has an option to
>inherit lightly used packing localities across multiple subdirs, which
>keeps things closer together in the tree if you have a bunch of subdirs
>without much in them.
Any of these new features documented anywhere? ;)
Cami
next prev parent reply other threads:[~2004-04-06 18:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 0:10 reiserfs v3 patches updated Chris Mason
2004-04-06 16:38 ` Christian Mayrhuber
2004-04-06 16:48 ` Chris Mason
2004-04-06 18:29 ` camis [this message]
2004-04-06 18:47 ` Chris Mason
2004-04-06 19:17 ` camis
2004-04-06 19:24 ` Chris Mason
2004-04-06 19:53 ` camis
2004-04-06 20:29 ` Chris Mason
2004-04-06 20:38 ` Cami
2004-04-06 20:33 ` Chris Mason
2004-04-06 20:51 ` Cami
2004-04-06 21:10 ` Chris Mason
2004-04-06 21:30 ` Cami
2004-04-06 21:39 ` Chris Mason
2004-04-07 9:28 ` reiserfs v3 patches updated - Bug Christian Mayrhuber
2004-04-07 13:07 ` Chris Mason
[not found] ` <200404071714.39187.christian.mayrhuber@gmx.net>
2004-04-07 23:58 ` Chris Mason
2004-04-13 14:57 ` Christian Mayrhuber
2004-04-10 22:53 ` reiserfs v3 patches updated Hubert Chan
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=4072F6F1.3090806@mweb.co.za \
--to=camis@mweb.co.za \
--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.