From: Yi Zou <yi.zou-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: devel-s9riP+hp16TNLxjTenLetw@public.gmane.org
Cc: linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [RFC PATCH v2 0/8] adding support to FCoE transport
Date: Fri, 07 Jan 2011 09:42:24 -0800 [thread overview]
Message-ID: <20110107174027.14631.47077.stg.yi.zou@intel.com> (raw)
This is the RFC v2 of adding fcoe transport to support vendor specific FCoE
transport into the existing Open-FCoE framework.
v1:
Initial post for adding fcoe transport:
https://lists.open-fcoe.org/pipermail/devel/2010-December/010865.html
Follow-up comments & discussions:
https://lists.open-fcoe.org/pipermail/devel/2011-January/010890.html
v2:
1. Per Joe's comment, renamed the libfcoe_fip.c to be fcoe_ctlr.c. I
also renamed the new ibfcoe_transport.c to be fcoe_transport.c.
2. Per Bhanu's comment, I have merged the three follow-up patches
from Bhanu with the following changes in fcoe_parse_buffer():
a) Though not a problem of the existing fcoe-util since the sysfs
entry is changing to libfcoe anyway, I still want to fill the buffer
of drv_name with default "fcoe" so default behavior is still the same
w/o changing cfg-ethx.
b) Fixed the '\n' ending in the input buffer in fcoe_parse_buffer, we still
need that proper formatting logic from the original fcoe_if_to_netdev(),
otherwise the ifname and drv_name will be messed up, causing the lookup for
netdev and transport to fail.
Testing Notes:
Did the checkpatch and tested w/ overnight stress FCoE traffic on 2 LUNs using
fcoe.ko as the default fcoe transport, that seems to be working ok. However,
loop create/destroy testing is needed before this gets committed eventually.
thanks,
yi
---
Yi Zou (8):
fcoe: convert fcoe.ko to become an fcoe transport provider driver
fcoe: prepare fcoe for using fcoe transport
libfcoe: include fcoe_transport.c into kernel libfcoe module
libfcoe: remove libfcoe.c, use the same fcoe_ctlr.c instead
libfcoe: rename libfcoe.c to fcoe_cltr.c for the coming fcoe_transport.c
libfcoe: add implementation to support fcoe transport
libfcoe: add fcoe_transport structure defines to include/scsi/libfcoe.h
libfcoe: move logging macros into the local libfcoe.h header file
drivers/scsi/fcoe/Makefile | 2
drivers/scsi/fcoe/fcoe.c | 183 +-
drivers/scsi/fcoe/fcoe_ctlr.c | 2682 ++++++++++++++++++++++++++++++++++++
drivers/scsi/fcoe/fcoe_transport.c | 548 +++++++
drivers/scsi/fcoe/libfcoe.c | 2708 ------------------------------------
drivers/scsi/fcoe/libfcoe.h | 31
include/scsi/libfcoe.h | 43 +
7 files changed, 3367 insertions(+), 2830 deletions(-)
create mode 100644 drivers/scsi/fcoe/fcoe_ctlr.c
create mode 100644 drivers/scsi/fcoe/fcoe_transport.c
delete mode 100644 drivers/scsi/fcoe/libfcoe.c
create mode 100644 drivers/scsi/fcoe/libfcoe.h
--
Signature: Yi Zou <yi.zou-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
next reply other threads:[~2011-01-07 17:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 17:42 Yi Zou [this message]
2011-01-07 17:42 ` [RFC PATCH v2 1/8] libfcoe: move logging macros into the local libfcoe.h header file Yi Zou
2011-01-07 17:42 ` [RFC PATCH v2 2/8] libfcoe: add fcoe_transport structure defines to include/scsi/libfcoe.h Yi Zou
2011-01-07 17:42 ` [RFC PATCH v2 3/8] libfcoe: add implementation to support fcoe transport Yi Zou
2011-01-07 17:42 ` [RFC PATCH v2 4/8] libfcoe: rename libfcoe.c to fcoe_cltr.c for the coming fcoe_transport.c Yi Zou
2011-01-07 17:43 ` [RFC PATCH v2 5/8] libfcoe: remove libfcoe.c, use the same fcoe_ctlr.c instead Yi Zou
2011-01-07 17:43 ` [RFC PATCH v2 6/8] libfcoe: include fcoe_transport.c into kernel libfcoe module Yi Zou
2011-01-07 17:43 ` [RFC PATCH v2 7/8] fcoe: prepare fcoe for using fcoe transport Yi Zou
2011-01-07 17:43 ` [RFC PATCH v2 8/8] fcoe: convert fcoe.ko to become an fcoe transport provider driver Yi Zou
2011-01-08 1:33 ` [RFC PATCH v2 0/8] adding support to FCoE transport Bhanu Gollapudi
2011-01-11 3:27 ` Bhanu Gollapudi
2011-01-11 19:55 ` Zou, Yi
2011-01-11 21:07 ` Bhanu Gollapudi
2011-01-12 22:36 ` Bhanu Gollapudi
2011-01-13 0:39 ` Zou, Yi
2011-01-13 0:43 ` Zou, Yi
2011-01-13 0:56 ` Bhanu Gollapudi
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=20110107174027.14631.47077.stg.yi.zou@intel.com \
--to=yi.zou-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=devel-s9riP+hp16TNLxjTenLetw@public.gmane.org \
--cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).