From owner-freebsd-hackers Tue Oct 7 23:09:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA23077 for hackers-outgoing; Tue, 7 Oct 1997 23:09:16 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from proxy3.ba.best.com (root@proxy3.ba.best.com [206.184.139.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA23072 for ; Tue, 7 Oct 1997 23:09:14 -0700 (PDT) (envelope-from mdean@shellx.best.com) Received: from shellx.best.com (shellx.best.com [206.86.0.11]) by proxy3.ba.best.com (8.8.7/8.8.BEST) with ESMTP id XAA04667; Tue, 7 Oct 1997 23:07:40 -0700 (PDT) Received: from localhost (mdean@localhost) by shellx.best.com (8.8.6/8.8.3) with SMTP id XAA23549; Tue, 7 Oct 1997 23:07:39 -0700 (PDT) Date: Tue, 7 Oct 1997 23:07:39 -0700 (PDT) From: mdean To: Julian Elischer cc: Peter Dufault , hackers@FreeBSD.ORG Subject: Re: A world of unexplored pain. In-Reply-To: <343AE7C6.592990BB@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Yes, through the acquire_timer0() call, does anyone know if acquiring the timer at a raised rate for a lengthy perios of time has any detrimental effects? > well for a start in FreeBSD the system provides a way of raising > the hardware clockrate transparently on the fly to do this sort > of thing the PCAUDIO device routinelyu raises the clockrate to > 16000 Hz. >