+28
−3
Loading
We want to start allocating memory local to NUMA nodes where possible, without breaking setups that may not have hugepages allocated for each NUMA node. So when a node_id is actually specified (i.e. not SOCKET_ID_ANY), and the allocation fails, try it again but with SOCKET_ID_ANY. (Note: using SOCKET_ID_ANY in this file instead of SPDK_ENV_NUMA_ID_ANY, since the former is the DPDK definition.) Later we will add a patch that enforces the NUMA node when specified, to help users who definitely want NUMA optimizations so that these setups can be ensured to have memory allocated per node. Note that setup.sh has already been updated to allocate memory evenly across NUMA nodes by default (originally it would only allocate from node 0 by default). Signed-off-by:Jim Harris <jim.harris@samsung.com> Change-Id: I6b852532ac93230de6a91d3eb829448fbd903e8b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/24578 Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by:
Ben Walker <ben@nvidia.com> Community-CI: Mellanox Build Bot