d9a83bd7be
The original time slice (200ms) is too large for the priority test to generate a satisfactory result in 20s. If we only schedule 5 times a second, there are only 100 pick_next calls to the scheduler. I believe making scheduling more frequently does little harm to the system. Actually more scheduling opportunities may also reveal bugs which are not triggered previously. Adopting smaller time slices also allows us to reduce the time spent on the priority test, which can benefit the autotesting system. Signed-off-by: Junjie Mao <junjie.mao@hotmail.com> |
||
---|---|---|
.. | ||
lab1 | ||
lab2 | ||
lab3 | ||
lab4 | ||
lab5 | ||
lab6 | ||
lab7 | ||
lab8 | ||
tools | ||
autobuild.sh | ||
autotest.sh | ||
clangbuildall.sh | ||
cleanall.sh | ||
formatter.py | ||
gccbuildall.sh |