public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Kurt Miller <kurt@intricatesoftware.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org
Subject: Re: LSI SAS2008 SATA TRIM not working
Date: Fri, 07 Feb 2014 20:24:18 -0500	[thread overview]
Message-ID: <yq1iosqs8fx.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1391808293.2761.9.camel@sonic.justonedata.com> (Kurt Miller's message of "Fri, 07 Feb 2014 16:24:53 -0500")

>>>>> "Kurt" == Kurt Miller <kurt@intricatesoftware.com> writes:

Kurt> #  hdparm -I /dev/sdc

[...]

I don't see any deterministic read after trim/read zero after trim
support on your drive. And I have a sneaking suspicion that those are
two of the fields that the LSI firmware looks at when deciding whether
to support logical block provisioning (in addition to support for the
DSM TRIM command).

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2014-02-08  1:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06 23:56 LSI SAS2008 SATA TRIM not working Kurt Miller
2014-02-07 20:44 ` Martin K. Petersen
2014-02-07 20:52   ` Kurt Miller
2014-02-07 20:59     ` Martin K. Petersen
2014-02-07 21:24       ` Kurt Miller
2014-02-08  1:24         ` Martin K. Petersen [this message]
2014-02-09 22:28           ` Kurt Miller
2014-02-12  2:27             ` Kurt Miller
2014-04-11 16:57               ` LSI SAS - SSDs with DRAT and DZAT Bernd Schubert
2014-04-17 19:42                 ` Martin K. Petersen
2014-04-17 22:32                   ` Kurt Miller
     [not found]                     ` <CAN7X1Un4=dTyvRbyt=0j6Q+=OBcXRDB+0J+dLPZCboKdxyTTzQ@mail.gmail.com>
2014-04-18 15:23                       ` Kurt Miller
2014-02-07 20:46 ` LSI SAS2008 SATA TRIM not working Kurt Miller
2015-09-09  1:45   ` Chang Limin

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=yq1iosqs8fx.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=kurt@intricatesoftware.com \
    --cc=linux-scsi@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