From: Kurt Miller <kurt@intricatesoftware.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: LSI SAS2008 SATA TRIM not working
Date: Sun, 09 Feb 2014 17:28:15 -0500 [thread overview]
Message-ID: <1391984895.13523.13.camel@tardis.intricatesoftware.com> (raw)
In-Reply-To: <yq1iosqs8fx.fsf@sermon.lab.mkp.net>
On Fri, 2014-02-07 at 20:24 -0500, Martin K. Petersen wrote:
> >>>>> "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).
>
I wonder how to bring this issue to LSI's attention? My cross flashed
used controllers are out of support with LSI so I don't think I can get
them to listen to me.
>From a pricing perspective the Samsung 840 Pro looks interesting and is
on LSI's supported list. Does anyone have one of these around and can
check for deterministic read after trim? (hdparm -I /dev/sdc | grep
TRIM).
Thanks,
-Kurt
next prev parent reply other threads:[~2014-02-09 22:28 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
2014-02-09 22:28 ` Kurt Miller [this message]
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=1391984895.13523.13.camel@tardis.intricatesoftware.com \
--to=kurt@intricatesoftware.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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