lkml.org 
[lkml]   [2011]   [May]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: [tip:timers/core] timerfd: Allow timers to be cancelled when clock was set
    On Wed, May 11, 2011 at 16:48, Peter Zijlstra <peterz@infradead.org> wrote:
    > On Wed, 2011-05-11 at 16:32 +0200, Kay Sievers wrote:
    >> On Wed, May 11, 2011 at 16:30, Peter Zijlstra <peterz@infradead.org> wrote:
    >> > On Wed, 2011-05-11 at 16:22 +0200, Kay Sievers wrote:
    >> >> On Wed, May 11, 2011 at 16:01, Peter Zijlstra <peterz@infradead.org> wrote:
    >> >> > On Wed, 2011-05-11 at 15:52 +0200, Kay Sievers wrote:
    >> >> >>
    >> >> >> No, fixed time spans have never been a problem, and are not the
    >> >> >> example here. It's about the normal wall clock, that wakes up every
    >> >> >> minute and updates the numbers on the screen.
    >> >> >
    >> >> > 'wakes up every minute' sounds like a fixed time interval to me.
    >> >>
    >> >> Right, but if the wall clock changes, it must not wait for the full
    >> >> minute to update the numbers, they need to update immediately with the
    >> >> new wall clock time. Stuff woke up every second in the past to do
    >> >> that, but that's not what we want today.
    >> >
    >> > Again, nothing that couldn't be solved with a notifier of sorts.
    >>
    >> Right. What we have with that patch, and what's visible to the
    >> outside, is nothing but such a notifier. What kind of interface you
    >> have in mind instead?
    >
    > Dunno, an eventfd that triggers every time someone calls adjtime() and
    > related?

    I think, we are exactly not interested in adjtime() calls, but only in
    jumps in wall clock time.

    Kay


    \
     
     \ /
      Last update: 2011-05-11 18:15    [W:5.773 / U:0.020 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site