Lines Matching refs:link

40   physical link to the switch for communication. Each N_Port_ID can have a
84   a new scsi_host for the vport and link its object under the vport.
88   This could be used in the future to link the object onto a vm-specific
90   a symbolic link to the vport object will be placed in the physical
146        but it will not be active on the FC link.
194       independent of the adapter's link state.
195     - Instantiation of the vport on the FC link via ELS traffic, etc.
196       This is equivalent to a "link up" and successful link initialization.
208       The vport has been successfully been created on the FC link.
213       on the FC link. This is equivalent to a physical port with the
214       link "down".
217       The vport is not operational as the physical link is not operational.
220       The vport is in the process of instantiating on the FC link.
323       independent of the adapter's link state.
324     - Instantiation of the vport on the FC link via ELS traffic, etc.
325       This is equivalent to a "link up" and successful link initialization.
331   hinge vport_create() on the link-side operation mainly because:
332     - The link may be down. It is not a failure if it is. It simply
333       means the vport is in an inoperable state until the link comes up.
334       This is consistent with the link bouncing post vport creation.
338       to the adapter, which is independent of link state.
360         link state - and return success (zero).
370     for the physical port only (link speed, topology setting, etc). This
394   the kernel and LLDD, but it is not active or visible on the FC link in
398   link - essentially restarting the LLDD statemachine (see Vport States
413   the LLDD to terminate the vport on the FC link, and teardown all other