lkml.org 
[lkml]   [2015]   [Feb]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: 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.
    >



    \
     
     \ /
      Last update: 2015-02-02 12:41    [W:2.282 / U:4.872 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site