From: Christoph Hellwig <hch@infradead.org>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: Jens Axboe <axboe@kernel.dk>,
Georg Sch?nberger <g.schoenberger@xortex.com>,
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 01:58:23 -0800 [thread overview]
Message-ID: <20151214095823.GA30662@infradead.org> (raw)
In-Reply-To: <3911767.qVqsL1TcMv@merkaba>
On Mon, Dec 14, 2015 at 09:38:56AM +0100, Martin Steigerwald wrote:
> Is it safe to use XFS (or any other filesystem) on enterprise SSDs with Power
> Loss Protection (PLP), i.e. some capacitor to provide for enough electricity
> to write out all data in DRAM to flash after a power loss, with a reordering
> I/O scheduler like CFQ?
If the device does not need cache flushes it should not report requiring
flushes, in which case nobarrier will be a noop. Or to phrase it
differently: If nobarrier makes a difference skipping it is not safe.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-12-14 9:58 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 [this message]
2015-12-14 10:18 ` Georg Schönberger
2015-12-14 10:27 ` Christoph Hellwig
2015-12-14 10:34 ` Georg Schönberger
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=20151214095823.GA30662@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox