From: Jeff Dike <jdike@karaya.com>
To: Dan Kegel <dank@kegel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] High-res-timers part 2 (x86 platform code) take 5.1
Date: Wed, 09 Oct 2002 22:55:52 -0500 [thread overview]
Message-ID: <200210100355.WAA06063@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Wed, 09 Oct 2002 17:50:30 MST." <3DA4CED6.1BD30A2F@kegel.com>
dank@kegel.com said:
> George's approach would work a lot better when doing lots of UML VM's
> on a single box, too, wouldn't it?
My thinking on this is that I'll have UML do the on-demand ticks. So, on
a host with n UMLs, we will no longer have n * HZ timer deliveries/sec.
I haven't thought a lot about it, but this seems largely unconnected to how
the host does its timers.
The one connection I can think of is that any generic support for on-demand
ticks would be re-used by UML. And if UML required generic changes for this,
then that would obviously affect the other ports somehow.
Jeff
next prev parent reply other threads:[~2002-10-10 2:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 0:50 [PATCH 2/3] High-res-timers part 2 (x86 platform code) take 5.1 Dan Kegel
2002-10-10 1:33 ` Ben Greear
2002-10-10 3:55 ` Jeff Dike [this message]
2002-10-10 3:32 ` Dan Kegel
2002-10-10 12:34 ` mbs
-- strict thread matches above, loose matches on Subject: below --
2002-10-19 1:02 Brad Bozarth
2002-10-12 22:03 Jim Houston
2002-10-14 6:50 ` Ulrich Windl
2002-10-15 22:03 ` george anzinger
2002-10-09 22:47 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
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
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=200210100355.WAA06063@ccure.karaya.com \
--to=jdike@karaya.com \
--cc=dank@kegel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.