From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Phillip Susi <psusi@ubuntu.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Tejun Heo <tj@kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: Whitelist SSDs that are known to properly return zeroes after TRIM
Date: Thu, 04 Dec 2014 20:53:22 -0500 [thread overview]
Message-ID: <yq18uimhnfx.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <547FE5BD.9070101@ubuntu.com> (Phillip Susi's message of "Wed, 03 Dec 2014 23:40:29 -0500")
>>>>> "Phillip" == Phillip Susi <psusi@ubuntu.com> writes:
Phillip> So your assertion is that you have seen it in writing,
Actually I haven't. I have talked to a bunch of people that have done
RAID qualification on SSDs. I also gleaned on a few vendor lists of
supported drive configurations.
The good news is that practice of each OEM having their own custom drive
firmware build is not very common for SSDs. And most of the results I
looked at was collected using off-the-shelf drives.
Phillip> I'm not saying a hard hell no, but this certainly makes me
Phillip> uncomfortable.
You do realize that my patch *restricts* the drives we enable
discard_zeroes_data on, right? Instead of relying solely on the drive's
own reporting we now also require empirical evidence that they do the
right thing.
Phillip> I'd much rather see the manufacturers put it in writing that
Phillip> yes, this make and model will perform this way even though it
Phillip> is not strictly required by ATA8.
Wishful thinking.
The sad reality is that standards are deliberately written to be
vague. And that any hard guarantees are part of product requirements
documents. That's not specific to SSDs in any way. That's true for
pretty much any piece of hardware.
Phillip> What would be better still is if the bloody ATA standard got a
Phillip> clue and said that if the drive claims that it does in fact
Phillip> zero after TRIM, that the TRIM command becomes mandatory
Phillip> instead of advisory.
I agree that the standards efforts in this department are a total train
wreck.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2014-12-05 1:53 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 2:44 [PATCH] libata: Whitelist SSDs that are known to properly return zeroes after TRIM Martin K. Petersen
2014-12-04 3:02 ` Phillip Susi
2014-12-04 3:24 ` Martin K. Petersen
2014-12-04 3:28 ` Phillip Susi
2014-12-04 3:35 ` Martin K. Petersen
2014-12-04 4:40 ` Phillip Susi
2014-12-05 1:53 ` Martin K. Petersen [this message]
2014-12-04 21:49 ` One Thousand Gnomes
2014-12-05 2:46 ` Martin K. Petersen
2014-12-04 17:06 ` Tejun Heo
2014-12-05 2:13 ` Martin K. Petersen
2014-12-05 14:51 ` Tejun Heo
2014-12-10 4:09 ` James Bottomley
2014-12-10 14:29 ` Tejun Heo
2014-12-10 20:34 ` James Bottomley
2014-12-10 21:02 ` Martin K. Petersen
2014-12-12 8:35 ` Ming Lei
2015-01-05 16:28 ` Tejun Heo
2015-01-07 0:05 ` Martin K. Petersen
2015-01-07 2:54 ` Tejun Heo
2015-01-07 4:15 ` Dave Chinner
2015-01-07 15:26 ` Tejun Heo
2015-01-08 14:28 ` Martin K. Petersen
2015-01-08 15:11 ` Tejun Heo
2015-01-08 15:34 ` Martin K. Petersen
2015-01-08 15:36 ` Tejun Heo
2015-01-08 15:58 ` Tim Small
2015-01-09 20:52 ` Martin K. Petersen
2015-01-09 21:39 ` Tejun Heo
2015-01-08 14:29 ` Martin K. Petersen
2015-01-08 4:05 ` Phillip Susi
2015-01-08 4:58 ` Andreas Dilger
2015-01-08 14:09 ` Phillip Susi
2015-01-08 22:31 ` Andreas Dilger
2014-12-10 15:43 ` Tim Small
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=yq18uimhnfx.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=psusi@ubuntu.com \
--cc=tj@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).