From: "Georg Schönberger" <g.schoenberger@xortex.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jens Axboe <axboe@kernel.dk>, XFS mailing list <xfs@oss.sgi.com>,
Linux Block mailing list <linux-block@vger.kernel.org>,
Jeff Moyer <jmoyer@redhat.com>,
Linux FS-Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: XFS and nobarrier with SSDs
Date: Mon, 14 Dec 2015 10:34:30 +0000 [thread overview]
Message-ID: <566E9B36.9080509@xortex.com> (raw)
In-Reply-To: <20151214102750.GA29192@infradead.org>
On 2015-12-14 11:27, Christoph Hellwig wrote:
> On Mon, Dec 14, 2015 at 10:18:54AM +0000, Georg Sch?nberger wrote:
>>> Or to phrase it
>>> differently: If nobarrier makes a difference skipping it is not safe.
>> I do not fully understand that sentence, what do you mean by "makes a
>> difference" and "skipping is not safe"?
> The rule of thumb is: if nobarrier makes your workload run faster you
> should not be using it, aka: don't use it.
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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-12-14 10:34 UTC|newest]
Thread overview: 11+ 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 9:58 ` Christoph Hellwig
2015-12-14 10:18 ` Georg Schönberger
2015-12-14 10:27 ` Christoph Hellwig
2015-12-14 10:34 ` Georg Schönberger [this message]
2015-12-14 16:39 ` Eric Sandeen
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=566E9B36.9080509@xortex.com \
--to=g.schoenberger@xortex.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=jmoyer@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox