Lines Matching full:virtual

24 virtual switches and IOV devices.  Just as each physical port of a Linux-
25 controlled switch has a separate netdev, so does each virtual port of a virtual
28 the virtual functions appear in the networking stack of the PF via the
29 representors.  The PF can thus always communicate freely with the virtual
35 administrative commands) and a data plane object (one end of a virtual pipe).
36 As a virtual link endpoint, the representor can be configured like any other
45 which has administrative control over the virtual switch on the device.
49 for the whole device or might have a separate virtual switch, and hence
69    fast-path rules in the virtual switch.  Packets transmitted on the
72    be received on the representor netdevice.  (That is, there is a virtual pipe
90 Essentially, for each virtual port on the device's internal switch, there
105    if) their network access is implemented through a virtual switch port. [#]_
111    through a virtual switch port, even if they do not have a corresponding PCIe
117 It is a common misunderstanding to conflate virtual ports with PCIe virtual
125 Such a function has no switch virtual port for the representor to configure or
126 to be the other end of the virtual pipe.
127 The representor represents the virtual port, not the PCIe function nor the 'end
132    network packets pass through the virtual port onto the switch.  The network
141    run over the virtual switch and the virtio-blk PF should thus *not* have a
147 The driver instance attached to the switchdev function should, for each virtual
188 to another port on the virtual switch, the driver may choose to offload it to
214 actions (e.g. VLAN push/pop), which should be performed by the virtual switch.