Home
last modified time | relevance | path

Searched refs:probed (Results 1 – 25 of 28) sorted by relevance

12

/dpdk/drivers/bus/vmbus/
H A Dvmbus_common.c175 size_t probed = 0, failed = 0; in rte_vmbus_probe() local
179 probed++; in rte_vmbus_probe()
193 return (probed && probed == failed) ? -1 : 0; in rte_vmbus_probe()
/dpdk/drivers/bus/auxiliary/
H A Dauxiliary_common.c217 size_t probed = 0, failed = 0; in auxiliary_probe() local
221 probed++; in auxiliary_probe()
235 return (probed && probed == failed) ? -1 : 0; in auxiliary_probe()
/dpdk/doc/guides/vdpadevs/
H A Dsfc.rst20 will be probed by net/sfc driver and will used as a net device.
70 **net** device will work as network device and will be probed by net/sfc driver.
71 **vdpa** device will work as vdpa device and will be probed by vdpa/sfc driver.
H A Difc.rst19 probed by IFCVF driver, adding "vdpa=1" parameter helps to specify that this
/dpdk/doc/guides/mempool/
H A Dcnxk.rst62 provide ``max_pools`` parameter to the first PCIe device probed by the given
84 driver configures an NPA LF and attach to the first probed ethdev or eventdev
/dpdk/doc/guides/nics/
H A Dfail_safe.rst63 When trying to use a PCI device automatically probed by the command line,
95 address of the first of its sub-device to be successfully probed and use it as
97 If no sub-device was successfully probed at initialization, then a random MAC
99 they are probed.
123 If the sub-device ``84:00.0`` is not blocked, it will be probed by the
H A Docteontx.rst113 PKI/PKO PCIe VF devices will be probed and then the vdev device can be created
115 the number of probed/bound PKI/PKO PCIe VF device to DPDK by
H A Dsfc_efx.rst387 **net** device will work as network device and will be probed by net/sfc driver.
388 **vdpa** device will work as vdpa device and will be probed by vdpa/sfc driver.
H A Dmlx4.rst89 times for additional ports. All ports are probed by default if left
/dpdk/drivers/bus/pci/
H A Dpci_common.c374 size_t probed = 0, failed = 0; in pci_probe() local
378 probed++; in pci_probe()
394 return (probed && probed == failed) ? -1 : 0; in pci_probe()
/dpdk/doc/guides/eventdevs/
H A Docteontx.rst50 SSO PCIe VF devices will be probed and then the vdev device can be created
52 the number of probed/bound SSO PCIe VF device to DPDK by
H A Ddpaa.rst49 probed and then vdev device can be created from the application code by
H A Ddpaa2.rst52 probed and then vdev device can be created from the application code by
/dpdk/doc/guides/dmadevs/
H A Dhisilicon.rst28 Once probed successfully, the device will appear as four ``dmadev``
H A Ddpaa.rst49 will be probed and populated into their device list.
H A Didxd.rst139 probed by the driver to make them available to the application.
155 Once probed successfully, irrespective of kernel driver, the device will appear as a ``dmadev``,
H A Dioat.rst67 Once probed successfully, the device will appear as a ``dmadev``, that is a
/dpdk/doc/guides/rawdevs/
H A Ddpaa2_cmdif.rst59 On EAL initialization, dpci devices will be probed and then vdev device
H A Ddpaa2_qdma.rst63 On EAL initialization, dpdmai devices will be probed and populated into the
H A Difpga.rst27 Each instance of IFPGA Rawdev Driver is probed by Intel FpgaDev. In coordination
H A Dcnxk_bphy.rst144 On EAL initialization BPHY and BPHY CGX/RPM devices will be probed and populated into
H A Dcnxk_gpio.rst194 On EAL initialization CNXK GPIO device will be probed and populated into
H A Dioat.rst132 and any which have ``dpdk_`` prefix in their name will be automatically probed by the
139 Once probed successfully, irrespective of kernel driver, the device will appear as a ``rawdev``,
/dpdk/doc/guides/compressdevs/
H A Docteontx.rst64 probed. To use the PMD in an application, user must:
/dpdk/doc/guides/platform/
H A Dmlx5.rst54 One mlx5 device can be probed by a number of different PMDs.
72 By default, the mlx5 device will be probed by the ``eth`` PMD.
78 - ``eth`` and ``vdpa`` PMDs cannot be probed at the same time.

12