From: Hans Reiser <reiser@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Re: [PATCH CFT] tons of logging patches
Date: Fri, 02 Aug 2002 16:59:39 +0400 [thread overview]
Message-ID: <3D4A823B.7040803@namesys.com> (raw)
In-Reply-To: 1028291685.19330.215.camel@tiny
Chris Mason wrote:
>On Fri, 2002-08-02 at 08:28, Chris Mason wrote:
>
>
>>Hello everyone,
>>
>>I've uploaded 03-data-logging-24.diff, which fixes a tail packing oops
>>in data=journal mode, and fixes the data=ordered slow down (5-10%)
>>introduced in -23.
>>
>>
>
>Whoops, I neglected to mention that data=ordered is now the default in
>the patch. You can mount with -o data=writeback if you don't want
>ordered data writes.
>
>-chris
>
>
>
>
>
>
we just saw a benchmark in which data=ordered caused a major slowdown.
Does this patch fix this?
Edward and Elena, I want thorough benchmarking of this.
--
Hans
next prev parent reply other threads:[~2002-08-02 12:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-22 20:02 [PATCH CFT] tons of logging patches Dieter Nützel
2002-06-24 19:05 ` Chris Mason
2002-07-09 13:52 ` Dieter Nützel
2002-07-09 14:00 ` Chris Mason
2002-07-12 19:43 ` Chris Mason
2002-07-14 0:52 ` Manuel Krause
2002-08-02 12:28 ` Chris Mason
2002-08-02 12:34 ` Chris Mason
2002-08-02 12:59 ` Hans Reiser [this message]
2002-08-02 13:10 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 3:51 Chris Mason
2002-06-04 1:49 ` Manuel Krause
2002-06-04 2:20 ` Chris Mason
2002-06-04 3:28 ` Manuel Krause
2002-06-04 13:12 ` Chris Mason
2002-06-05 21:13 ` Manuel Krause
2002-06-05 21:27 ` Manuel Krause
2002-06-06 0:09 ` Chris Mason
2002-06-06 4:59 ` Manuel Krause
2002-06-12 22:32 ` Manuel Krause
2002-06-17 0:47 ` Chris Mason
2002-06-17 0:31 ` Manuel Krause
2002-06-17 19:04 ` Chris Mason
2002-06-21 0:25 ` Chris Mason
2002-06-25 0:55 ` Manuel Krause
2002-06-28 13:51 ` Chris Mason
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=3D4A823B.7040803@namesys.com \
--to=reiser@namesys.com \
--cc=mason@suse.com \
--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.