+4
−1
+12
−5
+8
−0
Loading
We have started to add some NUMA based memory allocations (specifically NVMe SSD CQ memory). We will likely have more in the future. Some configurations may not have memory allocated across all NUMA nodes, for example, setup.sh used to require special flags to make sure memory was alllocated across NUMA nodes. setup.sh has since been changed to allocate across NUMA nodes by default, but other users may have their own scripts that have not yet been adjusted. So as a transition point, env layer currently tries to allocate from DPDK based on user-specified numa_id, and if that fails, will revert to SOCKET_ID_ANY instead. But specifying this new enforce_numa flag will not do the fallback and will just return NULL to the user. Signed-off-by:Jim Harris <jim.harris@samsung.com> Change-Id: Ieb346ac194fdd46c97e6fa77c117f637feb23b02 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/23966 Reviewed-by:
Ben Walker <ben@nvidia.com> Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by:
Konrad Sztyber <konrad.sztyber@intel.com>