From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>, Eric Sandeen <sandeen@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Harald Arnesen <skogtun.harald@gmail.com>,
linux-kernel@vger.kernel.org, linux-
Subject: Re: [ext4] Documentation patch
Date: Sun, 07 Dec 2008 14:43:28 -0600 [thread overview]
Message-ID: <493C3570.4040100@redhat.com> (raw)
In-Reply-To: <20081207183916.GB15998@mit.edu>
Theodore Tso wrote:
> Good points. OK, how about this?
>
> - When comparing performance with other filesystems, it's always
> important to try multiple workloads; very often a subtle change in a
> workload parameter can completely change the ranking of which
> filesystems do well compared to others. When comparing versus ext3,
> note that ext4 enables write barriers by default, while ext3 does
> not enable write barriers by default. So it is useful to use
> explicitly specify whether barriers are enabled or not when via the
> '-o barriers=[0|1]' mount option for both ext3 and ext4 filesystems
> for a fair comparison. When tuning ext3 for best benchmark numbers,
> it is often worthwhile to try changing the data journaling mode; '-o
> data=writeback,nobh' can be faster for some workloads. (Note
> however that running mounting with data=writeback can potentially
I'd say "running mounted with data=writeback...."
other than that it looks good to me :)
(sorta nitpicky but it probably won't be touched again for 5 years so
may as well get it right now) :)
-Eric
> leave stale data exposed in recently written files in case of an
> unclean shutdown, which could be a security exposure in some
> situations.) Configuring the filesystem with a large journal can
> also be helpful for metadata-intensive workloads.
>
> - Ted
prev parent reply other threads:[~2008-12-07 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 16:46 [ext4] Documentation patch Harald Arnesen
2008-12-01 16:57 ` Christoph Hellwig
2008-12-01 17:58 ` Eric Sandeen
2008-12-01 20:58 ` Theodore Tso
2008-12-06 22:25 ` Theodore Tso
2008-12-06 23:33 ` Eric Sandeen
2008-12-07 18:39 ` Theodore Tso
2008-12-07 20:43 ` Eric Sandeen [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=493C3570.4040100@redhat.com \
--to=sandeen@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skogtun.harald@gmail.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).