linux-kernel - Re: [PATCH 0/13] Turn hrtimers into a range capable timer

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]

Date:	Fri, 12 Sep 2008 13:39:49 +1000
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Arjan van de Ven <arjan@...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 0/13] Turn hrtimers into a range capable timer

On Tuesday 02 September 2008 09:03:43 Arjan van de Ven wrote:
> This series is a follow-on the the nanosecond select/poll series.
>
> The goal of this series is to introduce the capability into hrtimers to
> deal with a "range" rather than a specific point in time.
> (Several people discussed this recently, but we've been toying with the
> concept for a while)

Hi Arjen, sorry for not replying sooner.

I had half a patch to create a new "timer layer to rule them all" called 
ktimers, which took an explicit "slop" value.  Slop is the "how long before 
its worth waking the machine for this?" value, with friendly SLOP_USECS, 
SLOP_SECONDS, SLOP_DAYS etc defines.  Implemented in terms of normal and hr 
timers, which get deprecated over time.

Heuristics work for a while, but IMHO eventually this is going to have to be 
plumbed through to userspace.

Cheers,
Rusty.
--
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/