From owner-freebsd-stable@FreeBSD.ORG Wed Dec 7 05:16:58 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7715516A41F for ; Wed, 7 Dec 2005 05:16:58 +0000 (GMT) (envelope-from grog@lemis.com) Received: from ext-gw.lemis.com (ext-gw.lemis.com [150.101.14.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9056D43D5D for ; Wed, 7 Dec 2005 05:16:57 +0000 (GMT) (envelope-from grog@lemis.com) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.135]) by ext-gw.lemis.com (Postfix) with ESMTP id AE2851310CD; Wed, 7 Dec 2005 15:46:52 +1030 (CST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id DE4FC857B8; Wed, 7 Dec 2005 15:47:52 +1030 (CST) Date: Wed, 7 Dec 2005 15:47:52 +1030 From: Greg 'groggy' Lehey To: kama Message-ID: <20051207051752.GA60194@wantadilla.lemis.com> References: <20051202142731.H92866@ns1.as.pvp.se> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="G4iJoqBmSsgzjUCe" Content-Disposition: inline In-Reply-To: <20051202142731.H92866@ns1.as.pvp.se> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Cc: freebsd-stable@freebsd.org Subject: Re: cpu-timer rate X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 05:16:58 -0000 --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--