Lines Matching refs:vport
57 The FC transport is now recognizing a new object - a vport. A vport is
60 be specified for the vport, with FCP_Initiator being the primary role
64 to create vports. The transport will create the vport object within the
67 on the vport, resulting in a unique <H,C,T,L> namespace for the vport.
79 up to an administrative entity controlling the vport. For example,
81 utility would be responsible for creating wwpn/wwnn's for the vport,
91 transport creates the vport object and places it under the scsi_host
93 a new scsi_host for the vport and link its object under the vport.
96 allow the parent of the vport to be something other than the scsi_host.
98 device tree. If the vport's parent is not the physical port's scsi_host,
99 a symbolic link to the vport object will be placed in the physical
112 and then the vport is created on the Physical Port::
114 /sys/devices/.../host17/vport-17:0-0
116 and the vport's Scsi_Host is then created::
118 /sys/devices/.../host17/vport-17:0-0/host18
122 /sys/devices/.../host17/vport-17:0-0/host18/rport-18:0-0/target18:0:0/18:0:0:0:
128 /sys/class/scsi_host/host18 vport's scsi_host
131 /sys/class/fc_host/host18 vport's fc_host
133 /sys/class/fc_vports/vport-17:0-0 the vport's fc_vport
136 /sys/class/fc_remote_ports/rport-18:0-0 rport on the vport
145 The WWNN of the vport
148 The WWPN of the vport
151 Indicates the FC4 roles enabled on the vport.
155 is registered with the switch to identify the vport. For example,
161 When written with a "1", will tear down the vport.
164 When written with a "1", will transition the vport to a disabled.
165 state. The vport will still be instantiated with the Linux kernel,
167 When written with a "0", will enable the vport.
170 Indicates the previous state of the vport. See the section below on
174 Indicates the state of the vport. See the section below on
193 A "simple" create interface to instantiate a vport on an fc_host.
195 then instantiates the vport object and calls the LLDD to create the
196 vport with the role of FCP_Initiator. Each WWN is specified as 16
200 A "simple" delete interface to teardown a vport. A "<WWPN>:<WWNN>"
202 vport on the fc_host with the same WWNs and tear it down. Each WWN
216 - Instantiation of the vport on the FC link via ELS traffic, etc.
222 Once a vport has been instantiated with the kernel/LLDD, a vport state
226 An temporary state, typically set only while the vport is being
230 The vport has been successfully been created on the FC link.
234 The vport instantiated, but "disabled". The vport is not instantiated
239 The vport is not operational as the physical link is not operational.
242 The vport is in the process of instantiating on the FC link.
244 to create the vport. This state will persist until the vport is
250 The vport is not operational. One of the following conditions were
258 The vport is not operational. The Fabric failed FDISC with a status
263 The vport is not operational. The Fabric has LOGO'd the N_Port_ID
264 associated with the vport.
267 The vport is not operational. The Fabric failed FDISC with a status
271 The vport is not operational. This is a catchall for all other
349 int vport_create(struct fc_vport *vport, bool disable)
354 vport Is the newly allocated vport object
355 disable If "true", the vport is to be created in a disabled stated.
356 If "false", the vport is to be enabled upon creation.
359 When a request is made to create a new vport (via sgio/netlink, or the
361 can support another vport (e.g. max_npiv_vports > npiv_vports_inuse).
363 will increment the vport count, create the vport object, and then call the
364 LLDD's vport_create() function with the newly allocated vport object.
366 As mentioned above, vport creation is divided into two parts:
372 - Instantiation of the vport on the FC link via ELS traffic, etc.
378 vport creation (data structure build up) before returning. We do not
382 means the vport is in an inoperable state until the link comes up.
383 This is consistent with the link bouncing post vport creation.
384 - The vport may be created in a disabled state.
385 - This is consistent with a model where: the vport equates to a
398 - If the driver or adapter cannot support another vport, whether
410 - Call scsi_host_alloc() to allocate a scsi_host for the vport.
411 - Call scsi_add_host(new_shost, &vport->dev) to start the scsi_host
412 and bind it as a child of the vport device.
415 - Kick of further vport state transitions based on the disable flag and
435 int vport_disable(struct fc_vport *vport, bool disable)
440 vport Is vport to be enabled or disabled
441 disable If "true", the vport is to be disabled.
442 If "false", the vport is to be enabled.
445 When a request is made to change the disabled state on a vport, the
446 transport will validate the request against the existing vport state.
447 If the request is to disable and the vport is already disabled, the
449 vport is not in a disabled state, the request will fail. If the request
450 is valid for the vport state, the transport will call the LLDD to
451 change the vport's state.
453 Within the LLDD, if a vport is disabled, it remains instantiated with
456 The vport will remain in this state until it is deleted or re-enabled.
457 When enabling a vport, the LLDD reinstantiates the vport on the FC
466 int vport_delete(struct fc_vport *vport)
470 vport: Is vport to delete
472 When a request is made to delete a vport (via sgio/netlink, or via the
474 the LLDD to terminate the vport on the FC link, and teardown all other
476 the transport will teardown the vport objects and complete the vport
477 removal. If the LLDD delete request fails, the vport object will remain,
481 be followed. E.g. If the vport has a FCP Initiator role, the LLDD
489 must be set on all vport-based fc_hosts. Normally, on a physical port,
492 a vport, it makes more sense to report the FC mechanism used to create
493 the vport.
508 fc_vport_create create a vport
509 fc_vport_terminate detach and remove a vport
515 * fc_vport_create - Admin App or LLDD requests creation of a vport
527 * fc_vport_terminate - Admin App or LLDD requests termination of a vport
528 * @vport: fc_vport to be terminated
531 * the vport from the shost and object tree.
537 fc_vport_terminate(struct fc_vport *vport)