From: Douglas Gilbert <dgilbert@interlog.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
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>
Subject: Re: [GIT PULL] isci merge candidate
Date: Mon, 16 May 2011 23:41:08 -0400 [thread overview]
Message-ID: <4DD1EE54.9040201@interlog.com> (raw)
In-Reply-To: <BANLkTi=yGe+xKpB+VnD3+tvw1-o4Qs_Z7w@mail.gmail.com>
On 11-05-16 08:47 PM, Jeff Garzik wrote:
> On Mon, May 16, 2011 at 8:39 PM, Dan Williams<dan.j.williams@intel.com> wrote:
>> At a minimum It would require a more verbose interface to
>> libsas/libata (or new libframe?) to allow us to deliver raw
>> unsolicited frames into common protocol handlers.
>
> ...which is where SAS and SATA have been heading for a while, anyway.
> With chained SAS expander setup you have a network, if an annoying,
> manually configured and routed one. Over that network you deliver
> frames of various types.
For SAS-2 expanders, edit the above to:
s/manually/self/
Doug Gilbert
next prev parent reply other threads:[~2011-05-17 3:41 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
2011-05-17 0:39 ` Dan Williams
2011-05-17 0:47 ` Jeff Garzik
2011-05-17 3:41 ` Douglas Gilbert [this message]
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=4DD1EE54.9040201@interlog.com \
--to=dgilbert@interlog.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=benh@kernel.crashing.org \
--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.