From owner-freebsd-hackers Tue Oct 7 23:30:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA24302 for hackers-outgoing; Tue, 7 Oct 1997 23:30:42 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA24294 for ; Tue, 7 Oct 1997 23:30:39 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA07775; Tue, 7 Oct 1997 23:28:39 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd007773; Wed Oct 8 06:28:38 1997 Date: Tue, 7 Oct 1997 23:27:32 -0700 (PDT) From: Julian Elischer To: mdean cc: Peter Dufault , hackers@FreeBSD.ORG Subject: Re: A world of unexplored pain. In-Reply-To: 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 On Tue, 7 Oct 1997, mdean wrote: > > 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. > > > > OIf what you plan to do canbe done in a few instructiosn then, NO, there is no detrimental effect that I have ever seen, we run it here at 1KHz and 10KHz, and have seen no problems. clock is at a high priority, so jitter should be low. Just remember to keep what you want to a minimum, and do all the rest of the work elsewhere.