From owner-freebsd-questions@FreeBSD.ORG Sat Nov 26 01:24:28 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3655416A41F for ; Sat, 26 Nov 2005 01:24:25 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2303743D49 for ; Sat, 26 Nov 2005 01:24:24 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id 37E81D17ABB for ; Fri, 25 Nov 2005 20:24:23 -0500 (EST) Received: from frontend2.messagingengine.com ([10.202.2.151]) by frontend1.internal (MEProxy); Fri, 25 Nov 2005 20:24:23 -0500 X-Sasl-enc: sZTI5qsqTc4Itc29WMwOyeZY2hC0XkdV8s5km91RcY6x 1132968260 Received: from gumby.localdomain (88-104-192-20.dynamic.dsl.as9105.com [88.104.192.20]) by frontend2.messagingengine.com (Postfix) with ESMTP id 74CAE571431 for ; Fri, 25 Nov 2005 20:24:20 -0500 (EST) From: RW To: freebsd-questions@freebsd.org Date: Sat, 26 Nov 2005 01:24:20 +0000 User-Agent: KMail/1.8.3 References: <20051124013438.T8326@chylonia.3miasto.net> <20051124204359.GD30073@xor.obsecurity.org> <20051125064503.GA707@bsd.trippelsdorf.de> In-Reply-To: <20051125064503.GA707@bsd.trippelsdorf.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511260124.22384.list-freebsd-2004@morbius.sent.com> Subject: Re: so much clock interrupts?! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Nov 2005 01:24:28 -0000 On Friday 25 November 2005 06:45, Markus Trippelsdorf wrote: > 2000 interrupts per second per core for the timer is a > ridiculous high number and I reduce it simply for aesthetic reasons. > This may be a religious issue and everyone should use what he or she > seems fitting. If you think in a wider perspective, and consider the number of cpu cycles per interrupt on historical and embedded cpus, 2000 Hz is pretty conservative.