All other tests wait for scheduling to occur before verifying the results. Even for 100% busy threads, they are first round robined between cores. In some edge cases, if threads are created right at the end of the scheduling period - they will be 100% busy. Yet due to low busy_tsc it will be deemed that two of such threads can be placed on single core. To prevent that a few full scheduling periods have to be observed. Thus added sleep for 10 scheduling periods before verifying the results, similar to other test cases in this file. While here increased the sleep time between samples to match the scheduling period. With 1 sec default scheduling period, no change would occur between two 0.5 sec samples. Fixes #2140 Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: I5abf3bc04c6f65f4faae2bcd3e6828be72f97311 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9387 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Dong Yi <dongx.yi@intel.com> Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com> |
||
---|---|---|
.. | ||
cgroups.sh | ||
common.sh | ||
governor.sh | ||
idle.sh | ||
interrupt.sh | ||
isolate_cores.sh | ||
load_balancing.sh | ||
rdmsr.pl | ||
scheduler.sh |