| /dpdk/doc/guides/nics/ |
| H A D | avp.rst | 12 of the QEMU supported virtual and/or emulated devices (e.g., virtio, e1000,
14 launching a virtual machine or creating a virtual machine port. The AVP device
26 delivering packets directly to the virtual switch via a shared memory
27 mechanism. This provides DPDK applications running in virtual machines with
66 * A virtual machine running in a Wind River Systems virtualization
|
| H A D | overview.rst | 10 - virtual for emulated devices
12 Some physical devices may be shaped through a virtual layer as for
14 The interface seen in the virtual environment is a VF (Virtual Function).
|
| H A D | kni.rst | 16 will create ``kni#`` Linux virtual network interface.
18 There is no physical device backend for the virtual KNI device.
22 or to a virtual device (like another KNI interface or PCAP interface).
25 an application should control a physical port and create one virtual KNI port,
102 * Start testpmd with no physical device but two KNI virtual devices:
|
| H A D | vdev_netvsc.rst | 9 interfaces and associated SR-IOV virtual function (VF) devices found in
10 Linux virtual machines running on Microsoft Hyper-V_ (including Azure)
31 handling of physical devices is left to their original PMDs; this virtual
|
| H A D | intel_vf.rst | 24 expose them to a virtual machine as a separate PCI function called a "Virtual Function".
27 Therefore, a NIC is logically distributed among multiple virtual machines (as shown in :numref:`fig…
263 …environment, an Intel® 82576 Gigabit Ethernet Controller serves up to eight virtual machines (VMs).
487 — -hda = virtual disk image
516 replace pci-assign with vfio-pci when start virtual machine.
535 The virtual functions will be listed as available for use.
554 that can also be used to create, start, stop and delete virtual machines.
557 * virsh, a command line utility for virtual machine management,
558 can also be used to bind and unbind devices to a virtual machine in Ubuntu.
584 while others connect to a virtual switch and share the same uplink bandwidth.
[all …]
|
| H A D | enetfec.rst | 46 | | virtual ethernet device | |
77 - ENETFEC driver registers the device in virtual device driver.
126 4. The Ethernet device will be registered as virtual device,
|
| H A D | sfc_efx.rst | 174 - GENEVE (exact match of virtual network identifier, only Ethernet (0x6558)
177 - NVGRE (exact match of virtual subnet ID)
223 - GENEVE (exact match of virtual network identifier)
225 - NVGRE (exact match of virtual subnet ID)
394 In legacy mode, NIC firmware provides Ethernet virtual bridging (EVB) API
396 virtual (VF) PCI functions. PF driver is responsible to build the
400 software virtual switch (for example, Open vSwitch) makes the decision.
401 Software virtual switch may install MAE rules to pass established traffic
|
| H A D | mlx4.rst | 10 as well as their virtual functions (VF) in SR-IOV context.
34 For security reasons and robustness, this driver only deals with virtual
36 combined with hardware specifications that allow it to handle virtual memory
134 primary process and remapped to the same virtual address in secondary
136 different virtual address in secondary process, unexpected error may happen.
246 For SR-IOV virtual machine use::
|
| H A D | octeontx_ep.rst | 8 ethdev driver support for the virtual functions (VF) of **Marvell OCTEON 9**
|
| H A D | null.rst | 7 NULL PMD is a simple virtual driver mainly for testing. It always returns success for all packets f…
|
| H A D | e1000em.rst | 117 — -hda = virtual disk image
119 This command starts a new virtual machine with two emulated 82540EM devices,
|
| /dpdk/doc/guides/howto/ |
| H A D | virtio_user_for_container_networking.rst | 26 The virtual device, virtio-user, with unmodified vhost-user backend, is designed
40 context of QEMU/VM, the basic idea here is to present a kind of virtual devices,
42 QEMU in VM's context is saved by just registering a new kind of virtual device
49 all virtual memory regions to backend. So only those virtual memory regions
|
| H A D | flow_bifurcation.rst | 25 multiple virtual functions. Each virtual function (VF) has separated queues
27 virtual function with a matching destination MAC address. In a sense, SR-IOV
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | dmadev.rst | 16 physical (hardware) and virtual (software) DMA devices, as well as a generic DMA
28 * The dmadev could create multiple virtual DMA channels, each virtual DMA
30 * The DMA operation request must be submitted to the virtual DMA channel.
51 Each DMA device, whether physical or virtual is uniquely designated by two
|
| H A D | switch_representation.rst | 15 usually support the offload of traffic steering rules between their virtual
67 - DPDK port representors are implemented as additional virtual Ethernet
81 - As virtual devices, they may be more limited than their physical
88 - Applications can tell port representors apart from other physical of virtual
108 the switch ``port_id`` would represent the virtual function identifier of the
237 VF representors are virtual but standard DPDK network devices (albeit with
647 virtual function of the current device.
649 If supported, should work even if the virtual function is not managed by
661 Directs matching traffic to a given virtual function of the current device.
|
| H A D | source_org.rst | 22 devices: either hardware devices or pseudo/virtual devices. They are contained
|
| /dpdk/doc/guides/cryptodevs/ |
| H A D | armv8.rst | 29 To build DPDK with this virtual crypto PMD, the user is required to:
64 Use ``--vdev "crypto_armv8"`` in the EAL options to create virtual crypto device.
|
| /dpdk/doc/guides/bbdevs/ |
| H A D | acc100.rst | 89 The physical and virtual functions are compatible with Linux UIO drivers:
103 1. PCI functions (physical or virtual, depending on the use case) can be bound to
142 To enable VFs via igb_uio, echo the number of virtual functions intended to
164 The PCI virtual functions must be configured before working or getting assigned
|
| H A D | fpga_5gnr_fec.rst | 74 The physical and virtual functions are compatible with Linux UIO drivers:
88 1. PCI functions (physical or virtual, depending on the use case) can be bound to
127 To enable VFs via igb_uio, echo the number of virtual functions intended to
149 The PCI virtual functions must be configured before working or getting assigned
|
| H A D | fpga_lte_fec.rst | 73 The physical and virtual functions are compatible with Linux UIO drivers:
87 1. PCI functions (physical or virtual, depending on the use case) can be bound to
126 To enable VFs via igb_uio, echo the number of virtual functions intended to
148 The PCI virtual functions must be configured before working or getting assigned
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | bbdev_app.rst | 61 a SW baseband device/s (virtual BBdev) must be created (using --vdev).
74 This command creates one virtual bbdev devices ``baseband_turbo_sw`` where the
|
| H A D | vm_power_management.rst | 7 Applications running in virtual environments have an abstract view of
9 see the binding of virtual components to physical hardware. When looking
31 virtual CPU (vCPU) request to a physical CPU (pCPU) request and
64 virtual machines, and the VM Power Monitor application is shown running
79 - Commands include the virtual core to be modified, using ``libvirt`` to get
290 Now, it is possible to add virtual machines to the VM Power Manager:
304 Remove the virtual machine identified by ``{vm_name}`` from the VM Power
360 Set the binding of a virtual CPU on a VM with name ``{vm_name}`` to the
367 Set the binding of the virtual CPU on the VM to the physical CPU:
530 Allows the user to change the virtual machine name
[all …]
|
| H A D | l2_forward_real_virtual.rst | 63 This application can use the virtual function available in the system and
64 therefore can be used in a virtual machine without passing through
66 The virtual functions can be enabled in the host machine or the hypervisor with the respective phys…
68 For example, in a Linux* host machine, it is possible to enable a virtual function using the follow…
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_2_2.rst | 13 * ARMv7 can be tested with virtual PMDs.
14 * ARMv8 can be tested with virtual and physical PMDs.
100 * Added VF capabilities to virtual channel interface
161 * **Added virtual szedata2 driver for COMBO cards.**
163 Added virtual PMD for COMBO-100G and COMBO-80G cards.
527 * The devargs union field ``virtual`` is renamed to ``virt`` for C++
|
| /dpdk/doc/guides/dmadevs/ |
| H A D | dpaa.rst | 56 - Supports 1 virtual channel.
|