+58
−71
Loading
For some reason the routine for generating fio job/filename sections was different for kernel and spdk fio modes. This made fio results hard to compare because even configuration files themselves were not comparable. The function was modified to create the same fio configuration files for kernel and spdk. While at it, iodepth calculation has been slightly modified as well. It is now being calculated for each [ ] job section, so that each "filename" gets the actual iodepth value specified in test run parameters. While generating the config file the script will add NUMA node information as a comment for "cpus_allowed" and "filename" sections, so that it's clearly visible how resources are aligned. In case of cross numa configuration additional warnings will be printed to screen as well. For example, a configuration file for running test with 7 NVMe drives, 3 CPUs and effective (per filename) queue depth of 32 would look like this: run_perf.sh --cpu-allowed=0,1,2 --iodepth=32 --driver=kernel-classic-polling [...other params...] -------- [filename0] iodepth=96 cpus_allowed=0 #CPU NUMA Node X filename=/dev/nvme0n1 #NVMe NUMA Node X filename=/dev/nvme1n1 #NVMe NUMA Node X filename=/dev/nvme2n1 #NVMe NUMA Node X [filename1] iodepth=64 cpus_allowed=1 #CPU NUMA Node X filename=/dev/nvme3n1 #NVMe NUMA Node X filename=/dev/nvme4n1 #NVMe NUMA Node X [filename2] iodepth=64 cpus_allowed=2 #CPU NUMA Node X filename=/dev/nvme5n1 #NVMe NUMA Node X filename=/dev/nvme6n1 #NVMe NUMA Node X -------- Change-Id: Ida2f781fbb93c4a8c62154e711151152843ab997 Signed-off-by:Karol Latecki <karol.latecki@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/3370 Community-CI: Mellanox Build Bot Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by:
Michal Berger <michalx.berger@intel.com> Reviewed-by:
Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>