Re: [tip:timers/core] timerfd: Allow timers to be cancelled when clock was set
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:timers/core] timerfd: Allow timers to be cancelled when clock was set
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
- Date: Wed, 11 May 2011 16:01:58 +0200
- Cc: linux-kernel@xxxxxxxxxxxxxxx, mingo@xxxxxxxxxx, hpa@xxxxxxxxx, johnstul@xxxxxxxxxx, davidel@xxxxxxxxxxxxxxx, virtuoso@xxxxxxxxx, tglx@xxxxxxxxxxxxx, chris.friesen@xxxxxxxxxxx, kirill@xxxxxxxxxxxxx, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <BANLkTik5szBkinZEWySVjBKA5GF+6dn8Yg@xxxxxxxxxxxxxx>
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.
Anyway, I still don't agree with the current implementation, its adding
overhead to timer fast-paths for a definite slow-path.
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]