From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: Periodic clock tick considered harmful (was: Re: HZ, preferably as small as possible)
Date: Mon, 15 Jul 2002 05:21:19 +0000 (UTC) [thread overview]
Message-ID: <agtm4f$iic$1@penguin.transmeta.com> (raw)
In-Reply-To: 3D2DB5F3.3C0EF4A2@kegel.com
In article <3D2DB5F3.3C0EF4A2@kegel.com>, <dank@kegel.com> wrote:
>
>How about this: let's apply the high-resolution timer patch,
>which adds explicit timer events inbetween the normal 100 Hz
>events when needed to satisfy precise sleep requests.
The thing is, I think that's the wrong way around.
What we should have is a notion of a reasonably high frequency timer,
and then _slow_it_down_ to something else if not needed.
Speeding the timer up is bad, because:
- you do need to limit the speedup to _something_ anyway (and it might
as well be HZ)
- you get "partial jiffies", which means that only stuff that knows
about the finer granularity gets it.
In contrast, if you slow things down in integer increments of "n", the
only thing you need to do is to add in "n" instead of "1" in the timer
tick handler. Nobody else needs to really care - there is no such thing
as a "fractional jiffy".
Linus
next prev parent reply other threads:[~2002-07-15 5:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 16:44 Periodic clock tick considered harmful (was: Re: HZ, preferably as small as possible) dank
2002-07-11 16:59 ` Thunder from the hill
2002-07-11 19:45 ` Arnd Bergmann
2002-07-11 17:05 ` Hubertus Franke
2002-07-11 19:06 ` george anzinger
2002-07-11 19:19 ` mbs
2002-07-11 20:25 ` george anzinger
2002-07-11 21:29 ` Periodic clock tick considered harmful (was: Re: HZ, preferably as Alan Cox
2002-07-11 21:43 ` george anzinger
2002-07-11 22:32 ` Periodic clock tick considered harmful (was: Re: HZ, preferably as small as possible) Karim Yaghmour
2002-07-15 5:21 ` Linus Torvalds [this message]
2002-07-15 5:43 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2002-07-11 21:28 Per Jessen
2002-07-16 9:10 Martin Schwidefsky
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='agtm4f$iic$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--cc=linux-kernel@vger.kernel.org \
/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