fio_plugin: stop specifying io_queue_size in the probe_cb()
This will cause the NVMe driver to use the default qpair size as opposed to setting it up for the first job in what may end being a series of jobs in the same fio config file. If we don't do this and subsequent jobs are specifying a higher queue depth than earlier jobs, the NVMe qpairs will be too small and performance results can be way off. Future fix logged on Trello to correctly size q pairs even when multiple jobs are specified in a single file but this is a small optimization. Change-Id: I73a7b83b10418dd22b663a50ea8e33a6c3d7ecf7 Signed-off-by: Paul Luse <paul.e.luse@intel.com> Reviewed-on: https://review.gerrithub.io/371240 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
This commit is contained in:
parent
48b2e94f66
commit
4ef6d0f934
@ -92,10 +92,6 @@ static bool
|
||||
probe_cb(void *cb_ctx, const struct spdk_nvme_transport_id *trid,
|
||||
struct spdk_nvme_ctrlr_opts *opts)
|
||||
{
|
||||
struct thread_data *td = (struct thread_data *)cb_ctx;
|
||||
|
||||
opts->io_queue_size = td->o.iodepth + 1;
|
||||
|
||||
return true;
|
||||
}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user