when using --no-numa option, gro should be initiated with SOCKET_ID_ANY to allow using cross NUMA.
API changes notice: Changed socket_id field in struct rte_gro_param from uint16 to int32 to support negative value -1 (== SOCKET_ID_ANY). Changed gro_tbl_create typedef to receive negative socket input. Signed-off-by: Maayan Kashani <mkash...@nvidia.com> --- doc/guides/rel_notes/deprecation.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index 36489f6e68f..5d534f49d53 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -142,3 +142,11 @@ Deprecation Notices * bus/vmbus: Starting DPDK 25.11, all the vmbus API defined in ``drivers/bus/vmbus/rte_bus_vmbus.h`` will become internal to DPDK. Those API functions are used internally by DPDK core and netvsc PMD. + +* lib/gro: Starting DPDK 25.11, to enable using negative socket value + (``SOCKET_ID_ANY`` = -1) for gro init for cross NUMA initialization support, + perform the next changes in API: + + - In ``struct rte_gro_param``: ``socket_id`` type changed from ``uint16_t`` to ``int32_t``. + - Update all ``gro_xxx_create`` functions to use updated socket_id type. + -- 2.21.0
