86d77e2eb6
There could be cases (especially in virtualized and/or test environments) where we could accumulate significant skew in the timeslice frequency. Rather than depend on the application framework to try to guarantee the rate of timeslice poller callbacks, keep track internally of the last time the poller was invoked. If/when we accumulate and detect skew equivalent to one or more timeslices, increase the allowed IO and bandwidth of the next timeslice to accomodate. Since bdev poller now calls spdk_get_ticks() to do accounting, this patch also fixes up the increment_time() unit test function and the test env layer to properly increment the fake TSC. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Iba301ddc0fb3d02042106a8bf6e4a6a9a84dc263 Reviewed-on: https://review.gerrithub.io/423580 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: GangCao <gang.cao@intel.com> |
||
---|---|---|
.. | ||
test_env.c | ||
ut_multithread.c |