linux-kernel - Re: [PATCH 11/13] hrtimer: turn hrtimers into range timers

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20080902090211.31ebced7@infradead.org>
Date:	Tue, 2 Sep 2008 09:02:11 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	dwmw2@...radead.org, drepper@...hat.com, mingo@...e.hu,
	tglx@...x.de
Subject: Re: [PATCH 11/13] hrtimer: turn hrtimers into range timers

On Tue, 02 Sep 2008 15:47:07 +0200
Peter Zijlstra <peterz@...radead.org> wrote:

> > (it's not perfect by any means but it works ;-)
> 
> Gah, right. How about adding the following:
> 
> /*
>  * The immediate goal is minimizing wakeups, not running
>  * timers at the earliest interrupt after their soft expiration.
>  * This allows us to avoid using a Priority Search Tree,
>  * which can answer a stabbing querry for overlapping
>  * intervals and instead use the simple BST we already have.
>  * We don't add extra wakeups by delaying timers that are
>  * right-of a not yet expired timer, because that timer will
>  * have to trigger a wakeup anyway.
>  */

fair enough; I'll merge this in (I'm not going to resend the whole
series just for this redo though... maybe when there's more feedback
I'll roll it all up)
thanks!

-- 
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/