From owner-freebsd-net@FreeBSD.ORG Wed Feb 11 15:28:03 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C8F216A4CE; Wed, 11 Feb 2004 15:28:03 -0800 (PST) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84D9543D2F; Wed, 11 Feb 2004 15:28:02 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])i1BNRvLE006320; Thu, 12 Feb 2004 10:27:57 +1100 Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) i1BNRsi1012371; Thu, 12 Feb 2004 10:27:54 +1100 Date: Thu, 12 Feb 2004 10:27:53 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Andre Oppermann In-Reply-To: <402A3339.1BAAF97F@freebsd.org> Message-ID: <20040212100815.O83287@gamplex.bde.org> References: <200402111335.NAA09040@starburst.demon.co.uk> <402A3339.1BAAF97F@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Bjorn Eikeland cc: freebsd-net@freebsd.org cc: richard@wendland.org.uk Subject: Re: dummynet = local taffic > 100ms - help! X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2004 23:28:03 -0000 On Wed, 11 Feb 2004, Andre Oppermann wrote: > Richard Wendland wrote: > > Tom Pavel sent some patches to this list on 14 Jan 2004 that he has been > > using to overcome this HZ/RFC1323 problem. > > I remember some comments (by BDE?) to the effect that the patch is not > entirely correct. It was just inelegant. There are several different tick counters already active. None are quite right, but perhaps one could be adapted. The closest to being right is the implicit one in tc_ticktock(). This defaults to a period of max(1/1000, 1/HZ) seconds but doesn't guarantee a period of > 1/1000 seconds since it can be meddled with using the kern.timecounter.tick sysctl. There is also the implicit one in sched_clock(). sched_clock() is supposed to be called every 1/128 seconds (to within a factor of 2). Bruce