From: Christoph Hellwig <hch@infradead.org>
To: linux-btrace@vger.kernel.org
Subject: Re: What does FWFSM as an RBWS mean?
Date: Tue, 09 May 2017 19:08:02 +0000 [thread overview]
Message-ID: <20170509190802.GA10037@infradead.org> (raw)
In-Reply-To: <CANWz5fjBj_zNfCGGX4LMi2yghP1N80SNQZ__FgAOd=8n=mC01A@mail.gmail.com>
On Tue, May 09, 2017 at 07:03:06AM -1000, Chris Worley wrote:
> So one is pre-flush and the second is FUA? How do you tell which F
> you're looking at if just one? I'm seeing lots of both FWS and FWFSM.
A Pre-flush is before the 'W', a FUA is after the 'W'.
> So, really no effect, just informational (this is an XFS fs doing the I/O).
Yes.
>
> Any hints on when sync, flushes, or FUAs force flash to write to
> media? We're using NVMe drives. All these operations should be
> power-cut safe... I'm not sure if any force the driver/controller to
> commit to NAND when buffering (in power-cut safe memory) would be
> better for performance/lifespan. I'm guessing this isn't an easy
> question... any idea how to find out?
The answer is it depends. For enterprice drivers writes are usually
buffered on SRAM before going to the media, but those usually don't
even claim to have a volatile write cache (e.g. do not set the
Volatile Write Cache (VWC) bit in Identify Controller in nvme, you
can check that using 'nvme id-ctrl -H /dev/nvme0').
For consumer drivers chances are every flush or fua will go out
to the media, or the device is not actually power fail safe.
prev parent reply other threads:[~2017-05-09 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 16:40 What does FWFSM as an RBWS mean? Chris Worley
2017-05-09 16:43 ` Christoph Hellwig
2017-05-09 17:03 ` Chris Worley
2017-05-09 19:08 ` Christoph Hellwig [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=20170509190802.GA10037@infradead.org \
--to=hch@infradead.org \
--cc=linux-btrace@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).