From owner-freebsd-current@FreeBSD.ORG Sun Jan 30 21:06:13 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 39ED116A4D1 for ; Sun, 30 Jan 2005 21:06:13 +0000 (GMT) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 5FF4443D45 for ; Sun, 30 Jan 2005 21:06:12 +0000 (GMT) (envelope-from silby@silby.com) Received: (qmail 67487 invoked from network); 30 Jan 2005 21:06:11 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 30 Jan 2005 21:06:11 -0000 X-pair-Authenticated: 209.68.2.70 Date: Sun, 30 Jan 2005 15:06:10 -0600 (CST) From: Mike Silbersack To: Robert Watson In-Reply-To: Message-ID: <20050130150328.K59844@odysseus.silby.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Mon, 31 Jan 2005 12:46:43 +0000 cc: Poul-Henning Kamp cc: current@freebsd.org cc: cperciva@FreeBSD.org Subject: Re: tcp_isn_tick() / dummynet() callout madness ? 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: Sun, 30 Jan 2005 21:06:13 -0000 On Sun, 30 Jan 2005, Robert Watson wrote: > Note that the remainder run 1/100th as often, presumably because they do > hz/10 or hz/100 or the like. I've talked to both Colin Percival and Mike > Silby about the problem -- since the callout_reset() is one of the more > expensive parts of this code, Colin has been looking at some locking > optimizations to lower the cost. I attempted to convince Mike that if we > thought the ISN sequencing was "sufficiently secure" with HZ of 100, then > we should be able to still run it at hz/100 now instead of 1000 times per > second, but he seems resistant. I'll CC him so he's forced to reconsider > :-). You're right, reducing tcp_isn_tick to 100 hz won't really hurt anything. However, I'd still like an efficient way to run sometime once per tick. Is there a better place to hook in instead of callouts? Mike "Silby" Silbersack