linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Mirko Benz <mirko.benz@web.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: SATA on mptsas performance
Date: Tue, 28 Feb 2006 22:30:16 -0500	[thread overview]
Message-ID: <44051548.9090408@torque.net> (raw)
In-Reply-To: <43F2DDA7.7050700@web.de>

Mirko Benz wrote:
> Hello,
> 
> The SAS3442X is connected to the JBOD via a x4 SAS cable.
> The JBOD has an LSI SAS Expander chip - no port multiplier.
> Disks are Seagate ST3300831AS (300 GB, SATA-I, NCQ)
> 
> Does the SAS controller and the SAS expander communicate at 3 Gb when
> accessing SATA disks?

If the SATA disk does 3 Gb/sec then yes but SATA-1 disks
run at 1.5 Gb/sec (and don't have NCQ). When a SAS HBA
using STP connects to a SATA-1 disk via an expander it
rate matches. This means that it substitutes a dummy value
(ALIGN I think) between each data value on that path
(between the HBA and the expander). Hence it essentially
wastes half the available bandwidth for the duration of
the connection. There is talk of multiplexing in SAS-2
when the the physical link rate is 6 Gb/sec and the
connection rate is 3 or 1.5 Gb/sec.

> If not it should give 4 * 150 MB/s r/w throughput for this configuration.

4 * 150 MB/sec r/w throughput (half duplex ?) would be
correct.

BTW since SAS uses "10b8b" encoding (as do IB,
FC, SATA, PCIe, 10 gigabit ethernet on copper, etc) which
encodes 8 data bits into 10 bits on the wire then one
can flip between "<n> MB/sec" and "(<n> * 10) Mb/sec". The
capitalization (or not) of the "B" is obviously significant.
Perhaps somebody from a SAS vendor company could tell us how
much data one can really send down a 3 Gb/sec SAS/STP
connection under optimum conditions.


Doug Gilbert


  reply	other threads:[~2006-03-01  3:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-14 16:02 SATA on mptsas performance Moore, Eric
2006-02-15  7:52 ` Mirko Benz
2006-03-01  3:30   ` Douglas Gilbert [this message]
2006-03-01  6:09     ` Jeff Garzik
2006-03-01  8:16       ` Mirko Benz
2006-03-01 17:55     ` Asgeir Eiriksson
  -- strict thread matches above, loose matches on Subject: below --
2006-03-01 16:04 Moore, Eric
2006-02-13 14:01 Mirko Benz

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=44051548.9090408@torque.net \
    --to=dougg@torque.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mirko.benz@web.de \
    /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;
as well as URLs for NNTP newsgroup(s).