edb6e5b45a
For the commands sent from upper layer, the NVMe driver may split one command into several children requests based on stripe and data length, so number of requests in each queue pair has a value which is start from 512. we must ensure that the number of request in each queue pair is big enough to process all the commands, e.g: a user's input for a 512KiB read can be divided into 5 children NVMe commands when maximum transfer length is 128KiB, in addition, one parent request is occupied to track children commands. Fix issues #566 and #573. Change-Id: I162da8e1e15692625ce311e68a72c89b6492dd56 Signed-off-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-on: https://review.gerrithub.io/c/440457 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@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