3143d86b69
Updates for patchset 2 review comments Changed link depth of main Planning index and added some narrative guidance Added planning/openstack as sibling of planning/kubernetes Related additions to abbrevs.txt Added max-workers substitution to accomodate StarlingX/vendor variants Signed-off-by: Ron Stone <ronald.stone@windriver.com> Change-Id: Ibff9af74ab3f2c00958eff0e33c91465f1dab6b4 Signed-off-by: Stone <ronald.stone@windriver.com>
29 lines
1.0 KiB
ReStructuredText
Executable File
29 lines
1.0 KiB
ReStructuredText
Executable File
|
|
.. osb1466081265288
|
|
.. _pci-passthrough-ethernet-interfaces:
|
|
|
|
===================================
|
|
PCI Passthrough Ethernet Interfaces
|
|
===================================
|
|
|
|
A passthrough Ethernet interface is a physical |PCI| Ethernet |NIC| on a
|
|
compute node to which a virtual machine is granted direct access.
|
|
|
|
This minimizes packet processing delays but at the same time demands special
|
|
operational considerations.
|
|
|
|
For all purposes, a |PCI| passthrough interface behaves as if it were
|
|
physically attached to the virtual machine. Therefore, any potential throughput
|
|
limitations coming from the virtualized environment, such as the ones
|
|
introduced by internal copying of data buffers, are eliminated. However, by
|
|
bypassing the virtualized environment, the use of |PCI| passthrough Ethernet
|
|
devices introduces several restrictions that you must take into consideration.
|
|
They include:
|
|
|
|
|
|
.. _pci-passthrough-ethernet-interfaces-ul-mjs-m52-tp:
|
|
|
|
- no support for |LAG|, |QoS|, |ACL|, or host interface monitoring
|
|
|
|
- no support for live migration
|