From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Pavel Volkov <sailor@lists.xtsubasa.org>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: Using BTRFS on SSD now ?
Date: Sun, 08 Jun 2014 12:51:22 -0400 [thread overview]
Message-ID: <yq1mwdnwdit.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <62fc4c32-37c4-4c4e-b027-761859a12df4@lists.xtsubasa.org> (Pavel Volkov's message of "Sun, 08 Jun 2014 18:48:35 +0400")
>>>>> "Pavel" == Pavel Volkov <sailor@lists.xtsubasa.org> writes:
Pavel> Is mine a dinosaur drive?
[...]
Pavel> General Purpose Log 0x13 does not exist (override with '-T
Pavel> permissive' option)
The only flags defined in general purpose log page 0x13 are the queued
trim ones. So there is no compelling reason for a drive vendor to
implement that page unless the drive actually supports queued trim. And
consequently it's perfectly normal for that page to be absent.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2014-06-08 16:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 13:30 Using BTRFS on SSD now ? Swâmi Petaramesh
2014-06-05 14:42 ` Russell Coker
2014-06-05 15:14 ` Swâmi Petaramesh
2014-06-05 16:26 ` Marc MERLIN
2014-06-05 18:34 ` Chris Murphy
2014-06-05 14:56 ` Marc MERLIN
2014-06-05 15:11 ` Roman Mamedov
2014-06-08 14:26 ` Pavel Volkov
2014-06-05 15:59 ` Christoph Anton Mitterer
2014-06-05 17:07 ` Swâmi Petaramesh
2014-06-05 18:13 ` Chris Murphy
2014-06-05 19:05 ` Marc MERLIN
2014-06-05 22:25 ` Duncan
2014-06-05 23:58 ` Martin K. Petersen
2014-06-06 0:24 ` Chris Murphy
2014-06-06 0:35 ` Duncan
2014-06-08 14:48 ` Pavel Volkov
2014-06-08 16:51 ` Martin K. Petersen [this message]
2014-06-05 21:15 ` Duncan
2014-06-05 16:17 ` Martin Steigerwald
2014-06-05 18:00 ` Chris Murphy
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=yq1mwdnwdit.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sailor@lists.xtsubasa.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.