From: Mike Christie <michaelc@cs.wisc.edu>
To: James.Smart@Emulex.Com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [RFC] iscsi transport : add sgio pass-thru support
Date: Mon, 02 Nov 2009 17:55:08 -0600 [thread overview]
Message-ID: <4AEF715C.4030700@cs.wisc.edu> (raw)
In-Reply-To: <1256853056.7154.6.camel@wookie>
James Smart wrote:
> This patch implements the same infrastructure as found in the FC transport
> for sgio request/response handling.
>
> The patch creates (and exports to userland) a new header - scsi_bsg_iscsi.h
>
>
Sorry for the late reply. I am trying to sell my house and move.
Based on your experience with fc bsg support, do you think there is some
common code? It looks like a lot of this is generic. I just started
looking at the fc bsg stuff again, so I am not sure ATM.
next prev parent reply other threads:[~2009-11-02 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 21:50 [RFC] iscsi transport : add sgio pass-thru support James Smart
2009-11-02 23:55 ` Mike Christie [this message]
2009-11-03 14:37 ` James Smart
2009-11-04 15:52 ` Mike Christie
-- strict thread matches above, loose matches on Subject: below --
2009-10-30 13:49 James Smart
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=4AEF715C.4030700@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Smart@Emulex.Com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox