1. 02 5月, 2013 1 次提交
    • H
      [SCSI] fnic: FIP VLAN Discovery Feature Support · d3c995f1
      Hiral Patel 提交于
      FIP VLAN discovery discovers the FCoE VLAN that will be used by all other FIP
      protocols as well as by the FCoE encapsulation for Fibre Channel payloads on
      the established virtual link. One of the goals of FC-BB-5 was to be as
      nonintrusive as possible on initiators and targets, and therefore FIP VLAN
      discovery occurs in the native VLAN used by the initiator or target to
      exchange Ethernet traffic. The FIP VLAN discovery protocol is the only FIP
      protocol running on the native VLAN; all other FIP protocols run on the
      discovered FCoE VLANs.
      
      If an administrator has manually configured FCoE VLANs on ENodes and FCFs,
      there is no need to use this protocol. FIP and FCoE will run over the
      configured VLANs.
      
      An ENode without FCoE VLANs configuration would use this automated discovery
      protocol to discover over which VLANs FCoE is running.
      
      The ENode sends a FIP VLAN discovery request to a multicast MAC address called
      All-FCF-MACs, which is a multicast MAC address to which all FCFs listen.
      
      All FCFs that can be reached in the native VLAN of the ENode are expected to
      respond on the same VLAN with a response that lists one or more FCoE VLANs
      that are available for the ENode's VN_Port login. This protocol has the sole
      purpose of allowing the ENode to discover all the available FCoE VLANs.
      
      Now the ENode may enable a subset of these VLANs for FCoE Running the FIP
      protocol in these VLANs on a per VLAN basis. And FCoE data transactions also
      would occur on this VLAN. Hence, Except for FIP VLAN discovery, all other FIP
      and FCoE traffic runs on the selected FCoE VLAN.  Its only the FIP VLAN
      Discovery protocol that is permitted to run on the Default native VLAN of the
      system.
      
      [**** NOTE ****]
      We are working on moving this feature definitions and functionality to libfcoe
      module. We need this patch to be approved, as Suse is looking forward to merge
      this feature in SLES 11 SP3 release.  Once this patch is approved, we will
      submit patch which should move vlan discovery feature to libfoce.
      
      [Fengguang Wu <fengguang.wu@intel.com>: kmalloc cast removal]
      Signed-off-by: NAnantha Prakash T <atungara@cisco.com>
      Signed-off-by: NHiral Patel <hiralpat@cisco.com>
      Signed-off-by: NJames Bottomley <JBottomley@Parallels.com>
      d3c995f1
  2. 29 1月, 2013 1 次提交
  3. 31 3月, 2011 1 次提交
  4. 12 4月, 2010 1 次提交
  5. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  6. 05 12月, 2009 1 次提交
    • J
      [SCSI] fnic: Add FIP support to the fnic driver · 78112e55
      Joe Eykholt 提交于
      Use libfcoe as a common FIP implementation with fcoe.
      FIP or non-FIP mode is fully automatic if the firmware
      supports and enables it.
      
      Even if FIP is not supported, this uses libfcoe for the non-FIP
      handling of FLOGI and its response.
      
      Use the new lport_set_port_id() notification to capture
      successful FLOGI responses and port_id resets.
      
      While transitioning between Ethernet and FC mode, all rx and
      tx FC frames are queued.  In Ethernet mode, all frames are
      passed to the exchange manager to capture FLOGI responses.
      
      Change to set data_src_addr to the ctl_src_addr whenever it
      would have previously been zero because we're not logged in.
      This seems safer so we'll never send a frame with a 0 source MAC.
      This also eliminates a special case for sending FLOGI frames.
      Signed-off-by: NJoe Eykholt <jeykholt@cisco.com>
      Signed-off-by: NRobert Love <robert.w.love@intel.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@suse.de>
      78112e55
  7. 23 8月, 2009 1 次提交
    • V
      [SCSI] fcoe, fnic, libfc: modifies current code paths to use EM anchor list · 52ff878c
      Vasu Dev 提交于
      Modifies current code to use EM anchor list in EM allocation, EM free,
      EM reset, exch allocation and exch lookup code paths.
      
       1. Modifies fc_exch_mgr_alloc to accept EM match function and then
          have allocated EM added to the lport using fc_exch_mgr_add API
          while also updating EM kref for newly added EM.
      
       2. Updates fc_exch_mgr_free API to accept only lport pointer instead
          EM and then have this API free all EMs of the lport from EM anchor
          list.
      
       3. Removes single lport pointer link from the EM, which was used in
          associating lport pointer in newly allocated exchange. Instead have
          lport pointer passed along new exchange allocation call path and
          then store passed lport pointer in newly allocated exchange, this
          will allow a single EM instance to be used across more than one
          lport and used in EM reset to reset only lport specific exchanges.
      
       4. Modifies fc_exch_mgr_reset to reset all EMs from the EM anchor list
          of the lport, adds additional exch lport pointer (ep->lp) check for
          shared EM case to reset exchange specific to a lport requested reset.
      
       5. Updates exch allocation API fc_exch_alloc to use EM anchor list and
          its anchor match func pointer. The fc_exch_alloc will walk the list
          of EMs until it finds a match, a match will be either null match
          func pointer or call to match function returning true value.
      
       6. Updates fc_exch_recv to accept incoming frame on local port using
          only lport pointer and frame pointer without specifying EM instance
          of incoming frame. Instead modified fc_exch_recv to locate EM for the
          incoming frame by matching xid of incoming frame against a EM xid range.
          This change was required to use EM list in libfc Rx path and after this
          change the lport fc_exch_mgr pointer emp is not needed anymore, so
          removed emp pointer.
      
       7. Updates fnic for removed lport emp pointer and above modified libfc APIs
          fc_exch_recv, fc_exch_mgr_alloc and fc_exch_mgr_free.
      
       8. Removes exch_get and exch_put from libfc_function_template as these
          are no longer needed with EM anchor list and its match function use.
          Also removes its default function fc_exch_get.
      
      A defect this patch introduced regarding the libfc initialization order in
      the fnic driver was fixed by Joe Eykholt <jeykholt@cisco.com>.
      Signed-off-by: NVasu Dev <vasu.dev@intel.com>
      Signed-off-by: NRobert Love <robert.w.love@intel.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@HansenPartnership.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@suse.de>
      52ff878c
  8. 14 5月, 2009 1 次提交