From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"James.Bottomley@hansenpartnership.com"
<James.Bottomley@hansenpartnership.com>,
Christoph Hellwig <hch@lst.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
"Jiang, Dave" <dave.jiang@intel.com>,
David Milburn <dmilburn@redhat.com>,
"Ciechanowski, Ed" <ed.ciechanowski@intel.com>,
"Nadolski, Edmund" <edmund.nadolski@intel.com>,
"Danecki, Jacek" <jacek.danecki@intel.com>,
"Skirvin, Jeffrey D" <jeffrey.d.skirvin@intel.com>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: [GIT PULL] isci merge candidate
Date: Sat, 14 May 2011 08:16:02 +1000 [thread overview]
Message-ID: <1305324962.2781.5.camel@pasglop> (raw)
In-Reply-To: <4DCDA663.2040202@intel.com>
> It's a SAS (serial-attached-scsi) driver so it ties in to libsas rather
> than libata (libsas itself ties in to libata for tunnelling SATA
> protocol over SAS). The size is attributable to the fact that all
> protocol handling for non-fast path i/o is handled by software. There
> are still cleanups that can be made, but likely not on the on the same
> order of what we have already done.
How much of that non-fast-path could/should be in generic code vs. in
the driver specific code ? IE. If somebody comes up with another "dumb"
SAS adapter tomorrow that doesn't do all that magic in an offload CPU,
is any of that code re-usable ?
Cheers,
Ben.
next prev parent reply other threads:[~2011-05-13 22:16 UTC|newest]
Thread overview: 12+ 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 20:34 ` Linus Torvalds
2011-05-13 21:45 ` Dan Williams
2011-05-13 22:16 ` Benjamin Herrenschmidt [this message]
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
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=1305324962.2781.5.camel@pasglop \
--to=benh@kernel.crashing.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=jeff@garzik.org \
--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 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.