From: Christoph Hellwig <hch@infradead.org>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: Adriano Silva <adriano_da_silva@yahoo.com.br>,
Keith Busch <kbusch@kernel.org>,
Matthias Ferdinand <bcache@mfedv.net>,
Bcache Linux <linux-bcache@vger.kernel.org>,
Coly Li <colyli@suse.de>, Christoph Hellwig <hch@infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [RFC] Add sysctl option to drop disk flushes in bcache? (was: Bcache in writes direct with fsync)
Date: Wed, 1 Jun 2022 22:26:25 -0700 [thread overview]
Message-ID: <YphKAWHfhsCKZbBs@infradead.org> (raw)
In-Reply-To: <8a95d4f-b263-5231-537d-b1f88fdd5090@ewheeler.net>
On Wed, Jun 01, 2022 at 02:11:35PM -0700, Eric Wheeler wrote:
> It looks like the NVMe works well except in 512b situations. Its
> interesting that --force-unit-access doesn't increase the latency: Perhaps
> the NVMe ignores sync flags since it knows it has a non-volatile cache.
NVMe (and other interface) SSDs generally come in two flavors:
- consumer ones have a volatile write cache and FUA/Flush has a lot of
overhead
- enterprise ones with the grossly nisnamed "power loss protection"
feature have a non-volatile write cache and FUA/Flush has no overhead
at all
If this is an enterprise drive the behavior is expected. If on the
other hand it is a cheap consumer driver chances are it just lies, which
there have been a few instances of.
next prev parent reply other threads:[~2022-06-02 5:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <958894243.922478.1652201375900.ref@mail.yahoo.com>
[not found] ` <958894243.922478.1652201375900@mail.yahoo.com>
[not found] ` <9d59af25-d648-4777-a5c0-c38c246a9610@ewheeler.net>
2022-05-23 18:36 ` [RFC] Add sysctl option to drop disk flushes in bcache? (was: Bcache in writes direct with fsync) Eric Wheeler
2022-05-24 5:34 ` Christoph Hellwig
2022-05-24 20:14 ` Eric Wheeler
2022-05-24 20:34 ` Keith Busch
2022-05-24 21:34 ` Eric Wheeler
2022-05-25 5:20 ` Christoph Hellwig
2022-05-25 18:44 ` Eric Wheeler
2022-05-26 9:06 ` Christoph Hellwig
2022-05-28 1:52 ` Eric Wheeler
2022-05-28 3:57 ` Keith Busch
2022-05-28 4:59 ` Christoph Hellwig
[not found] ` <24456292.2324073.1653742646974@mail.yahoo.com>
[not found] ` <YpLmDtMgyNLxJgNQ@kbusch-mbp.dhcp.thefacebook.com>
[not found] ` <2064546094.2440522.1653825057164@mail.yahoo.com>
[not found] ` <YpTKfHHWz27Qugi+@kbusch-mbp.dhcp.thefacebook.com>
2022-06-01 19:27 ` Adriano Silva
2022-06-01 21:11 ` Eric Wheeler
2022-06-02 5:26 ` Christoph Hellwig [this message]
2022-05-25 5:17 ` Christoph Hellwig
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=YphKAWHfhsCKZbBs@infradead.org \
--to=hch@infradead.org \
--cc=adriano_da_silva@yahoo.com.br \
--cc=bcache@lists.ewheeler.net \
--cc=bcache@mfedv.net \
--cc=colyli@suse.de \
--cc=kbusch@kernel.org \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@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).