From: Nick Piggin <nickpiggin@yahoo.com.au>
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] schedule_timeout_range()
Date: Tue, 22 Jul 2008 13:56:29 +1000 [thread overview]
Message-ID: <200807221356.29892.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <1216695942.18980.19.camel@shinybook.infradead.org>
On Tuesday 22 July 2008 13:05, David Woodhouse wrote:
> Along the same lines as the previous patch, this provides
> schedule_timeout_range() for when the precise moment of wakeup doesn't
> matter (and isn't worth wasting power on), but any time the CPU happens
> to be awake within a given range of time is fine.
>
> Implement schedule_timeout() using it, and likewise for the _killable,
> _interruptible and _uninterruptible variants.
Rather than specific "deadline" values (which we can't guarantee anyway),
or vague "can defer" values, I would prefer just a small selection of
maybe orders of magnitude flags, maybe SECONDS, MILLISECONDS, MICROSECONDS
which gives an amount of delay the kernel might add to the timer.
If you prefer the deadline parameter, don't call it a hard deadline
which is misleading.
Otherwise, seems like a pretty good idea.
next prev parent reply other threads:[~2008-07-22 3:56 UTC|newest]
Thread overview: 24+ 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 [this message]
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 ` [RFC] Imprecise timers Rene Herman
2008-07-22 12:54 ` 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
[not found] <aSgqr-EJ-15@gated-at.bofh.it>
[not found] ` <aShcU-3uj-11@gated-at.bofh.it>
[not found] ` <aShw5-4ai-9@gated-at.bofh.it>
[not found] ` <aShPs-4IY-1@gated-at.bofh.it>
2008-07-23 11:52 ` [RFC] schedule_timeout_range() Bodo Eggert
2008-07-24 0:53 ` Nick Piggin
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=200807221356.29892.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--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
all inboxes | Powered by JetHome®