From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 12 09:44:05 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9DCAB106566C for ; Sat, 12 Dec 2009 09:44:05 +0000 (UTC) (envelope-from gatinhodosseussonhos@hotmail.com) Received: from snt0-omc3-s35.snt0.hotmail.com (snt0-omc3-s35.snt0.hotmail.com [65.55.90.174]) by mx1.freebsd.org (Postfix) with ESMTP id 6F6818FC15 for ; Sat, 12 Dec 2009 09:44:05 +0000 (UTC) Received: from SNT102-W31 ([65.55.90.136]) by snt0-omc3-s35.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 12 Dec 2009 01:44:04 -0800 Message-ID: X-Originating-IP: [187.52.21.29] From: Phillip Spring To: , Date: Sat, 12 Dec 2009 10:44:04 +0100 Importance: Normal In-Reply-To: References: MIME-Version: 1.0 X-OriginalArrivalTime: 12 Dec 2009 09:44:04.0887 (UTC) FILETIME=[A48C6270:01CA7B0F] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: RE: Request for information - timers, hz, interrupts X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Dec 2009 09:44:05 -0000 fact: =20 I had to clean up a motherboard to boot Suse 10.2 kernel. I think that dust and dead insects are for Windows 2003 only. =20 dog -- now with the right sender name :) =20 =20 > To: freebsd-hackers@freebsd.org > From: ivoras@freebsd.org > Date: Fri=2C 4 Dec 2009 15:52:39 +0100 > Subject: Request for information - timers=2C hz=2C interrupts >=20 > For a long time=2C at least in the 6-stable timeframe=2C I was used to=20 > seeing timer interrupts going at the frequency of 2*HZ=2C e.g. this is=20 > from 6.4-RELEASE: >=20 > kern.clockrate: { hz =3D 250=2C tick =3D 4000=2C profhz =3D 166=2C stathz= =3D 33 } > debug.psm.hz: 20 >=20 > cpu0: timer 6789885563 499 > cpu2: timer 6789885538 499 > cpu1: timer 6789885538 499 > cpu3: timer 6789885537 499 >=20 > Then sometime in 7.x this changed to 4*HZ=2C which continues in 8.x=2C e.= g.=20 > from 7.2-RELEASE: >=20 > kern.clockrate: { hz =3D 250=2C tick =3D 4000=2C profhz =3D 1000=2C stath= z =3D 142 } > kern.hz: 250 >=20 > cpu0: timer 1368329715 988 > cpu1: timer 1368324640 988 > cpu2: timer 1367642854 988 > cpu3: timer 1367642874 988 >=20 > I'm not very worried about it (though maybe laptop users might be=20 > because of potential power drainage) but would like to know the=20 > explanation behind it. >=20 > Presumably it has something to do with profhz but what and why? There=20 > isn't an obvious correlation between profhz frequency in 6.x and HZ and=20 > in 7.x. and HZ. >=20 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe=2C send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg" =20 _________________________________________________________________ Windows 7: agora com conex=F5es autom=E1ticas de rede. Conhe=E7a. http://www.microsoft.com/brasil/windows7/default.html?WT.mc_id=3D1539=