public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stefan /*St0fF*/ Hübner" <stefan.huebner@stud.tu-ilmenau.de>
To: dgilbert@interlog.com
Cc: "Prof. Dr. Klaus Kusche" <klaus.kusche@computerix.info>,
	linux-scsi@vger.kernel.org
Subject: Re: Good SAS adapters for 6 Gb/s SATA SSD's (with TRIM)?
Date: Fri, 12 Aug 2011 09:16:24 +0200	[thread overview]
Message-ID: <4E44D348.30003@stud.tu-ilmenau.de> (raw)
In-Reply-To: <4E449BB1.3060300@interlog.com>

Douglas,

have you double-checked to use the IT (Initiator Mode) Firmware from
LSI?  I mean we build up systems based on the X8SI6-F mainboard from
Supermicro which has a LSI SAS2008 with 8 Lanes on-board.  If using
HW-RAID (Modes 0, 1, 1E, ...) on those, we have to flash the "IR"
firmware.  If using the chip as HBA for Linux software RAID, we flash
the "IT" firmware, and if the customer needs HW-RAID5-Support, they get
an extra chip onto the board and we have to flash "iMR" firmware...

So you have 3 different firmware versions.  IT would be the way to go
here...

Greets,
Stefan

Am 12.08.2011 05:19, schrieb Douglas Gilbert:
> On 11-08-11 03:59 PM, Douglas Gilbert wrote:
>> 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.
> 
> I did check the LSI support page for my HBA just before sending
> my original reply. And the version 9 firmware was showing at the
> top of the list. Alas, that page had been alpha sorted on the
> file names so that version 10 of the firmware (May 2011) was
> hiding further down the page :-)
> 
> So I installed the newest firmware and redid the above tests.
> Now the SCSI WRITE SAME (16) with the UNMAP bit set works on
> that SSD. The SCSI UNMAP command was rejected and I did not
> test sending the ATA DATA SET MANAGEMENT command through
> the pass-through (but I expect that would work).
> 
> So Linux file systems will be able "discard" (="unmap"(SCSI);
> ="trim"(ATA)) data using LSI HBAs based the LSI 2008 chip
> which are running recent 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?
> 
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2011-08-12  7:40 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
2011-08-12  3:19   ` Douglas Gilbert
2011-08-12  7:16     ` Stefan /*St0fF*/ Hübner [this message]
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=4E44D348.30003@stud.tu-ilmenau.de \
    --to=stefan.huebner@stud.tu-ilmenau.de \
    --cc=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