| 44970291 | 05-Sep-2024 |
Jim Harris <jim.harris@samsung.com> |
fio/nvme, fio/bdev: use specific NUMA ID when possible
Currently if any namespace or bdev reports NUMA_ID_ANY, we allocate the buffer using NUMA_ID_ANY. This basically keeps original behavior, unles
fio/nvme, fio/bdev: use specific NUMA ID when possible
Currently if any namespace or bdev reports NUMA_ID_ANY, we allocate the buffer using NUMA_ID_ANY. This basically keeps original behavior, unless all namespaces and bdevs reports a NUMA ID.
But it is OK to just use a specific NUMA ID as long as none of the other namespaces or bdevs in that job have a conflicting NUMA ID. If the other namespaces or bdevs report NUMA_ID_ANY we can just ignore them.
Suggested-by: Konrad Sztyber <konrad.sztyber@intel.com> Signed-off-by: Jim Harris <jim.harris@samsung.com> Change-Id: I18743a5e26d1098804b7783c592b89bfe9286423 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/24815 Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <ben@nvidia.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>
show more ...
|