Date: Wed, 7 Dec 2005 15:47:52 +1030 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: kama <kama@pvp.se> Cc: freebsd-stable@freebsd.org Subject: Re: cpu-timer rate Message-ID: <20051207051752.GA60194@wantadilla.lemis.com> In-Reply-To: <20051202142731.H92866@ns1.as.pvp.se> References: <20051202142731.H92866@ns1.as.pvp.se>
next in thread | previous in thread | raw e-mail | index | archive | help
--G4iJoqBmSsgzjUCe
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Friday, 2 December 2005 at 14:32:58 +0100, kama wrote:
>
> Hi,
>
> I am just wondering why the cpu-timer is doubled from what I set in
> kern.hz?
>
> # vmstat -i
> ...
> cpu0: timer 14314031 1999
>
> # sysctl -a | grep hz
> kern.clockrate: { hz = 1000, tick = 1000, profhz = 666, stathz = 133 }
Interesting question. So far I haven't seen an answer that comes
close to explaining it. My guess is that it's because of the specific
timer you're using; which is it? Is there anything else of interest
in your setup?
FWIW, I get (without ACPI) on two different machines essentially the
same:
$ vmstat -i
interrupt total rate
irq0: clk 55250411 1000
irq1: atkbd0 47365 0
irq5: ohci1 97516 1
irq8: rtc 7069645 127
irq10: ehci0 1 0
irq11: nve0 xl0+ 1022991 18
irq14: ata0 425652 7
irq15: ata1 4777 0
Total 63918358 1157
$ sysctl -a | grep hz
kern.clockrate: { hz = 1000, tick = 1000, profhz = 1024, stathz = 128 }
debug.psm.hz: 20
Greg
--
See complete headers for address and phone numbers.
--G4iJoqBmSsgzjUCe
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)
iD8DBQFDlnCAIubykFB6QiMRAhKRAJ9RnZj48W/yE88bNbldMmvj8frvagCfSFQS
DmgU8R7kG8nre/582P286x0=
=5Cyd
-----END PGP SIGNATURE-----
--G4iJoqBmSsgzjUCe--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051207051752.GA60194>