From: Vasu Dev <vasu.dev@intel.com>
To: linux-scsi@vger.kernel.org, devel@open-fcoe.org
Subject: [PATCH 0/5] Series short description
Date: Mon, 25 Feb 2008 03:20:04 -0800 [thread overview]
Message-ID: <20080225111856.22380.70951.stgit@vdinit.jf.intel.com> (raw)
The following series implements...
Currently OpenFC maintains several control structures for each enabled fcoe
interface, such as inner and outer fc_port, fcdev, openfc_softc,
fcs_state (for fc_local_port and fc_virt_fab) etc. Here fc_port should not
be confused with FC protocol's ports related structs, instead fc_port provides
generic/portable interface to FCS sub module embedded inside openFC
for egress, ingress handlers and sa events lists to OpenFC per FCoE interface
instance.
I removed outer port instance in these patches, instead used existing fcdev
structure by direct functions calls between FCS & OpenFC for outer port
egress and inegress functions. The fcdev is key shared structure per FCoE
interface between OpenFC and FCoE modules, fcdev can be extended for all
libfc(TBD) users to access per libfc user instance.
Consolidation of more control structures in fcdev will simplify openFC
implementation which will help in converting OpenFC into generic libfc
library as suggested by linux-scsi reviewers.
--
Signature : Vasu Dev <vasu.dev@intel.com>
next reply other threads:[~2008-02-25 19:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 11:20 Vasu Dev [this message]
2008-02-25 11:20 ` [PATCH 1/5] Removed outer port allocation Vasu Dev
2008-02-25 11:20 ` [PATCH 2/5] Removed outer port use from fcs Vasu Dev
2008-02-25 11:20 ` [PATCH 3/5] Removed outer port use in fc_exch Vasu Dev
2008-02-25 11:20 ` [PATCH 4/5] Fixed style error reported by checkpatch Vasu Dev
2008-02-25 11:20 ` [PATCH 5/5] Removed fc_port from fc_frame_alloc() Vasu Dev
-- strict thread matches above, loose matches on Subject: below --
2008-06-12 4:54 [PATCH 0/5] Series short description Ian Kent
2008-06-12 6:15 ` Ian Kent
2009-11-17 14:50 Alan Cox
2009-11-19 21:41 ` Jeff Garzik
2010-06-07 4:11 Bruno Randolf
2010-11-16 20:49 John Bonesio
2010-11-16 20:49 ` John Bonesio
2010-11-16 20:49 ` John Bonesio
2013-12-24 7:52 Ian Kent
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=20080225111856.22380.70951.stgit@vdinit.jf.intel.com \
--to=vasu.dev@intel.com \
--cc=devel@open-fcoe.org \
--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 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.