From: Alberto Bursi <alberto.bursi@outlook.it>
To: "J. Bruce Fields" <bfields@fieldses.org>,
Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Supercilious Dude <supercilious.dude@gmail.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: Is it possible that certain physical disk doesn't implement flush correctly?
Date: Sun, 31 Mar 2019 23:07:16 +0000 [thread overview]
Message-ID: <AM0PR03MB57458DE4ECD60598920D9CC092540@AM0PR03MB5745.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <20190331224553.GA17421@fieldses.org>
On 01/04/19 00:45, J. Bruce Fields wrote:
> On Sat, Mar 30, 2019 at 09:24:37PM +0800, Qu Wenruo wrote:
>>
>> On 2019/3/30 下午9:14, Supercilious Dude wrote:
>>> On Sat, 30 Mar 2019 at 13:09, Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>>> If controller is doing so, it must have its own power or at least finish
>>>> flush when controller writes to its fast cache.
>>>>
>>> The controller has its own battery backup to power the DRAM cache, as
>>> well as flash storage to dump it onto in the exceedingly unlikely
>>> event that the battery gets depleted.
>>>
>>>> For cache case, if we have enough data, we could still find some clue on
>>>> the flush execution time.
>>>>
>>>> Despite that, for that enterprise level usage, it's OK.
>>>>
>>>> But for consumer level storage, I'm not sure, especially for HDDs, and
>>>> maybe NVMe devices.
>>>>
>>> How do you distinguish who is a who? Am I an enterprise or a consumer?
>> Easy, price. :P
>>
>> To be honest, I don't really care about that fancy use case.
>> It's the vendor doing its work, and if something wrong happened,
>> customer will yell at them.
>>
>> I'm more interesting in the consumer level situation.
> The feature seems to be advertised as "power loss protection" or
> "enhanced power loss data protection". Which makes it sound like a data
> safety feature when really it's a performance feature. E.g. these are
> the Intel drives with "EPLDP":
>
> https://ark.intel.com/content/www/us/en/ark/search/featurefilter.html?productType=35125&0_EPLDP=True
>
> Last I checked there were some that weren't too expensive.
>
> --b.
Afaik quite a few consumer Crucial SSDs do have power loss protection
(those that advertise it either have a large
bank of capacitors on their PCB or use newer flash that for some reason
can do without that)
-Alberto
next prev parent reply other threads:[~2019-03-31 23:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 12:31 Is it possible that certain physical disk doesn't implement flush correctly? Qu Wenruo
2019-03-30 12:57 ` Supercilious Dude
2019-03-30 13:00 ` Qu Wenruo
2019-03-30 13:04 ` Supercilious Dude
2019-03-30 13:09 ` Qu Wenruo
2019-03-30 13:14 ` Supercilious Dude
2019-03-30 13:24 ` Qu Wenruo
2019-03-31 22:45 ` J. Bruce Fields
2019-03-31 23:07 ` Alberto Bursi [this message]
2019-03-31 11:27 ` Alberto Bursi
2019-03-31 12:00 ` Qu Wenruo
2019-03-31 13:36 ` Hannes Reinecke
2019-03-31 14:17 ` Qu Wenruo
2019-03-31 14:37 ` Hannes Reinecke
2019-03-31 14:40 ` Qu Wenruo
2019-03-31 12:21 ` Andrei Borzenkov
2019-04-01 11:55 ` Austin S. Hemmelgarn
2019-04-01 12:04 ` Austin S. Hemmelgarn
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=AM0PR03MB57458DE4ECD60598920D9CC092540@AM0PR03MB5745.eurprd03.prod.outlook.com \
--to=alberto.bursi@outlook.it \
--cc=bfields@fieldses.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=supercilious.dude@gmail.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;
as well as URLs for NNTP newsgroup(s).