From owner-freebsd-current@FreeBSD.ORG Sun Jan 30 22:53:12 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 D6E0416A4CE; Sun, 30 Jan 2005 22:53:12 +0000 (GMT) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA78843D2D; Sun, 30 Jan 2005 22:53:12 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with SMTP id 3050246B0A; Sun, 30 Jan 2005 17:53:12 -0500 (EST) Date: Sun, 30 Jan 2005 22:52:34 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Mike Silbersack In-Reply-To: <20050130151427.U59844@odysseus.silby.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Poul-Henning Kamp cc: current@freebsd.org cc: Colin Percival 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 22:53:13 -0000 On Sun, 30 Jan 2005, Mike Silbersack wrote: > change to the callout API? Just a few places in the kernel account for > most of the use of callouts, so even if a rewrite of those would be > necessary, it should pay off. Well, part of the problem is that many callouts always re-register, and right now they're forced to pay a penalty for it. I almost wonder if we shouldn't add a new flag or method to swap the costs: register a recurring callout every (x) ticks, and you pay a cost to unregister it if the flag is set, and the callout is otherwise automatically rescheduled. Robert N M Watson