From: Hans Reiser <reiser@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: linux-fsdevel@vger.kernel.org, akpm@osdl.org,
reiserfs-dev@namesys.com,
Martin Steigerwald <Martin@lichtvoll.de>
Subject: Re: [PATCH 0/2] enable write barriers by default
Date: Fri, 04 Aug 2006 21:39:39 -0600 [thread overview]
Message-ID: <44D412FB.8080902@namesys.com> (raw)
In-Reply-To: <20060804135140.GA942@watt.suse.com>
Chris Mason wrote:
>Hello everyone,
>
>ReiserFS and ext3 have had code to support forcing cache flushes for a
>while, but it has been off by default.
>
>These two patches enable it by default on both filesystems. Disabling
>barriers can be done with:
>
>mount -o barrier=none in reiser
>mount -o barrier=0 in ext3
>
>-chris
>
>
>
>
>
Please explain when cache flushes occur now. For every fsync on a drive
that does not support write barriers? Which drives support it?
Did this only get enabled now because it is only now that someone from
the press is paying attention to it?
This is the price we paid for losing Andre, yes?
next prev parent reply other threads:[~2006-08-05 4:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 13:51 [PATCH 0/2] enable write barriers by default Chris Mason
2006-08-04 13:53 ` [PATCH 1/2] Make reiserfs default to barrier=flush Chris Mason
2006-08-04 13:55 ` [PATCH 2/2] make ext3 mount default to barrier=1 Chris Mason
2006-08-05 3:39 ` Hans Reiser [this message]
2006-08-05 12:45 ` [PATCH 0/2] enable write barriers by default 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=44D412FB.8080902@namesys.com \
--to=reiser@namesys.com \
--cc=Martin@lichtvoll.de \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mason@suse.com \
--cc=reiserfs-dev@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;
as well as URLs for NNTP newsgroup(s).