From owner-freebsd-hackers Thu Nov 12 10:08:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04161 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 10:08:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04155 for ; Thu, 12 Nov 1998 10:08:31 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id NAA17224; Thu, 12 Nov 1998 13:07:59 -0500 (EST) Date: Thu, 12 Nov 1998 13:07:59 -0500 (EST) From: Daniel Eischen Message-Id: <199811121807.NAA17224@pcnet1.pcnet.com> To: luigi@labinfo.iet.unipi.it, s0k9955@unix.tamu.edu Subject: Re: Timer Granularity Cc: freebsd-hackers@FreeBSD.ORG, mike@smith.net.au, shafiak@ee.tamu.edu Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I need a kernel clock of granularity 1ms or less, for some experiments. > > Which version of FreeBsd supports this granularity, other than the 3.0 > > version? > > > > There is a mention of the resolution depending on the clock > > sources in use. Which source gives me the best resolution?? > > settin HZ=1000 or more in the kernel config file should do the job (if > you go too high you might start losing ticks...) > > luigi I set HZ to 500 just a couple of days ago on a 1-2 month old -current system without too many hiccups. There still are a few places in the kernel that need to be fixed to use hz properly, though. sysbeep is one. Grep'ing for all the timeout()s and ensuring proper use of hz is a start. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message