Messages in this thread | | | From | Nick Piggin <> | Subject | Re: [RFC] schedule_timeout_range() | Date | Tue, 22 Jul 2008 13:56:29 +1000 |
| |
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.
| |