public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
* HighPoint RocketRaid 620 vs. RocketRaid 640 -- supported?
@ 2011-09-19 21:56 Justin Piszcz
  2011-09-21 11:28 ` Justin Piszcz
  0 siblings, 1 reply; 4+ messages in thread
From: Justin Piszcz @ 2011-09-19 21:56 UTC (permalink / raw)
  To: linux-kernel, linux-scsi

Hi,

I have a HighPoint RocketRaid 620 and it works fine with 3.0+.
The HighPoint RocketRaid 640 also has a Marvell 88SE9128, can anyne 
confirm whether this (x4) PCI-e 2.0 card works in Linux with the 
built-in kernel driver?

Justin.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: HighPoint RocketRaid 620 vs. RocketRaid 640 -- supported?
  2011-09-19 21:56 HighPoint RocketRaid 620 vs. RocketRaid 640 -- supported? Justin Piszcz
@ 2011-09-21 11:28 ` Justin Piszcz
  2011-10-03 20:13   ` Pasi Kärkkäinen
  0 siblings, 1 reply; 4+ messages in thread
From: Justin Piszcz @ 2011-09-21 11:28 UTC (permalink / raw)
  To: linux-kernel, linux-scsi

Hi,

Incase anyone is wondering the same thing, I contacted Highpoint and they 
said (confirmed) the 620 support (which I am using now) is built-in to the 
kernel and the 640 is not, so unless you like compiling kernel modules/out 
of tree drivers for a _boot_ volume and want a regular SATA 6.0gbps 
controller that supports TRIM, I'd go for the 620 even though it maxes out 
around 390-420MiB/s read where a real SAS controller supports 490-500MiB/s 
for an Intel 510 SSD, but remember, SAS controllers (at least the one I 
tested with does not support TRIM and there is no Intel SSD optimizer for 
Linux.

Justin.

On Mon, 19 Sep 2011, Justin Piszcz wrote:

> Hi,
>
> I have a HighPoint RocketRaid 620 and it works fine with 3.0+.
> The HighPoint RocketRaid 640 also has a Marvell 88SE9128, can anyne confirm 
> whether this (x4) PCI-e 2.0 card works in Linux with the built-in kernel 
> driver?
>
> Justin.
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: HighPoint RocketRaid 620 vs. RocketRaid 640 -- supported?
  2011-09-21 11:28 ` Justin Piszcz
@ 2011-10-03 20:13   ` Pasi Kärkkäinen
  2011-10-03 20:16     ` Justin Piszcz
  0 siblings, 1 reply; 4+ messages in thread
From: Pasi Kärkkäinen @ 2011-10-03 20:13 UTC (permalink / raw)
  To: Justin Piszcz; +Cc: linux-kernel, linux-scsi

On Wed, Sep 21, 2011 at 07:28:26AM -0400, Justin Piszcz wrote:
> Hi,
>
> Incase anyone is wondering the same thing, I contacted Highpoint and they 
> said (confirmed) the 620 support (which I am using now) is built-in to 
> the kernel and the 640 is not, so unless you like compiling kernel 
> modules/out of tree drivers for a _boot_ volume and want a regular SATA 
> 6.0gbps controller that supports TRIM, I'd go for the 620 even though it 
> maxes out around 390-420MiB/s read where a real SAS controller supports 
> 490-500MiB/s for an Intel 510 SSD, but remember, SAS controllers (at 
> least the one I tested with does not support TRIM and there is no Intel 
> SSD optimizer for Linux.
>

Hmm.. does SAS "SCSI UNMAP" automatically get translated to 
ATA TRIM if you hook up SATA disk to SAS HBA ?

Is the ATA<->SCSI translation being done by the HBA firmware, 
or is it handled in the driver? 

-- Pasi (who is too lazy to grep in the driver right now ;)


> Justin.
>
> On Mon, 19 Sep 2011, Justin Piszcz wrote:
>
>> Hi,
>>
>> I have a HighPoint RocketRaid 620 and it works fine with 3.0+.
>> The HighPoint RocketRaid 640 also has a Marvell 88SE9128, can anyne 
>> confirm whether this (x4) PCI-e 2.0 card works in Linux with the 
>> built-in kernel driver?
>>
>> Justin.
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: HighPoint RocketRaid 620 vs. RocketRaid 640 -- supported?
  2011-10-03 20:13   ` Pasi Kärkkäinen
@ 2011-10-03 20:16     ` Justin Piszcz
  0 siblings, 0 replies; 4+ messages in thread
From: Justin Piszcz @ 2011-10-03 20:16 UTC (permalink / raw)
  To: Pasi Kärkkäinen; +Cc: linux-kernel, linux-scsi

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1448 bytes --]



On Mon, 3 Oct 2011, Pasi Kärkkäinen wrote:

> On Wed, Sep 21, 2011 at 07:28:26AM -0400, Justin Piszcz wrote:
>> Hi,
>>
>> Incase anyone is wondering the same thing, I contacted Highpoint and they
>> said (confirmed) the 620 support (which I am using now) is built-in to
>> the kernel and the 640 is not, so unless you like compiling kernel
>> modules/out of tree drivers for a _boot_ volume and want a regular SATA
>> 6.0gbps controller that supports TRIM, I'd go for the 620 even though it
>> maxes out around 390-420MiB/s read where a real SAS controller supports
>> 490-500MiB/s for an Intel 510 SSD, but remember, SAS controllers (at
>> least the one I tested with does not support TRIM and there is no Intel
>> SSD optimizer for Linux.
>>
>
> Hmm.. does SAS "SCSI UNMAP" automatically get translated to
> ATA TRIM if you hook up SATA disk to SAS HBA ?
When attached to a SAS HBA, it simply says:

Jul 14 16:12:03 p34 kernel: [   22.258855] EXT4-fs warning (device sda2): release_blocks_on_commit:2679: discard not supported, disabling

>
> Is the ATA<->SCSI translation being done by the HBA firmware,
> or is it handled in the driver?
I'm not sure, it would appear the driver handles it, when its on the Sata 6gbps
card (not SAS), it works fine:
Sep 20 13:53:34 p34 kernel: [    6.786898] EXT4-fs (sdb2): re-mounted. Opts: discard

>
> -- Pasi (who is too lazy to grep in the driver right now ;)

Justin.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2011-10-03 20:50 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-09-19 21:56 HighPoint RocketRaid 620 vs. RocketRaid 640 -- supported? Justin Piszcz
2011-09-21 11:28 ` Justin Piszcz
2011-10-03 20:13   ` Pasi Kärkkäinen
2011-10-03 20:16     ` Justin Piszcz

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox