Re: [PATCH v3 1/2] sched/fair: Introduce short duration task check

[Yicong Yang]

On 2022/12/7 22:24, Chen Yu wrote:
> Hi Josh,
> On 2022-12-06 at 18:23:47 -0800, Josh Don wrote:
>>> We don't want to add more dedicated knobs. So using
>>> sysctl_sched_min_granularity as you are doing in this patch looks ok
>>
>> If not a knob, then maybe at least a smaller hardcoded value? Several
>> milliseconds seems like too long for this optimization; the
>> opportunity cost of not doing the idle search likely doesn't make
>> sense if the waker is going to be active for several additional
>> milliseconds. I would have guessed something on the order of 100us.
>>
>> Chen, what is the run duration of tasks in your ping pong example?
> OK, I'll measure the duration of all the tests and summarize the data later.
> 

If we decide to use sysctl_sched_min_granularity as the threshold of a short
task, can we also export p->se.dur_avg (somewhere like /proc/[pid]/sched)?
It may be helpful to choose a proper value for sysctl_sched_min_granularity.

Thanks.