Running iSCSI in loopback runs into some cases where a core is considerably impacted by the initiator TCP traffic, even though the scheduler is trying to schedule it on different cores. Gang is working through modifying the QoS tests to just use bdevperf instead of iSCSI, but until that is ready, let's allow more variance to reduce the fairly significant rate of test failures we're seeing due to this test. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I99fe13621f5ca2f8e6402fc17fb859df815fe05e Reviewed-on: https://review.gerrithub.io/c/444458 Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> |
||
---|---|---|
.. | ||
qos.sh |