From owner-freebsd-current@FreeBSD.ORG Sat Jan 15 12:20:10 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 111CB16A4CE; Sat, 15 Jan 2005 12:20:10 +0000 (GMT) Received: from acampi.inet.it (acampi.inet.it [213.92.1.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99F3943D41; Sat, 15 Jan 2005 12:20:07 +0000 (GMT) (envelope-from andrea@acampi.inet.it) Received: by acampi.inet.it (Postfix, from userid 1000) id 43C481A; Sat, 15 Jan 2005 13:20:06 +0100 (CET) Date: Sat, 15 Jan 2005 13:20:06 +0100 From: Andrea Campi To: John Baldwin Message-ID: <20050115122005.GA70274@webcom.it> References: <200501141546.31386.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501141546.31386.jhb@FreeBSD.org> User-Agent: Mutt/1.5.6i cc: phk@FreeBSD.org cc: current@FreeBSD.org cc: bde@FreeBSD.org Subject: Re: [PATCH] Use local APIC timer to drive kernel clocks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jan 2005 12:20:10 -0000 On Fri, Jan 14, 2005 at 03:46:31PM -0500, John Baldwin wrote: > IPIs per second. Instead, I went with a simpler algorithm suggested by phk > that lets me run the timer at hz and guarantees that statclock() will be > called stathz times per second, just not evenly spaced. The same is true I guess this assumes hz > stathz? If that's true and this is committed, you should send a big headsup, as people may still have HZ=100 (I know that's not default, but habits are hard to change). Bye, Andrea -- Intel: where Quality is job number 0.9998782345!