Messages in this thread | | | Date | Mon, 02 Feb 2015 11:31:40 +0000 | From | Juri Lelli <> | Subject | Re: Another SCHED_DEADLINE bug (with bisection and possible fix) |
| |
On 31/01/2015 09:56, Peter Zijlstra wrote: > On Fri, Jan 30, 2015 at 10:35:02AM +0000, Juri Lelli wrote: >> So, we do the safe thing only in case of throttling. > > No, even for the !throttle aka running tasks. We only use > dl_{runtime,deadline,period} for replenishment, until that time we > observe the old runtime/deadline set by the previous replenishment. >
Oh, right. We set dl_new in __dl_clear_params(), nice.
Thanks,
- Juri
>> I guess is more than >> ok for now, while we hopefully find some spare cycle to implement a >> complete solution :/. > > Yeah, I bet the fun part is computing the 0-lag across the entire root > domain, per-cpu 0-lag isn't correct afaict. >
| |