Currently, NVMe perf worker starts IO and measurements as soon as all its QPs were connected. But other workers may still be connecting and not started their measurements yet. With large number of QPs when connections take a long time this can cause inaccurate performance reporting. This patch adds synchronization point for workers after all QPs were connected and before start of IO and measurements. Signed-off-by: Evgeniy Kochetov <evgeniik@nvidia.com> Change-Id: If0c9be8dd41c8e851aae6b3e71afa3efe5314330 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5126 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> |
||
---|---|---|
.. | ||
.gitignore | ||
Makefile | ||
perf.c | ||
README.md |
Compiling perf on FreeBSD
To use perf test on FreeBSD over NVMe-oF, explicitly link userspace library of HBA. For example, on a setup with Mellanox HBA,
LIBS += -lmlx5