[lkml]   [2002]   [Aug]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [BK] [PATCH] reiserfs changeset 7 of 7 to include into 2.4 tree

On Sat, 10 Aug 2002, Hans Reiser wrote:

> I forgot to mention that a variety of benchmarks of various allocator
> options are on They aren't very
> understandable, but if questions are asked I'll answer them.

I get this from the "Mongo" benchmark homepage.

I suppose the behaviour with your patches is "skip_busy", right?

Block allocator options are passed with alloc=opt1:opt2:... mount
parameter, where opt1, opt2,... are:

Try to allocate blocks in block-groups (called bitmaps in
reiserfs) that have more than 10% of blocks free first, if that fail,
allocate anywhere.
turned on 'border algorithm' and put this border in X% of
available space.
Mimic original block allocator from 2.4.18
Displace formatted nodes of directories at creation time.
Displacing is the hash from the dir_id.
Takes one parameter - a blocknumber. When this blocknumber
allocated for the file, it is placed separately on disk (by default new
location is the keyed_hash from the object_id
value. "displace_based_on_dirid" will change that.
When displacing files, place files that live in same directory
in the same disk area. (achieved by hashing by dir_id value of ondisk_key,
instead of object_id)


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:22    [W:0.065 / U:2.856 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site