[lkml]   [2010]   [Jan]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC 8/12][PATCH] SCHED_DEADLINE: wait next instance syscall added.
    On Mon, 2009-12-28 at 15:30 +0100, Peter Zijlstra wrote:
    > > However, for SCHED_DEADLINE tasks, it should be the call with which each
    > > job closes its current instance. In fact, in this case, the task is put to
    > > sleep and, when it wakes up, the scheduler is informed that a new job
    > > arrived, saving the overhead that usually comes with a task activation
    > > to enforce maximum task bandwidth.
    > The changelog suggests (and a very brief looks seems to confirm) that
    > this code could be much smaller by using hrtimer_nanosleep().
    > The implementation as presented seems to only call ->wait_interval()
    > when the timer arms, which seems like a bug, we should always call it,
    > regardless of whether we're on a period boundary.
    Ok, thanks, I'll look carefully at that! The current code is an attempt
    of mine to replicate the behaviour of clock_nanosleep, but you're
    definitely right here, it can be done much better.

    Thanks and regards,

    <<This happens because I choose it to happen!>> (Raistlin Majere)
    Dario Faggioli, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa (Italy) / /
    [unhandled content-type:application/pgp-signature]
     \ /
      Last update: 2010-01-13 10:35    [W:0.028 / U:2.284 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site