linux-kernel - Re: [tip:timers/core] timerfd: Allow timers to be cancelled when clock was set

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1305122518.2914.224.camel@laptop>
Date:	Wed, 11 May 2011 16:01:58 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	linux-kernel@...r.kernel.org, mingo@...hat.com, hpa@...or.com,
	johnstul@...ibm.com, davidel@...ilserver.org, virtuoso@...nd.org,
	tglx@...utronix.de, chris.friesen@...band.com,
	kirill@...temov.name, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:timers/core] timerfd: Allow timers to be cancelled when
 clock was set

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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/