From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Vladimir Saveliev <vs@namesys.com>,
Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>,
Andrew Morton <akpm@osdl.org>,
Alexander Zarochentcev <zam@namesys.com>,
ReiserFS List <reiserfs-list@namesys.com>,
LKML <linux-kernel@vger.kernel.org>,
Jeff Mahoney <jeffm@suse.com>
Subject: Re: I would like to see ReiserFS V3 enter a feature freeze real soon.
Date: Tue, 01 Jun 2004 14:53:23 -0400 [thread overview]
Message-ID: <1086116003.22636.3445.camel@watt.suse.com> (raw)
In-Reply-To: <40BCB6BC.8020901@namesys.com>
On Tue, 2004-06-01 at 13:02, Hans Reiser wrote:
> > I can't promise that I'll never making another
> >change in there, but my goal is to keep them to a minimum.
> >
> >
> >
> >>Also, I would like to see some serious benchmarks of the bitmap
> >>algorithm changes before they go in. They seem nice in theory, and some
> >>users liked them for their uses, but that does not make a serious
> >>scientific study. Such a study has a high chance of making them even
> >>better.;-)
> >>
> >>
> >>
> >
> >Some benchmarks have been posted on reiserfs-list, but I'd love to
> >coordinate with you on getting some mongo numbers.
> >
> Ok.
> >A good start would be to just rebenchmark against v4.
> >
> >
> V4 performance is not at a stable point at the moment I think, I have
> not been monitoring things closely due to trying to earn bucks
> consulting, and performance did not get tested every week, but there
> have been reports of performance decreasing and no reports of anyone
> investigating it, so I need to....
>
Sure, since v4 is being done again -mm right now (right?) you can just
benchmark against a few of the new options. mount -o alloc=skip_busy
will give you the old allocator.
> Elena, please compose a URL consisting of past benchmarks of various V4
> snapshots and send it to me. (I did not read the last one you sent,
> sorry about that, so include the contents of that one also).
>
> If the objective is to determine if the algorithm is good, then we
> should test it with only the algorithm in question changed.
>
> I would be quite happy to add the algorithm to V4 (or Chris and Jeff can
> do that) and test it on vs. off.
The algorithm has a few key components, but v4 doesn't need most of it.
The part to inherit packing localities down the chain would be most
interesting in v4.
The rest approximates things v4 should already be good at, like grouping
some of the metadata near the data blocks.
-chris
prev parent reply other threads:[~2004-06-01 18:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 12:28 filesystem corruption (ReiserFS, 2.6.6): regions replaced by \000 bytes David Madore
2004-05-28 12:46 ` Chris Mason
2004-05-28 13:05 ` Lenar Lõhmus
2004-05-28 16:24 ` Tomas Szepe
2004-05-28 16:29 ` Chris Mason
2004-05-28 16:42 ` Pat
2004-05-28 16:54 ` Chris Mason
2004-05-28 16:45 ` Tomas Szepe
2004-05-28 16:55 ` Chris Mason
2004-05-28 16:58 ` Steven Cole
2004-05-29 11:56 ` Lenar Lõhmus
[not found] ` <1085750828.1914.385.camel@tribesman.namesys.com>
[not found] ` <1085751695.22636.3163.camel@watt.suse.com>
2004-05-31 16:48 ` I would like to see ReiserFS V3 enter a feature freeze real soon Hans Reiser
2004-06-01 11:37 ` Chris Mason
2004-06-01 17:02 ` Hans Reiser
2004-06-01 18:53 ` Chris Mason [this message]
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=1086116003.22636.3445.camel@watt.suse.com \
--to=mason@suse.com \
--cc=Reiserfs-Dev@namesys.com \
--cc=akpm@osdl.org \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=vs@namesys.com \
--cc=zam@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®