public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <robert.w.love@intel.com>
To: linux-scsi@vger.kernel.org
Subject: [PATCH 0/3][RFC] libfc and fcoe
Date: Fri, 08 Aug 2008 16:26:22 -0700	[thread overview]
Message-ID: <20080808232622.24715.7743.stgit@fritz> (raw)

This patch-set adds the following code to the SCSI subsystem.

1) FC and FCoE protocol definitions in header files
        - Files are added in include/scsi/fc/
        - New files are: fc_els.h, fc_encaps.h, fc_fc2.h,
          fc_fcp.h, fc_fs.h, fc_gs.h and fc_ns.h

2) libfc - a FC assist library
        - Composed of 5 sub-components: Exchange Manager, Local Port
          Remote Port, Name Server and SCSI-FCP
        - Uses libfc_function_template for cross-layer calls
        - Uses struct fc_lport as primary object shared by all
	  sub-modules
        - Common code defined in include/scsi/libfc/libfc.h

3) fcoe - a FCoE initiator implementation
        - Simple encapsulation and unpacking layer
        - Interacts with netdev
        - Uses /sys/module/fcoe/create and destroy for
          enabling/disabling FCoE connection over a particular Ethernet
          adapter
        - Works on any Ethernet adapter

These patches adds 12,291 lines of code to 4 new directories-

include/scsi/fc/
include/scsi/libfc/
drivers/scsi/libfc/
drivers/scsi/fcoe/

We've created some diagrams to suppliment this RFC. They're posted on
our wiki at http://www.open-fcoe.org/openfc/wiki/index.php/Architecture.

The Open-FCoE team recognizes that this code will continue to evolve and
we are committed to maintaining and improving it. We have a list of TODO
items on our wiki at http://www.open-fcoe.org/openfc/wiki/index.php/TODO
and intend to work through that list.

In addition to our engineering tasks we will be putting this stack under
more testing and as defects are exposed we will fix them. Defects are
tracked on the Open-FCoE.org bugzilla. Currently engineers have been
testing this stack and within their test environments the stack works.
It has seen some validation, but no heavy testing.

We recognize that we have a lot of work to do but we also think that
we've made a lot of progress in the last few months and we would like to
be merged. We're sending this RFC to solicit any comments, but in
particular comments about the code that should prevent a merger.

Thanks,

Open-FCoE
//Rob, Vasu, Chris, Yi, Steve

             reply	other threads:[~2008-08-08 23:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08 23:26 Robert Love [this message]
2008-08-08 23:26 ` [PATCH 1/3] [RFC] FC protocol definition header files Robert Love
2008-08-08 23:26 ` [PATCH 2/3] [RFC] libfc: a modular software Fibre Channel implementation Robert Love
2008-08-08 23:26 ` [PATCH 3/3] [RFC] fcoe: Fibre Channel over Ethernet Robert Love

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=20080808232622.24715.7743.stgit@fritz \
    --to=robert.w.love@intel.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