Home
last modified time | relevance | path

Searched refs:devices (Results 1 – 25 of 175) sorted by relevance

1234567

/dpdk/usertools/
H A Ddpdk-devbind.py89 devices = {} variable
192 global devices
193 devices = {}
200 global devices
249 devices[d] = devices[d].copy()
302 if dev_name in devices:
319 dev = devices[dev_id]
345 dev = devices[dev_id]
471 global devices
510 devices[d] = dict(devices[d].items()
[all …]
/dpdk/doc/guides/tools/
H A Ddevbind.rst8 that helps binding and unbinding devices from specific drivers.
52 By default, devices which are used by Linux - as indicated by having
62 Due to the way VFIO works, there are certain limitations to which devices can be used with VFIO.
64 …Any Virtual Function device can be used with VFIO on its own, but physical devices will require ei…
68 … should also be unbound from the bridge PCI device for VFIO to work with devices behind the bridge.
97 # Check the status of the available devices.
99 Network devices using DPDK-compatible driver
103 Network devices using kernel driver
112 # Recheck the status of the devices.
114 Network devices using DPDK-compatible driver
/dpdk/doc/guides/dmadevs/
H A Dioat.rst22 will show all the DMA devices on the system, IOAT devices are included in this
23 list. For Intel\ |reg| IOAT devices, the hardware will often be listed as
41 Intel\ |reg| IOAT devices will need to be bound to a suitable DPDK-supported
44 The ``dpdk-devbind.py`` script can be used to view the state of the devices using::
48 The ``dpdk-devbind.py`` script can also be used to bind devices to a suitable driver.
56 For devices bound to a suitable DPDK-supported driver (``vfio-pci``), the HW
57 devices will be found as part of the device scan done at application
60 If the application does not require all the devices available an allowlist can
61 be used in the same way that other DPDK devices use them.
74 To use IOAT devices from an application, the ``dmadev`` API can be used.
H A Didxd.rst12 This PMD can be used in conjunction with Intel\ |reg| DSA devices to offload
21 will show all the DMA devices on the system, including IDXD supported devices.
22 Intel\ |reg| DSA devices, are currently (at time of writing) appearing
23 as devices with type “0b25”, due to the absence of pci-id database entries for
38 Intel\ |reg| DSA devices using IDXD kernel driver
75 Once the devices have been configured, they need to be enabled::
114 The ``dpdk-devbind.py`` script can be used to view the state of the devices
123 For devices bound to a suitable DPDK-supported VFIO/UIO driver, the HW devices will
135 For devices bound to the IDXD kernel driver,
162 To use the devices from an application, the dmadev API can be used.
[all …]
H A Dcnxk.rst29 Running ``dpdk-devbind.py --status-dev dma`` will show all the CNXK DMA devices.
34 The HW devices to be used will need to be bound to a user-space IO driver for use.
35 The ``dpdk-devbind.py`` script can be used to view the state of the devices
44 To use the devices from an application, the dmadev API can be used.
48 * CNXK DMA devices do not support silent mode.
/dpdk/doc/guides/regexdevs/
H A Dcn9k.rst30 The CN9K REE devices will need to be bound to a user-space IO driver
32 used to view the state of the devices and to bind them to a suitable
33 DPDK-supported kernel driver. When querying the status of the devices,
34 they will appear under the category of "REGEX devices", i.e. the command
36 those devices alone.
/dpdk/doc/guides/prog_guide/
H A Dlink_bonding_poll_mode_drv_lib.rst25 creation of bonded devices as well as the configuration and management of the
26 bonded device and its slave devices.
49 the last. Packets are bulk dequeued from devices then serviced in a
143 Bonded devices support the dynamical addition and removal of slave devices using
247 possible, when all slave devices support the same key size.
265 Link bonding devices are created using the ``rte_eth_bond_create`` API
275 Bonding devices support up to a maximum of ``RTE_MAX_ETHPORTS`` slave devices
277 maximum of one bonded device. Slave devices are reconfigured with the
299 the bonded devices MAC address.
428 the bonded devices resources will be allocated on.
[all …]
H A Dsource_org.rst22 devices: either hardware devices or pseudo/virtual devices. They are contained
H A Drawdev.rst23 way to manage such devices in a generic manner without expecting changes to
26 interfacing with such type of devices.
89 Physical rawdev devices are discovered during the Bus scan executed at DPDK
94 Virtual devices can be created by two mechanisms, either using the EAL command
H A Dregexdev.rst18 and virtual (software) RegEx devices as well as a generic RegEx API which allows
19 RegEx devices to be managed and configured and supports RegEx operations to be
29 Physical RegEx devices are discovered during the PCI probe/enumeration of the
32 function). Specific physical ReEx devices, like other physical devices in DPDK
153 RegEx devices may support different feature set.
/dpdk/doc/guides/nics/
H A Doverview.rst9 - physical for real devices
10 - virtual for emulated devices
12 Some physical devices may be shaped through a virtual layer as for
17 of these devices.
H A Dvdev_netvsc.rst9 interfaces and associated SR-IOV virtual function (VF) devices found in
18 Each instance of this driver effectively needs to drive two devices: the
22 Physical devices are part of the host system and cannot be maintained during
23 VM migration. From a VM standpoint they appear as hot-plug devices that come
31 handling of physical devices is left to their original PMDs; this virtual
H A Dfail_safe.rst26 meant to be removed itself, unlike its sub-devices which should support it.
28 automatically by detecting capable devices and registering the relevant handler.
36 The Fail-safe PMD can be used like most other DPDK virtual devices, by passing a
79 executing the command. This helps using scripts to specify devices.
93 and all of its sub-devices.
96 its default MAC address, trying to set it to all of its other sub-devices.
98 address is generated, that will be subsequently applied to all sub-devices once
161 over ethernet devices, instead of directly accessing them or by writing one's
193 synchronized with other sub-devices, i.e. be started if the fail-safe PMD has
222 Periodical event during which sub-devices are serviced. Each devices having a state
H A Dintel_vf.rst414 echo 2 > /sys/bus/pci/devices/0000\:02\:00.0/max_vfs
415 echo 2 > /sys/bus/pci/devices/0000\:02\:00.1/max_vfs
416 echo 2 > /sys/bus/pci/devices/0000\:0e\:00.0/max_vfs
417 echo 2 > /sys/bus/pci/devices/0000\:0e\:00.1/max_vfs
439 ls -alrt /sys/bus/pci/devices/0000\:02\:00.0/virt*
447 ls -alrt /sys/bus/pci/devices/0000\:02\:00.1/virt*
462 Unbind the default driver from the PCI devices representing the Virtual Functions.
468 echo 0000:08:10.0 > /sys/bus/pci/devices/0000:08:10.0/driver/unbind
497 — qemu-kvm-0.14.0 allows a maximum of four PCI devices assigned to a VM,
523 echo 0000:08:10.0 > /sys/bus/pci/devices/0000:08:10.0/driver/unbind
[all …]
/dpdk/doc/guides/howto/
H A Dlm_virtio_vhost_user.rst266 cat /sys/bus/pci/devices/0000\:02\:00.0/max_vfs
267 echo 0 > /sys/bus/pci/devices/0000\:02\:00.0/max_vfs
268 cat /sys/bus/pci/devices/0000\:02\:00.0/max_vfs
271 cat /sys/bus/pci/devices/0000\:09\:00.0/max_vfs
272 echo 0 > /sys/bus/pci/devices/0000\:09\:00.0/max_vfs
273 cat /sys/bus/pci/devices/0000\:09\:00.0/max_vfs
342 cat /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
343 echo 0 > /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
344 cat /sys/bus/pci/devices/0000\:06\:00.0/max_vfs
347 cat /sys/bus/pci/devices/0000\:03\:00.0/max_vfs
[all …]
H A Dpvp_reference_benchmark.rst57 cat /sys/devices/system/cpu/cpu*[0-9]/topology/thread_siblings_list \
59 | awk -F, '{system("echo 0 > /sys/devices/system/cpu/cpu"$2"/online")}'
71 echo ffffff03 > /sys/bus/workqueue/devices/writeback/cpumask
150 Launch QEMU with two Virtio-net devices paired to the vhost-user sockets
218 important information (hugepages, vCPU pinning, Virtio PCI devices):
251 <devices>
266 </devices>
293 echo 1 > /sys/bus/workqueue/devices/writeback/cpumask
325 Bind the virtio-net devices to DPDK:
H A Dlm_bond_virtio_sriov.rst386 cat /sys/bus/pci/devices/0000\:09\:00.0/sriov_numvfs
387 echo 1 > /sys/bus/pci/devices/0000\:09\:00.0/sriov_numvfs
388 cat /sys/bus/pci/devices/0000\:09\:00.0/sriov_numvfs
392 cat /sys/bus/pci/devices/0000\:02\:00.0/sriov_numvfs
393 echo 1 > /sys/bus/pci/devices/0000\:02\:00.0/sriov_numvfs
394 cat /sys/bus/pci/devices/0000\:02\:00.0/sriov_numvfs
486 cat /sys/bus/pci/devices/0000\:06\:00.0/sriov_numvfs
487 echo 1 > /sys/bus/pci/devices/0000\:06\:00.0/sriov_numvfs
488 cat /sys/bus/pci/devices/0000\:06\:00.0/sriov_numvfs
492 cat /sys/bus/pci/devices/0000\:03\:00.0/sriov_numvfs
[all …]
/dpdk/doc/guides/rawdevs/
H A Dioat.rst29 or rawdev-based devices on the system.
32 For Intel\ |reg| DSA devices, they are currently (at time of writing) appearing as devices with typ…
57 Intel\ |reg| DSA devices using idxd kernel driver
95 Once the devices have been configured, they need to be enabled::
107 The HW devices to be used will need to be bound to a user-space IO driver for use.
108 The ``dpdk-devbind.py`` script can be used to view the state of the devices
117 For devices bound to a suitable DPDK-supported VFIO/UIO driver, the HW devices will
129 For devices bound to the IDXD kernel driver,
146 To use the devices from an application, the rawdev API can be used, along
150 devices, as well as providing key functions for using the device for memory
[all …]
H A Dcnxk_bphy.rst26 The BPHY CGX/RPM devices will need to be bound to a user-space IO driver for
28 view the state of the devices and to bind them to a suitable DPDK-supported
29 kernel driver. When querying the status of the devices, they will appear under
30 the category of "Misc (rawdev) devices", i.e. the command
32 devices alone.
144 On EAL initialization BPHY and BPHY CGX/RPM devices will be probed and populated into
145 the raw devices. The rawdev ID of the device can be obtained using invocation
H A Ddpaa2_cmdif.rst9 via using the DPCI devices exposed by MC for GPP <--> AIOP interaction.
58 The DPAA2 CMDIF is exposed as a vdev device which consists of dpci devices.
59 On EAL initialization, dpci devices will be probed and then vdev device
/dpdk/doc/guides/linux_gsg/
H A Dlinux_drivers.rst54 to which devices can be used with VFIO.
57 but physical devices may require either all ports bound to VFIO,
63 for VFIO to work with devices behind the bridge.
77 Network devices using DPDK-compatible driver
82 Network devices using kernel driver
89 Other network devices
156 After that, VFIO can be used with hardware devices as usual.
197 and use it to initialize both VF and PF devices.
222 #. Bind the PCI devices to ``vfio-pci`` driver
228 #. Create the desired number of VF devices
[all …]
/dpdk/doc/guides/sample_app_ug/
H A Dl2_forward_crypto.rst159 The application requires that crypto devices capable of performing
164 To run the application in linux environment with 2 lcores, 2 ports and 2 crypto devices, issue the …
182 * If multiple Ethernet ports is passed, then equal number of crypto devices are to be passed.
184 * All crypto devices shall use the same session.
235 to make sure that it is supported by the crypto devices.
240 Once the encryption operation is defined, crypto devices are initialized.
241 The crypto devices must be either bound to a DPDK driver (if they are physical devices)
242 or created using the EAL option --vdev (if they are virtual devices),
246 It iterates through the list of the available crypto devices and
274 The number of crypto devices that supports the specified crypto operation
[all …]
/dpdk/doc/guides/cryptodevs/
H A Dqat.rst20 poll mode crypto driver support for the following hardware accelerator devices:
117 * ZUC EEA3/EIA3 is not supported by dh895xcc devices
124 generations of QAT devices on a single platform.
324 devices created and initialised by this driver will be used by the QAT PMDs.
327 relationships between the PF/VF devices and the PMDs visible to
335 devices to applications.
356 .. table:: QAT device generations, devices and drivers
397 devices. p = release pending.
444 list 48 VF devices available for a ``C62x`` device.
513 Confirm the presence of 48 VF devices - 16 per PF::
[all …]
/dpdk/doc/guides/eventdevs/
H A Ddpaa2.rst51 devices and dpci devices. On EAL initialization, dpcon and dpci devices will be
/dpdk/doc/guides/rel_notes/
H A Drelease_1_8.rst14 * Support for registration of link status change callbacks with link bonding devices.
16 …* Support for slaves devices which do not support link status change interrupts in the link bond…

1234567