From owner-freebsd-hackers Sun Mar 9 23:10:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA11346 for hackers-outgoing; Sun, 9 Mar 1997 23:10:46 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA11307 for ; Sun, 9 Mar 1997 23:10:38 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA04022; Mon, 10 Mar 1997 00:16:31 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id XAA26620; Sun, 9 Mar 1997 23:54:12 +0100 (MET) Message-ID: <19970309235411.LH28573@uriah.heep.sax.de> Date: Sun, 9 Mar 1997 23:54:11 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: bmcgover@cisco.com (Brian McGovern) Subject: Re: Performance questions (Interrupt vs. polled) References: <3.0.32.19970307084514.00905c60@visigenic.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <3.0.32.19970307084514.00905c60@visigenic.com>; from Tim Oneil on Mar 7, 1997 08:45:15 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Tim Oneil wrote: > No flame. My learned opinion however is that a system with efficiant thread > scheduling (such as freeBSD) is best served by polling. Interrupted tasking > is best for serial, brain-dead systems, like DOS. You've just got this reversed. A decent multiprocessing system benefits a lot from hardware that can do interrupt notification right when there is something to do. The worst that could happen are CPU spin loops where the CPU is waiting for some bit to be set by a peripheral device. (That's why IDE drives are ugly.) To the contrary, DOS often doesn't use interrupt-controlled drivers, so you can even work with peripherals that have a broken-by-design interrupt behaviour (like the IRQ clash for COM1/3 or COM2/4). This doesn't do much harm there, since it's a single-process system, so the CPU has to wait anyway until the current operation has completed. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)