From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Andreas Dilger <adilger@clusterfs.com>,
Zygo Blaxell <eazgwmir@umail.furryterror.org>,
reiserfs-list@namesys.com
Subject: Re: reiserfs on removable media
Date: 02 Jul 2003 14:59:05 -0400 [thread overview]
Message-ID: <1057172345.20904.923.camel@tiny.suse.com> (raw)
In-Reply-To: <3F032A33.3050303@namesys.com>
On Wed, 2003-07-02 at 14:53, Hans Reiser wrote:
> >This is called ordered data mode, and exists on ext3 and also reiserfs with
> >Chris Mason's patches. Under normal usage it shouldn't change performance
> >compared to writeback data mode (which is what reiserfs does by default).
> >
> It had some impact, I forget exactly how much, maybe Chris can
> resuscitate his benchmark of it?
>
The major cost of data=ordered is that dirty blocks are flushed every 5
seconds instead of every 30. The journal header patch in my
experimental data logging directory changes things so that only new
bytes in the file are done in data=ordered mode (either adding a new
block or appending onto the end of the file).
This helps a lot in the file rewrite tests.
-chris
next prev parent reply other threads:[~2003-07-02 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 18:23 reiserfs on removable media Zygo Blaxell
2003-07-02 18:45 ` Andreas Dilger
2003-07-02 18:53 ` Hans Reiser
2003-07-02 18:59 ` Chris Mason [this message]
2003-07-02 19:08 ` Dieter Nützel
2003-07-02 19:17 ` Chris Mason
2003-07-02 20:19 ` Zygo Blaxell
2003-07-03 2:02 ` Recipe for reiserfs oops on "removable" disks (was: Re: reiserfs on removable media) Zygo Blaxell
2003-07-03 6:08 ` reiserfs on removable media Oleg Drokin
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=1057172345.20904.923.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=adilger@clusterfs.com \
--cc=eazgwmir@umail.furryterror.org \
--cc=reiser@namesys.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.