From owner-freebsd-arch@FreeBSD.ORG Thu Nov 4 20:54:44 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 236A816A4CE for ; Thu, 4 Nov 2004 20:54:44 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id D06D543D45 for ; Thu, 4 Nov 2004 20:54:43 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 2437 invoked from network); 4 Nov 2004 20:54:43 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 4 Nov 2004 20:54:42 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iA4KsIlG088385; Thu, 4 Nov 2004 15:54:22 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-arch@FreeBSD.org Date: Thu, 4 Nov 2004 14:56:33 -0500 User-Agent: KMail/1.6.2 References: <48555.1099585930@critter.freebsd.dk> <418A5A72.6020700@freebsd.org> In-Reply-To: <418A5A72.6020700@freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411041456.33778.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= cc: Poul-Henning Kamp cc: Scott Long cc: arch@FreeBSD.org Subject: Re: HEADSUP: HZ=1000 by default on i386 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 20:54:44 -0000 On Thursday 04 November 2004 11:36 am, Scott Long wrote: > Poul-Henning Kamp wrote: > > In message , =?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= writes: > >>Poul-Henning Kamp writes: > >>>So pending any really good arguments to the contrary I plan to increase > >>>HZ to 1000 on i386 this weekend. > >> > >>two good arguments: > >> > >> 1) I'm already working on this, and you know it, since I asked you > >> about it in Karlsruhe. > > > > Ahh, sorry, I got the impression that you were not going to do it on > > your own. > > > >> 2) 1000 is not a good choice, because we can't approximate it well > >> with the 8254. 1268 is better, 1381 is even better, 1903 is the > >> best we can do between 1000 and 2000, 2299 is the best we can do > >> between 1000 and 5000. > > > > I played with it here and found that 1000 actually works better than 941. > > (1193182 / 941 ~= 1268) because the 941 gives a slow beat against 1Hz. > > > > It is actually preferable to have a fast beat (jitter) than a slow > > beat (wander), particularly for people doing benchmarks. > > > > Poul-Henning > > What timing hardware is used on amd64? Would it suffer there too? Identical to x86 for now. Note that it would be really nice at some point to drive hardclock and statclock via the local APIC timers for SMP on x86 and amd64 so we can stop sending IPIs for each clock interrupt. Alpha uses the per-CPU timers this way already. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org