| /dpdk/usertools/ |
| H A D | dpdk-pmdinfo.py | 121 def __init__(self, vendor, device, name): argument
125 self.vendorID = vendor
160 def report(self, vendor=None): argument
166 if vendor is not None:
167 self.vendors[vendor].report()
279 vendor = pcidb.find_vendor(i[0])
280 device = vendor.find_device(i[1])
283 (vendor.name, vendor.ID, device.name,
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_22_07.rst | 46 * Device abstraction libs and PMDs (ordered alphabetically by vendor name)
178 * <vendor> platform with <vendor> <type of devices> combinations
|
| H A D | known_issues.rst | 126 Other vendor platforms with Intel® Xeon® processor 5500 series processors should
|
| /dpdk/doc/guides/tools/ |
| H A D | pmdinfo.rst | 23 -d FILE, --pcidb=FILE Specify a pci database to get vendor names from
|
| /dpdk/doc/guides/vdpadevs/ |
| H A D | ifc.rst | 17 IFCVF's vendor ID and device ID are same as that of virtio net pci device,
18 with its specific subsystem vendor ID and device ID. To let the device be
|
| /dpdk/drivers/crypto/ccp/ |
| H A D | ccp_dev.c | 626 uint16_t vendor, device_id; in is_ccp_device() local
634 vendor = (uint16_t)tmp; in is_ccp_device()
643 if (vendor == id->vendor_id && in is_ccp_device()
|
| /dpdk/drivers/common/mlx5/ |
| H A D | mlx5_common.c | 1216 unsigned int i, model, family, brand_id, vendor; in RTE_INIT_PRIO() local
1226 vendor = ebx; in RTE_INIT_PRIO()
1238 if (vendor == signature_intel_ebx) { in RTE_INIT_PRIO()
|
| /dpdk/doc/guides/nics/ |
| H A D | enetc.rst | 63 - Driver registers the device vendor table in PCI subsystem.
|
| H A D | ena.rst | 49 vendor-specific extensions. Most of the management operations are
|
| H A D | ark.rst | 50 RTL Core, regardless of configuration, FPGA vendor, or target
|
| H A D | bnxt.rst | 594 Unlike basic stats, the extended stats are vendor-specific, i.e. each vendor
|
| H A D | i40e.rst | 73 support is dependent on your system board. Please see your vendor for details.
|
| /dpdk/doc/guides/contributing/ |
| H A D | stable.rst | 119 * Does it impact common components or vendor specific?
|
| /dpdk/doc/guides/linux_gsg/ |
| H A D | sys_reqs.rst | 125 the vendor supplied kernel configurations can be used to run most DPDK applications.
|
| /dpdk/drivers/net/axgbe/ |
| H A D | axgbe_phy_impl.c | 148 u8 vendor[32]; member
156 char vendor[AXGBE_SFP_BASE_VENDOR_NAME_LEN + 1]; member
|
| /dpdk/doc/guides/howto/ |
| H A D | debug_troubleshoot.rst | 438 #. If there are vendor or application specific metadata, check for errors due
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | graph_lib.rst | 41 - The modular scheme allows us to abstract the vendor HW specific
|
| H A D | poll_mode_drv.rst | 184 This includes the PCI vendor identifier, the PCI device identifier, the mapping address of the PCI …
|
| H A D | rte_flow.rst | 4109 rte_flow API provides the building blocks for vendor-agnostic flow
4117 design is often vendor-specific.
4140 hardware vendor. For example, some hardware may have a limited number
|