From: Chris Snook <csnook@redhat.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Few interrupts with NO_HZ
Date: Mon, 06 Aug 2007 10:35:30 -0400 [thread overview]
Message-ID: <46B731B2.3040409@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708061626010.13469@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Aug 6 2007 09:47, Chris Snook wrote:
>>> this more of an informational question. So:
>>> kernel version is 2.6.22.1 on i686
>>> /proc/uptime 9917.81 9140.90 (2h45m)
>>> /proc/cpuinfo:
>>> CPU0
>>> 0: 282 IO-APIC-edge timer
>>>
>>> this is kinda neat, I expected much more interrupts than just 282
>>> since boot. What kernel code actually uses the irq0 timer?
>> If you don't have an HPET (and most single-processor systems do not)
>
> This is an AMD Athlon with 'Thoroughbred' core; it does not seem to
> have C-states at all (or: exactly one). It clearly is not idle all the
> time, sometimes I run povray. (And 282 has not changed since the
> morning.)
>
>
> Jan
In that case, it's probably the early bootstrap code that runs before the TSC is
calibrated. PIT sucks, but it sucks very reliably, so it's a good basis for
calibrating the other timekeeping devices. Once you have something better set
up, you don't need it anymore if you're not doing C-state transitions.
-- Chris
next prev parent reply other threads:[~2007-08-06 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 10:52 Few interrupts with NO_HZ Jan Engelhardt
2007-08-06 13:47 ` Chris Snook
2007-08-06 14:28 ` Jan Engelhardt
2007-08-06 14:35 ` Chris Snook [this message]
2007-08-06 22:31 ` Kyle McMartin
[not found] <fa.09fMUH3GW8WqIBDx7yLbNn+7hAo@ifi.uio.no>
2007-08-06 23:22 ` Robert Hancock
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=46B731B2.3040409@redhat.com \
--to=csnook@redhat.com \
--cc=jengelh@computergmbh.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 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.