From: Chris Mason <mason@suse.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>,
"ReiserFS List" <reiserfs-list@namesys.com>,
"Paul P Komkoff Jr" <i@stingr.net>,
"Manuel Krause" <manuel.krause@mb.tu-ilmenau.de>
Subject: Re: Re: [STUPID TESTCASE] ext3 htree vs. reiserfs on 2.5.40-mm1
Date: 07 Oct 2002 09:12:21 -0400 [thread overview]
Message-ID: <1033996342.13900.383.camel@tiny> (raw)
In-Reply-To: <20021004220126.GB3000@clusterfs.com>
On Fri, 2002-10-04 at 18:01, Andreas Dilger wrote:
> On Oct 04, 2002 22:54 +0200, Dieter N?tzel wrote:
> > Am Mittwoch, 2. Oktober 2002 10:48 schrieb Paul P Komkoff Jr:
> > > Replying to Andreas Dilger:
> > > > Why do you think data=writeback is better than data=journal? If the
> > > > files have no data then it should not make a difference.
> > >
> > > It is better than default data=ordered I think :)
> > > Reiserfs worked fine because it don't have such kind of limit ...
> >
> > Orange and apples, again?
> >
> > Try with latest ReiserFS data-logging and see what we get?
> > Chris do you have something for 2.5.40+ ready?
>
> I don't think it will make much difference - the files being created
> are zero-length files so the journaling mode is irrelevant.
The data logging patches have a bunch of other metadata writeback
optimizations. It helps most for small transactions, but improves
things for all metadata workloads. Updated 2.4.20-preX patches should
finally go out today, and then I'll start on 2.5
-chris
next prev parent reply other threads:[~2002-10-07 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 20:54 [STUPID TESTCASE] ext3 htree vs. reiserfs on 2.5.40-mm1 Dieter Nützel
2002-10-04 21:28 ` 2.5.40 (was " Valdis.Kletnieks
2002-10-04 21:54 ` Ed Tomlinson
2002-10-04 22:21 ` Valdis.Kletnieks
2002-10-04 22:00 ` Andreas Dilger
2002-10-04 22:01 ` Re: [STUPID TESTCASE] " Andreas Dilger
2002-10-07 8:51 ` Oleg Drokin
2002-10-07 13:12 ` Chris Mason [this message]
2002-10-08 20:31 ` Manuel Krause
2002-10-04 22:27 ` 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=1033996342.13900.383.camel@tiny \
--to=mason@suse.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=adilger@clusterfs.com \
--cc=i@stingr.net \
--cc=manuel.krause@mb.tu-ilmenau.de \
--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.