numam-spdk/test/nvmf/host
Jim Harris d96abc9f0d test/nvmf: remove -p num_queues restrictions
There's a bug in Linux 5.1 (possibly 5.0 too) where
the kernel initiator driver crashes if it can't get
one queue per CPU.  This will get fixed eventually,
but for now we need to remove the cases where we
restrict the number of queues per controller so that
we can test on newer kernels.

Even on cases where we're testing the SPDK initiator,
there's no real need to restrict the number of queue
pairs.

The kernel will eventually get fixed, but we should
be testing with default behavior anyways (the kernel
wants lots of queues).  We'll also want to add some
regression tests to make sure the kernel doesn't
break again.  But that will all come later.

Signed-off-by: Jim Harris <james.r.harris@intel.com>
Change-Id: I9979e6d94456e075688b822b042936b63e518a4a

Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/454819
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
2019-05-22 14:50:05 +00:00
..
aer.sh test/nvmf: remove -p num_queues restrictions 2019-05-22 14:50:05 +00:00
bdevperf.sh test/nvmf: remove -p num_queues restrictions 2019-05-22 14:50:05 +00:00
fio.sh test/nvmf: remove -p num_queues restrictions 2019-05-22 14:50:05 +00:00
identify_kernel_nvmf.sh test/nvmf: simplify "iso" parameter 2019-05-17 12:48:19 +00:00
identify.sh test/nvmf: remove -p num_queues restrictions 2019-05-22 14:50:05 +00:00
perf.sh test/nvmf: remove -p num_queues restrictions 2019-05-22 14:50:05 +00:00