From: Douglas Gilbert <dgilbert@interlog.com>
To: "Prof. Dr. Klaus Kusche" <klaus.kusche@computerix.info>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Good SAS adapters for 6 Gb/s SATA SSD's (with TRIM)?
Date: Thu, 11 Aug 2011 15:59:32 -0400 [thread overview]
Message-ID: <4E4434A4.7010808@interlog.com> (raw)
In-Reply-To: <4E43F2C3.9000808@computerix.info>
On 11-08-11 11:18 AM, Prof. Dr. Klaus Kusche wrote:
> I'm looking for ways to hook up fast 6 Gb/s SATA SSD's (non-RAID!)
> to (server or i-X58) mainboards which do not have native 6 Gb/s SATA.
>
> From the reviews I've read so far, two things became obvious:
> * The SSD's I'm looking at really want a working SATA TRIM command.
> * All the onboard Marvell 88SE9128 (or ASmedia) solutions
> seriuosly lack performance, as do PCIe cards based on those chips.
>
> So basically, there seem to be two choices:
> 1.) LSI 2008
> 2.) Marvell 9485
>
> 1.) seems to be fast, reliable and well-supported,
> but as far as I can tell, it doesn't support TRIM at all:
> It neither maps SCSI unmap to SATA TRIM,
> nor accepts TRIM as a SATA passthrough command.
>
> Is that true?
What counts in Linux for "trim" support on a SSD (SATA,
SAS or FC) is correctly processing the SCSI WRITE SAME (16)
with the UNMAP bit set. In the case of a SATA SSD, a SCSI
to ATA Translation Layer (SATL) should map that SCSI WRITE
SAME (16) with the UNMAP bit set to the ATA DATA SET
MANAGEMENT command with the TRIM attribute set.
Many Linux SATA low level drivers use libata which
implements the above mapping. However some SAS HBAs
(e.g. LSI MPT Fusion 3 and 6 Gbps) implement the SATL
in their own HBA firmware.
I tested a LSI SAS 9212-4i4e HBA running its most recent
firmware (9.0 from Feb 26, 2011) with a Intel SSDSA2M080
which does support trim. I used my ddpt utility and the
SCSI WRITE SAME (16) with the UNMAP bit set was rejected
as an "illegal request". With the UNMAP bit clear it
accepted the command. I also checked the SCSI UNMAP
command and it was also rejected.
LSI have some more work to do on their firmware.
Doug Gilbert
> I didn't find much about 2.)
> * The only cards based on this chip are the HighPoint 27xx,
> or did I miss something?
> * Running a 27xx with the mvsas driver was reported to have stability
> problems or random errors. Are these problems solved?
> * Is the 27xx fast (with SATA SSD's & mvsas driver),
> i.e. significantly faster than onboard SATA 3 Gb/s ports?
> * Does the 27xx+mvsas support TRIM when connected to SATA drives?
>
> Are there any other solutions?
next prev parent reply other threads:[~2011-08-11 19:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 15:18 Good SAS adapters for 6 Gb/s SATA SSD's (with TRIM)? Prof. Dr. Klaus Kusche
2011-08-11 19:59 ` Douglas Gilbert [this message]
2011-08-12 3:19 ` Douglas Gilbert
2011-08-12 7:16 ` Stefan /*St0fF*/ Hübner
2011-08-12 13:42 ` Douglas Gilbert
2011-08-14 19:59 ` Stefan Hübner
2011-08-12 8:04 ` Prof. Dr. Klaus Kusche
2011-08-12 8:15 ` Ric Wheeler
2011-08-12 8:48 ` Prof. Dr. Klaus Kusche
2011-08-12 9:01 ` Ric Wheeler
2011-08-12 9:24 ` Prof. Dr. Klaus Kusche
2011-08-12 9:35 ` Ric Wheeler
2011-08-12 11:14 ` Lukas Czerner
2011-08-12 9:52 ` Lukas Czerner
2011-08-12 12:32 ` Mark Lord
2011-08-12 9:17 ` Artem Bokhan
2011-08-12 9:34 ` Artem Bokhan
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=4E4434A4.7010808@interlog.com \
--to=dgilbert@interlog.com \
--cc=klaus.kusche@computerix.info \
--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