From: Christoph Hellwig <hch@infradead.org>
To: Georg Sch?nberger <g.schoenberger@xortex.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Martin Steigerwald <martin@lichtvoll.de>,
Jens Axboe <axboe@kernel.dk>,
Linux FS-Devel <linux-fsdevel@vger.kernel.org>,
Jeff Moyer <jmoyer@redhat.com>,
Linux Block mailing list <linux-block@vger.kernel.org>,
XFS mailing list <xfs@oss.sgi.com>
Subject: Re: XFS and nobarrier with SSDs
Date: Mon, 14 Dec 2015 05:36:05 -0800 [thread overview]
Message-ID: <20151214133605.GA20841@infradead.org> (raw)
In-Reply-To: <566E9B36.9080509@xortex.com>
On Mon, Dec 14, 2015 at 10:34:30AM +0000, Georg Sch?nberger wrote:
> OK, thanks for clarification.
> Should the XFS FAQ be updated?
> *http://xfs.org/index.php/XFS_FAQ#Q._Should_barriers_be_enabled_with_storage_which_has_a_persistent_write_cache.3F
Probably. The text soudns to me like it was written a long time ago
when Linux actually use barriers that also prevent I/O reordering
instead of just issuing the required cache flushes.
next prev parent reply other threads:[~2015-12-14 13:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 10:24 XFS and nobarrier with SSDs Georg Schönberger
2015-12-12 12:26 ` Martin Steigerwald
2015-12-14 6:43 ` Georg Schönberger
2015-12-14 8:38 ` Martin Steigerwald
2015-12-14 8:38 ` Martin Steigerwald
2015-12-14 9:58 ` Christoph Hellwig
2015-12-14 9:58 ` Christoph Hellwig
2015-12-14 10:18 ` Georg Schönberger
2015-12-14 10:18 ` Georg Schönberger
2015-12-14 10:27 ` Christoph Hellwig
2015-12-14 10:27 ` Christoph Hellwig
2015-12-14 10:34 ` Georg Schönberger
2015-12-14 10:34 ` Georg Schönberger
2015-12-14 13:36 ` Christoph Hellwig [this message]
2015-12-14 16:39 ` Eric Sandeen
2015-12-26 23:44 ` Linda Walsh
2015-12-26 23:44 ` Linda Walsh
2015-12-14 11:48 ` Emmanuel Florac
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=20151214133605.GA20841@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=g.schoenberger@xortex.com \
--cc=jmoyer@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=martin@lichtvoll.de \
--cc=xfs@oss.sgi.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.