Lines Matching refs:with

44   interact with the Fabric Port to join multiple fabrics. The port will
47   used together with VF so that the port can obtain multiple N_Port_IDs
53   be specified for the vport, with FCP_Initiator being the primary role
56   The fc_host associated with the physical adapter will export the ability
62   each will appear as a unique scsi_host with its own target and lun space.
71     if vports are to be associated with virtual machines, a XEN mgmt
81   with rports and scsi target objects underneath it. Currently the FC
135        is registered with the switch to identify the vport. For example,
141        When written with a "1", will tear down the vport.
144        When written with a "1", will transition the vport to a disabled.
145        state.  The vport will still be instantiated with the Linux kernel,
147        When written with a "0", will enable the vport.
176        vport with the role of FCP_Initiator.  Each WWN is specified as 16
182         vport on the fc_host with the same WWNs and tear it down.  Each WWN
191     - Creation with the kernel and LLDD. This means all transport and
200   Once a vport has been instantiated with the kernel/LLDD, a vport state
205       instantiated with the kernel and LLDD.
213       on the FC link. This is equivalent to a physical port with the
235       The vport is not operational. The Fabric failed FDISC with a status
241       associated with the vport.
244       The vport is not operational. The Fabric failed FDISC with a status
317   LLDD's vport_create() function with the newly allocated vport object.
320     - Creation with the kernel and LLDD. This means all transport and
334       This is consistent with the link bouncing post vport creation.
336     - This is consistent with a model where:  the vport equates to a
337       FC adapter. The vport_create is synonymous with driver attachment
393   Within the LLDD, if a vport is disabled, it remains instantiated with