[lkml]   [2008]   [Jul]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC] schedule_timeout_range()
On Wednesday 23 July 2008 21:52, Bodo Eggert wrote:
> Nick Piggin <> wrote:
> > The only thing I dislike about explicit times is that when a driver or
> > someone doesn't _really_ know how much to specify. Do you say 10s, 100s?
> > It shouldn't be arbitrary, but we should have a few constants I think.
> You'd replace "Should I use 10 or 100 seconds?" with "Should I use
> TIMEOUT_10_SEC or TIMEOUT_100_SEC?", while replacing "I want 40 seconds!"
> with "Danmed, I want 40 seconds, but that's not an option!".
> BTW: If you don't know about which timeout you should use, you should think
> about mowing the lawn instead. ¢¢

It's not always that simple. If you code drivers or network protocols,
it might seem easy, but a lot of the VM for example is riddled with
rather arbitrary heuristics. Suppose we do slab cache reaping at 1HZ
(for no really good reason)... what I want to do with that guy is to
get maximum power savings when the CPU is idle, however I don't want to
wait infinitely long because that's leaving work to do when the CPU
finally does wake up, and it also ties up memory. I want the minimum
timeout that gives maximum power saving (say, within 99.9% of theoretical

Can you tell me how to achieve this, or do you have lawn to mow too? ;)

OK, today we probably just add a few seconds of slop and forget about it,
but actually in future if we might want to power down most of the system
between key strokes, we might want 10s of seconds of sleep time.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2008-07-24 02:57    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean