[RFC PATCH v4 1/3] pci: add non-merged Linux uAPI changes

This commit is a hack to prevent build failures the next commit in this patch series causes due to missing vfio uapi definitions. This commit should NEVER BE MERGED. Next commit in this patch series depends on additions to vfio uapi that enable TPH icotl in the vfio-pci driver in the Linux kernel.

[RFC PATCH v4 2/3] bus/pci: introduce the PCIe TLP Processing Hints API

Extend the PCI bus driver to enable or disable TPH capability and set or get PCI Steering-Tags (STs) on an endpoint device. The functions rte_pci_tph_{enable, disable,st_set,st_get} provide the primary interface for DPDK device drivers. Implementation of the interface is OS dependent. For Linux, th

[RFC PATCH v4 3/3] ethdev: introduce the cache stashing hints API

Extend the ethdev library to enable the stashing of different data objects, such as the ones listed below, into CPU caches directly from the NIC. - Rx/Tx queue descriptors - Rx packets - Packet headers - packet payloads - Data of a packet at an offset from the start of the packet The APIs are des

[RFC PATCH v4 0/3] An API for Stashing Packets into CPU caches

ethdev: an API for cache stashing hints Today, DPDK applications benefit from Direct Cache Access (DCA) features like Intel DDIO and Arm's write-allocate-to-SLC. However, those features do not allow fine-grained control of direct cache access, such as stashing packets into upper-level caches (L2 c

RE: [PATCH v5 1/2] lib/fib: remove warning about implicit 64-bit conversion

From: Stephen Hemminger [mailto:step...@networkplumber.org] Sent: Saturday, 17 May 2025 13.10 Ok. Wonder if RTE_PTR_ADD should have the cast there instead  Morten: Considered the same; but prefer not. It will suppress warnings like this, which may be real. On Sat, May 17, 2025, 05:45 Andre Mu

Re: [PATCH v5 1/2] lib/fib: remove warning about implicit 64-bit conversion

Ok. Wonder if RTE_PTR_ADD should have the cast there instead On Sat, May 17, 2025, 05:45 Andre Muezerie wrote: > MSVC issues the warning below: > > ../lib/fib/trie.c(341): warning C4334: '<<': > result of 32-bit shift implicitly converted to 64 bits > (was 64-bit shift intended?) > > The fix is

RE: [PATCH v5 1/2] lib/fib: remove warning about implicit 64-bit conversion

> From: Andre Muezerie [mailto:andre...@linux.microsoft.com] > Sent: Friday, 16 May 2025 22.46 > > MSVC issues the warning below: > > ../lib/fib/trie.c(341): warning C4334: '<<': > result of 32-bit shift implicitly converted to 64 bits > (was 64-bit shift intended?) > > The fix is to cast (1) ex

[PATCH] Skip vfio in the scenario of non-privileged mode

DPDK detect vfio container according the existence of vfio module. But for container with non-privileged mode, there is possibility that no VFIO_DIR(/dev/vfio) mapping from host to container when host have both Intel NIC and Mellanox NIC but this conntainer only allocate VFs from Mellanox NIC. In t

[PATCH v4] eal/linux: skip vfio for non-privileged container

DPDK detect vfio container according the existence of vfio module. But for container with non-privileged mode, there is possibility that no VFIO_DIR(/dev/vfio) mapping from host to container when host have both Intel NIC and Mellanox NIC but this conntainer only allocate VFs from Mellanox NIC. In t

[PATCH v3] Skip vfio in the scenario of non-privileged mode

DPDK detect vfio container according the existence of vfio module. But for container with non-privileged mode, there is possibility that no VFIO_DIR(/dev/vfio) mapping from host to container when host have both Intel NIC and Mellanox NIC but this conntainer only allocate VFs from Mellanox NIC. In t

Re: [PATCH v2] eal/linux: skip vfio for non-privileged container

On 5/16/2025 9:30 PM, Burakov, Anatoly wrote: On 3/27/2025 8:57 AM, Yang Ming wrote: DPDK detect vfio container according the existence of vfio module. But for container with non-privileged mode, there is possibility that no VFIO_DIR(/dev/vfio) mapping from host to container when host have both