All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: XFS and nobarrier with SSDs
Date: Mon, 14 Dec 2015 10:39:57 -0600	[thread overview]
Message-ID: <566EF0DD.8000209@sandeen.net> (raw)
In-Reply-To: <566E9B36.9080509@xortex.com>



On 12/14/15 4:34 AM, Georg Schönberger wrote:
> 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

Yes, it should.  I've made some edits, hopefully it's up to date and clear now.

Thanks,
-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2015-12-14 16:40 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
2015-12-14 16:39               ` Eric Sandeen [this message]
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=566EF0DD.8000209@sandeen.net \
    --to=sandeen@sandeen.net \
    --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.