From owner-freebsd-arch@FreeBSD.ORG Sat Oct 18 13:02:31 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32F8316A4B3 for ; Sat, 18 Oct 2003 13:02:31 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 92CD843FA3 for ; Sat, 18 Oct 2003 13:02:28 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 47249 invoked by uid 1000); 18 Oct 2003 20:02:29 -0000 Date: Sat, 18 Oct 2003 13:02:29 -0700 (PDT) From: Nate Lawson To: arch@freebsd.org Message-ID: <20031018130119.T47207@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Variable timer tick rate? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Oct 2003 20:02:31 -0000 This is an interesting approach. If there are no upcoming timeouts, decrease the tick rate. Of course, you have to amortize the cost of resetting the timer over the period of no ticks. http://kerneltrap.org/node/view/1006 -Nate