From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Marc MERLIN <marc@merlins.org>
Cc: Chris Samuel <chris@csamuel.org>, Duncan <1i5t5.duncan@cox.net>,
Christopher Corsi <cjmovie@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: discard synchronous on most SSDs?
Date: Fri, 14 Mar 2014 15:57:41 -0400 [thread overview]
Message-ID: <yq1bnx8y2mi.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20140314192605.GD6143@merlins.org> (Marc MERLIN's message of "Fri, 14 Mar 2014 12:26:05 -0700")
>>>>> "Marc" == Marc MERLIN <marc@merlins.org> writes:
Marc,
Marc> So I have Sata 3.1, that's great news, it means I can keep using
Marc> discard without worrying about performance and hangs
The fact that the drive reports compliance with a certain version of
SATA does not in any way imply that it implements all commands defined
in that specification.
The location where queued TRIM support is reported is somewhat unusual.
And last I looked hdparm -I had no infrastructure in place to report
stuff contained in log pages.
The kernel does look the right place to determine whether to issue the
queued or unqueued variant or not. But the information isn't exported to
userland.
So right now I'm afraid we don't have a good way for a user to determine
whether a device supports queued trims or not.
I guess we could consider either adding an ATA-specific "I don't suck"
flag in sysfs, add the missing code to hdparm, or both...
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2014-03-14 19:58 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 [this message]
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
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=yq1bnx8y2mi.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=1i5t5.duncan@cox.net \
--cc=chris@csamuel.org \
--cc=cjmovie@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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