From: Jeff Garzik <jeff@garzik.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
James.Bottomley@hansenpartnership.com,
Christoph Hellwig <hch@lst.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Dave Jiang <dave.jiang@intel.com>,
David Milburn <dmilburn@redhat.com>,
Ed Ciechanowski <ed.ciechanowski@intel.com>,
Ed Nadolski <edmund.nadolski@intel.com>,
Jacek Danecki <jacek.danecki@intel.com>,
Jeff Skirvin <jeffrey.d.skirvin@intel.com>
Subject: Re: [GIT PULL] isci merge candidate
Date: Fri, 13 May 2011 17:46:10 -0400 [thread overview]
Message-ID: <4DCDA6A2.4060001@garzik.org> (raw)
In-Reply-To: <BANLkTim3igaB8XXQkDY6GEutWfbK-o840A@mail.gmail.com>
On 05/13/2011 04:34 PM, Linus Torvalds wrote:
> What's the likely user base of this?
Pretty big, I imagine.
> Why is it a SCSI driver rather
> than SATA?
It's "server" SAS hardware, a la mvsas driver. SAS hardware is that
"lovely" superset of SATA + SCSI, where SATA is one of several frame
formats the device may speak. So it is definitely a SCSI driver, that
hooks into SATA processing via ata_sas_* hooks and functions.
> Why is it so f&*%ing big?
1. Because it's a SAS driver :)
2. Because it used to be an ugly vendor driver, now in the process of
being cleaned up, rather than a nice, clean from-scratch Linux driver.
So it's a bit of a tough call. It still needs more hammering and
cleaning, but if this is what winds up on all Intel "server" boards that
makes it pretty important.
Jeff
next prev parent reply other threads:[~2011-05-13 21:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 20:14 [GIT PULL] isci merge candidate Dan Williams
2011-05-13 20:34 ` Linus Torvalds
2011-05-13 21:45 ` Dan Williams
2011-05-13 22:16 ` Benjamin Herrenschmidt
2011-05-17 0:39 ` Dan Williams
2011-05-17 0:47 ` Jeff Garzik
2011-05-17 3:41 ` Douglas Gilbert
2011-05-13 21:46 ` Jeff Garzik [this message]
2011-05-14 8:49 ` Christoph Hellwig
2011-05-17 3:56 ` James Bottomley
2011-05-17 22:11 ` Dan Williams
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=4DCDA6A2.4060001@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmilburn@redhat.com \
--cc=ed.ciechanowski@intel.com \
--cc=edmund.nadolski@intel.com \
--cc=hch@lst.de \
--cc=jacek.danecki@intel.com \
--cc=jeffrey.d.skirvin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).