From owner-freebsd-hackers Thu Jul 2 12:38:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24079 for freebsd-hackers-outgoing; Thu, 2 Jul 1998 12:38:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24074 for ; Thu, 2 Jul 1998 12:38:53 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA28401; Thu, 2 Jul 1998 12:35:07 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd028389; Thu Jul 2 19:35:02 1998 Date: Thu, 2 Jul 1998 12:34:58 -0700 (PDT) From: Julian Elischer To: "Ron G. Minnich" cc: hackers@FreeBSD.ORG Subject: RE: timeout granularity (was: Re: Console driver...) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG why do all that fiddling when there is already support for this in FreeBSD? use "aquire_timer0()" and set the hardware clock to whatever you want dynamically.. it will call whatever function you want at that speed.. remember that the pcaudio driver sets it to 16000 Hz. that would seem a good speed to set it, so that pcaudio could still work.. On Thu, 2 Jul 1998, Ron G. Minnich wrote: > > On Thu, 2 Jul 1998 sbabkin@dcn.att.com wrote: > > The measurements > > have shown that handling 115200 bps transfer caused 11520 > > interrupts per second and ate up about 20% CPU of 20 MHz 386 > > in the interrupt handler. The OS was SCO Unix 3.2.1. > > Interesting. One the 486/25, linux 1.0.xx, the 10k interrupts also seemed to > eat about 20% of the machine. > > ron > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message