From: Jan Kara <jack@suse.cz>
To: Christoph Hellwig <hch@infradead.org>
Cc: viro@zeniv.linux.org.uk, jeffm@suse.com, chris.mason@oracle.com,
jack@suse.cz, reiserfs-devel@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/2] always default to issue cache flushes
Date: Mon, 11 Jul 2011 21:19:16 +0200 [thread overview]
Message-ID: <20110711191916.GH5482@quack.suse.cz> (raw)
In-Reply-To: <20110711182532.GA12099@infradead.org>
On Mon 11-07-11 14:25:33, Christoph Hellwig wrote:
> It's bad enough that we still have filesystems who can't deal with
> the volatile write caches present on all modern consumer disks, but
> let's at least make use of this feature where present instead of
> playing fast and lose with users data. Switch ext3 and reiserfs
> to the same default already applied in btrfs, ext4, gfs2, hfsplus,
> nilfs2 and XFS.
Maybe it's worth noting that both RH and SUSE distributions actually have
barriers switched on by default for years so this change isn't going to
affect most enterprise users.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2011-07-11 19:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 18:25 [PATCH 0/2] always default to issue cache flushes Christoph Hellwig
2011-07-11 18:25 ` [PATCH 1/2] ext3: make ext3 mount default to barrier=1 Christoph Hellwig
2011-07-11 19:17 ` Jan Kara
2011-07-11 19:20 ` Christoph Hellwig
2011-07-11 22:23 ` Ted Ts'o
2011-07-12 0:16 ` Eric Sandeen
2011-07-12 13:24 ` Chris Mason
2011-07-14 15:19 ` Christoph Hellwig
2011-07-11 18:26 ` [PATCH 2/2] reiserfs: make reiserfs default to barrier=flush Christoph Hellwig
2011-07-11 19:19 ` Jan Kara [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=20110711191916.GH5482@quack.suse.cz \
--to=jack@suse.cz \
--cc=chris.mason@oracle.com \
--cc=hch@infradead.org \
--cc=jeffm@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.