From: Ben Greear <greearb@candelatech.com>
To: unlisted-recipients:; (no To-header on input)
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 18:33:29 -0700 [thread overview]
Message-ID: <3DA4D8E9.9050605@candelatech.com> (raw)
In-Reply-To: 3DA4CED6.1BD30A2F@kegel.com
> george anzinger wrote:
>
>>Linus Torvalds wrote:
>>
>>>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.
>>
>>...
>>
>>Making ticks shorter causes extra overhead ALL the time,
>>even when it is not needed. Higher resolution is not free
>>in any case, but it is much closer to free with this patch
>>than by increasing HZ (which, of course, can still be
>>done). Overhead wise and resolution wise, for timers, we
>>would be better off with a 1/HZ tick and the "on demand"
>>high-res interrupts this patch introduces.
I would like to add my small vote for including the timers too.
I have not looked at the code, but the idea seems sound (let
those who need the timers pay the price at that time, don't make
the rest of the machine suffer otherwise)....
Enjoy,
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2002-10-10 1:27 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 [this message]
2002-10-10 3:55 ` Jeff Dike
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=3DA4D8E9.9050605@candelatech.com \
--to=greearb@candelatech.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