From: Ingo.Adlung@t-online.de (Ingo Adlung)
To: linux-kernel@vger.kernel.org
Cc: "Linus Torvalds" <"Linus Torvalds"@t-online.de>
Subject: Re: [PATCH 2/3] High-res-timers part 2 (x86 platform code) take 5.1
Date: Sun, 13 Oct 2002 12:46:31 +0200 [thread overview]
Message-ID: <3DA94F07.7070109@t-online.de> (raw)
In-Reply-To: Pine.LNX.4.44.0210091613590.9234-100000@home.transmeta.com
Linus Torvalds wrote:
> On Wed, 9 Oct 2002, george anzinger wrote:
>
>>This patch, in conjunction with the "core" high-res-timers
>>patch implements high resolution timers on the i386
>>platforms.
>
>
> I really don't get the notion of partial ticks, and quite frankly, this
> isn't going into my tree until some major distribution kicks me in the
> head and explains to me why the hell we have partial ticks instead of just
> making the ticks shorter.
>
> Linus
In any kind of virtual environment you would rather prefer a completely
tickless system alltogether than increased tick rates. In a S/390
virtual machine, running many hundreds of virtual Linux servers the
100Hz timer pops are already considerably painful, and going to a higher
tick rate achieving higher timer resolution is completely prohibitive.
Similar is true in many embedded systems related to power consumption of
high frequency ticks.
However, George has shown that introducing the notion of a completely
tickless system is expensive on Intel overhead wise, thus partial ticks
seem to be a possibility addressing the needs for embedded and virtual
environments, getting decent timer resolution as needed.
Ingo Adlung
next prev parent reply other threads:[~2002-10-13 10:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 22:47 [PATCH 2/3] High-res-timers part 2 (x86 platform code) take 5.1 george anzinger
2002-10-09 23:14 ` Linus Torvalds
2002-10-09 23:42 ` george anzinger
2002-10-10 15:03 ` Eric W. Biederman
2002-10-10 15:45 ` george anzinger
2002-10-10 15:54 ` Oliver Xymoron
2002-10-10 16:24 ` george anzinger
2002-10-10 17:04 ` Oliver Xymoron
2002-10-10 17:47 ` george anzinger
2002-10-13 10:46 ` Ingo Adlung [this message]
2002-10-14 7:18 ` Vojtech Pavlik
2002-10-14 22:17 ` Pavel Machek
2002-10-15 7:13 ` Vojtech Pavlik
2002-10-15 21:45 ` george anzinger
2002-10-17 21:54 ` Randy.Dunlap
2002-10-17 22:11 ` Robert Love
2002-10-18 13:11 ` mbs
2002-10-10 0:50 Dan Kegel
2002-10-10 1:33 ` Ben Greear
2002-10-10 3:55 ` Jeff Dike
2002-10-10 3:32 ` Dan Kegel
2002-10-10 12:34 ` mbs
2002-10-12 22:03 Jim Houston
2002-10-14 6:50 ` Ulrich Windl
2002-10-15 22:03 ` george anzinger
2002-10-19 1:02 Brad Bozarth
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=3DA94F07.7070109@t-online.de \
--to=ingo.adlung@t-online.de \
--cc="Linus Torvalds"@t-online.de \
--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;
as well as URLs for NNTP newsgroup(s).