From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: discard synchronous on most SSDs?
Date: Sat, 15 Mar 2014 11:26:27 +0000 (UTC) [thread overview]
Message-ID: <pan$86f37$20eb1911$444fa726$8400b046@cox.net> (raw)
In-Reply-To: 1566234.HjNzCBAKa5@quad
Chris Samuel posted on Sat, 15 Mar 2014 17:48:56 +1100 as excerpted:
> $ sudo smartctl --identify /dev/sdb | fgrep 'Trim bit in DATA SET
> MANAGEMENT'
> 169 0 1 Trim bit in DATA SET MANAGEMENT command
> supported
> $
>
> If that command returns nothing then it's not reported as supported (and
> I've tested that). You can get the same info with hdparm -I.
> My puzzle now is that I have two SSD drives that report supporting NCQ
> TRIM (one confirmed via product info) but report only supporting SATA
> 3.0 not 3.1.
My SATA 2.5 SSDs reported earlier, report support for it too, so it's
apparently not SATA 3.1 limited. (Note that I'm simply grepping word
169, in the command below. Since word 169 is trim support...)
sudo smartctl --identify /dev/sda | grep '^ 169'
169 - 0x0001 Data Set Management support
169 0 1 Trim bit in DATA SET MANAGEMENT command supported
Either that or that feature bit simply indicates trim support, not NCQ
trim support.
But it can be noted that if SATA 3.1 requires trim to be NCQ if its
supported at all (spinning rust would thus get a pass), then claiming 3.1
support as well as trim support should be the equivalent of claiming NCQ
trim support, likely with no indicator of whether that trim support is NCQ
or not, pre-3.1.
... Which would mean that my SATA 2.5 and your SATA 3.0 drives are simply
indicating trim support, not specifically NCQ trim support.
I guess you'd have to check the SATA 2.5 and 3.0 specs to find that out.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-03-15 11:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 7:48 Massive BTRFS performance degradation KC
2014-03-09 8:17 ` Swâmi Petaramesh
2014-03-09 10:01 ` Martin Steigerwald
2014-03-09 10:23 ` Swâmi Petaramesh
2014-03-09 11:33 ` Hugo Mills
2014-03-09 11:54 ` Martin Steigerwald
2014-03-09 12:10 ` Swâmi Petaramesh
2014-03-09 17:14 ` boris
2014-03-14 2:11 ` discard synchronous on most SSDs? Marc MERLIN
2014-03-14 3:39 ` Chris Murphy
2014-03-14 5:17 ` Marc MERLIN
2014-03-14 7:33 ` Chris Samuel
2014-03-14 19:26 ` Marc MERLIN
2014-03-14 19:57 ` Martin K. Petersen
2014-03-14 20:46 ` Holger Hoffstätte
2014-03-15 4:21 ` Marc MERLIN
2014-03-15 9:38 ` Holger Hoffstätte
2014-03-15 5:25 ` Chris Samuel
2014-03-15 6:48 ` Chris Samuel
2014-03-15 11:26 ` Duncan [this message]
2014-03-15 22:48 ` Chris Samuel
2014-03-16 6:06 ` Marc MERLIN
2014-03-16 17:09 ` Chris Murphy
2014-03-16 16:22 ` Martin K. Petersen
2014-03-16 17:50 ` Marc MERLIN
2014-03-15 4:06 ` Chris Samuel
2014-03-16 16:07 ` Martin K. Petersen
2014-03-14 12:07 ` Duncan
2014-03-14 21:44 ` Chris Murphy
2014-03-14 7:27 ` Chris Samuel
2014-03-09 17:36 ` Massive BTRFS performance degradation Austin S Hemmelgarn
2014-03-09 18:55 ` Tobias Holst
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='pan$86f37$20eb1911$444fa726$8400b046@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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