From: Mike Christie <michaelc@cs.wisc.edu>
To: FUJITA Tomonori <tomof@acm.org>
Cc: robert.w.love@intel.com, yi.zou@intel.com,
christopher.leech@intel.com, vasu.dev@intel.com,
linux-scsi@vger.kernel.org, fujita.tomonori@lab.ntt.co.jp
Subject: Re: Open-FCoE on linux-scsi
Date: Fri, 04 Jan 2008 14:19:14 -0600 [thread overview]
Message-ID: <477E94C2.3050106@cs.wisc.edu> (raw)
In-Reply-To: <20080104225015Z.tomof@acm.org>
FUJITA Tomonori wrote:
>> Understood, but open-iscsi doesn't have the layering scheme that we do.
>> Since we're providing a Fibre Channel protocol processing layer that
>> different transport types can register with I think the generic name is
>> appropriate. Anyway, I don't think anyone here is terribly stuck on the
>> name; it's not a high priority at this time.
>
> open-iscsi provides the proper abstraction. It can handles different
> transport types, tcp and RDMA (iSER). It supports software iSCSI
> drivers and HW iSCSI HBAs drivers. They are done via iscsi transport
> class (and libiscsi).
I think I hinted to this offlist, but the bnx2i branch in my iscsi git
tree is best to look at for this. The upstream stuff is best the model
where we support only HW iscsi hbas drivers (all offload) and SW iscsi
drivers (all software). The bnx2i branch modifies the class and lib so
it also supports a model in between the two, so pretty much everything
is covered.
next prev parent reply other threads:[~2008-01-04 20:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 23:40 Open-FCoE on linux-scsi Love, Robert W
2007-11-28 0:19 ` FUJITA Tomonori
2007-11-28 0:29 ` Love, Robert W
2007-12-28 19:11 ` FUJITA Tomonori
2007-12-31 16:34 ` Love, Robert W
2008-01-03 10:35 ` FUJITA Tomonori
2008-01-03 21:58 ` Love, Robert W
2008-01-04 11:45 ` Stefan Richter
2008-01-04 11:59 ` FUJITA Tomonori
2008-01-04 22:07 ` Dev, Vasu
2008-01-04 23:41 ` Stefan Richter
2008-01-05 0:09 ` Stefan Richter
2008-01-05 0:21 ` Stefan Richter
2008-01-05 8:28 ` Christoph Hellwig
2008-01-15 1:18 ` Love, Robert W
2008-01-15 22:18 ` James Smart
2008-01-22 23:52 ` Love, Robert W
2008-01-29 5:42 ` Chris Leech
2008-02-01 1:53 ` James Smart
2008-01-06 4:14 ` FUJITA Tomonori
2008-01-06 4:27 ` FUJITA Tomonori
2008-01-04 13:47 ` FUJITA Tomonori
2008-01-04 20:19 ` Mike Christie [this message]
2008-01-05 18:33 ` Vladislav Bolkhovitin
2008-01-06 1:28 ` FUJITA Tomonori
2008-01-08 17:38 ` Vladislav Bolkhovitin
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=477E94C2.3050106@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=christopher.leech@intel.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-scsi@vger.kernel.org \
--cc=robert.w.love@intel.com \
--cc=tomof@acm.org \
--cc=vasu.dev@intel.com \
--cc=yi.zou@intel.com \
/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.