From: Rene Herman <rene.herman@keyaccess.nl>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
arjan@infradead.org
Subject: Re: [RFC] Imprecise timers.
Date: Tue, 22 Jul 2008 09:19:02 +0200 [thread overview]
Message-ID: <488589E6.5070300@keyaccess.nl> (raw)
In-Reply-To: <1216695757.18980.16.camel@shinybook.infradead.org>
On 22-07-08 05:02, David Woodhouse wrote:
> Many users of timers don't really care too much about exactly when
> their timer fires -- and waking a CPU to satisfy such a timer is a
> waste of power. This patch implements a 'range' timer which will fire
> at a 'convenient' moment within given constraints.
>
> It's implemented by a deferrable timer at the beginning of the range,
> which will run some time later when the CPU happens to be awake. And
> a non-deferrable timer at the hard deadline, to ensure it really does
> happen by then.
Are there actually users for this (not just in theory)? The deferrable
timer sort of sounds like all I'd ever want if I, as you say, wouldn't
really care...
Rene.
next prev parent reply other threads:[~2008-07-22 7:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 3:02 [RFC] Imprecise timers David Woodhouse
2008-07-22 3:05 ` [RFC] schedule_timeout_range() David Woodhouse
2008-07-22 3:56 ` Nick Piggin
2008-07-22 4:12 ` David Woodhouse
2008-07-22 4:26 ` Arjan van de Ven
2008-07-22 4:34 ` David Woodhouse
2008-07-22 4:33 ` Nick Piggin
2008-07-22 4:45 ` David Woodhouse
2008-07-22 4:50 ` Nick Piggin
2008-07-22 4:58 ` David Woodhouse
2008-07-22 5:35 ` Jan Engelhardt
2008-07-22 4:33 ` Arjan van de Ven
2008-07-22 7:19 ` Rene Herman [this message]
2008-07-22 12:54 ` [RFC] Imprecise timers Arjan van de Ven
2008-07-22 14:04 ` Rene Herman
2008-07-29 0:36 ` Pallipadi, Venkatesh
2008-08-09 12:54 ` Pavel Machek
2008-08-11 17:35 ` Venki Pallipadi
2008-08-12 12:00 ` Pavel Machek
2008-08-12 18:11 ` Venki Pallipadi
2008-08-12 21:55 ` Alan Cox
2008-08-12 21:58 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=488589E6.5070300@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=arjan@infradead.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox