+2
−6
+6
−0
Loading
To that end, remove it altogether and allow setup.sh to always split requested amount of hugepages across all available nodes. Custom setups per node are still available through the HUGENODE var. Adjust some of the hugepages.sh tests to adhere to the new default. This change allows us to remove the per_node_1G_alloc() test since its flow is now covered by the custom_alloc(). By default, autotest.sh sets HUGEMEM=4096 and by spreading it across all the nodes, for the minimal scenario, we get only 2GB on a single node. For vhost tests, the default alloc per VM via vm_setup() is set to 1GB so sharing that 2GB between qemu and SPDK spreads it a bit too thin. Case in point, for vhost.vhost_blk_packed_ring_integrity test roughly > 600 hugepages is used for vhost. Since it slurps everything from node0, only < 512 remains. Since VMs are assigned per node, the most basic setups keep VM_*_qemu_numa_node set to 0. This is then used by qemu to bind to a specific node. With 1G, < 512 hugepages is simply not enough. With that in mind, for vhost tests, keep all allocations on a single node instead of trying to figure out right amount of memory per node to keep the old behavior in (this may change in the future when SPDK/vhost becomes numa-aware). Change-Id: I83e18bfa4cc6de0a777804b354de083ae6ae9d8c Signed-off-by:Michal Berger <michal.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/24176 Community-CI: Mellanox Build Bot Reviewed-by:
Tomasz Zawadzki <tomasz@tzawadzki.com> Reviewed-by:
Jim Harris <jim.harris@samsung.com> Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com>