linux-kernel - Re: [PATCH] timers: Introduce the concept of timer slack for legacy 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20100113214528.41e2de4a@infradead.org>
Date:	Wed, 13 Jan 2010 21:45:28 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, tglx@...x.de, mingo@...e.hu,
	Cyrill Gorcunov <gorcunov@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] timers: Introduce the concept of timer slack for legacy
 timers

On Wed, 13 Jan 2010 13:52:19 -0800
Andrew Morton <akpm@...ux-foundation.org> wrote:

> I suppose this could be inlined.

.. and then I expand it a bit in a few weeks and guess who complains an
inline gets too big ? ;-)


> OK, so by default this causes every timer in the system to have a bit
> of slack (unless they're really short-term?), 

0.4%.. so yeah you need to sleep a little before it rounds up to 1 ;)


>so the feature does get
> runtime tested.

yep..

> 
> But the set_timer_slack() interface has no callers.  Perhaps it
> should?

I have some callers pending, and I thought I posted those to lkml but
maybe I did not.


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
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/