From: Douglas Gilbert <dougg@torque.net>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-scsi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Broadcom 8603 SAS/SATA driver, rough draft
Date: Sun, 23 Sep 2007 17:59:30 -0400 [thread overview]
Message-ID: <46F6E1C2.20905@torque.net> (raw)
In-Reply-To: <20070923040437.GA30170@havoc.gtf.org>
Jeff Garzik wrote:
> Rather than sitting on this for far too long, I wanted to go ahead and
> get this out there. I heard some chips might be trickling out into
> public hands.
>
> This is a bare bones Broadcom 8603 SAS+SATA driver, attempting to use
> the vaunted libsas. Notes:
>
> * A quick glance at the FIXMEs will tell you obviously doesn't work.
>
> * The hardware is quite simple and straightforward and easy to program
> in an efficient way: each SAS port has a command queue (DMA ring) and
> a response queue (DMA ring). Or if in SATA mode, just a command
> queue.
>
> * The SAS/SATA negotiation is largely out of our hands. The silicon
> does its thing, and then tells us what type of device connected. We
> are then expected to switch the port to either SAS mode or SATA mode,
> accordingly.
>
> * There is no firmware or anything. Just DMA and register bitbanging.
> We have plenty of low-level control.
>
> * The state of SAS/SATA integration is perpetually pathetic. Updates
> in this area are likely. There's a rumor Brian King @ IBM may look
> into this area too.
>
> * This driver pretty much completely lacks exception handling.
>
>
> As an aside, I am also writing a driver for Marvell chips that behave
> quite similarly to this chip. It seems the future of storage might look
> like these Broadcom and Marvell SAS+SATA DMA ring interfaces, in the
> volume marketspace at least.
Jeff,
Is the lack of SMP support a driver limitation or is it
the silicon?
How about support for wide ports (i.e. when 2 or more HBA
phys are attached to remote phys which have the same SAS
addresses)?
Last question: can the chip run in SCSI target mode?
Doug Gilbert
next prev parent reply other threads:[~2007-09-23 21:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 4:04 [PATCH] Broadcom 8603 SAS/SATA driver, rough draft Jeff Garzik
2007-09-23 21:59 ` Douglas Gilbert [this message]
2007-09-23 23:33 ` Jeff Garzik
2007-09-23 23:46 ` Jeff Garzik
2007-09-23 23:47 ` Jeff Garzik
2007-09-23 23:05 ` James Bottomley
2007-09-23 23:43 ` Jeff Garzik
2007-09-23 23:59 ` James Bottomley
2007-09-24 0:14 ` Jeff Garzik
2007-09-24 14:06 ` James Bottomley
2007-09-24 15:30 ` Jeff Garzik
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=46F6E1C2.20905@torque.net \
--to=dougg@torque.net \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.