From owner-freebsd-hackers Thu Mar 30 16:41:12 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA04474 for hackers-outgoing; Thu, 30 Mar 1995 16:41:12 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA04463 for ; Thu, 30 Mar 1995 16:41:08 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id RAA08865; Thu, 30 Mar 1995 17:45:05 -0700 Date: Thu, 30 Mar 1995 17:45:05 -0700 From: Nate Williams Message-Id: <199503310045.RAA08865@trout.sri.MT.net> In-Reply-To: David Greenman "Re: help with splbio, splnet, spl..." (Mar 30, 4:19pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: davidg@Root.COM, terry@cs.weber.edu (Terry Lambert) Subject: Re: help with splbio, splnet, spl... Cc: freebsd-hackers@FreeBSD.org Sender: hackers-owner@FreeBSD.org Precedence: bulk [ What do the spl* routines do? ] > >It's a tiered interrupt scheme. You can block all interrupts > >at or below a specified priority while you are doing high > >priority stuff so that it gets done in time. The "fast" > >interrupts can't be blocked. > > It doesn't work this way in FreeBSD. It is not a tierd interrupt scheme. > Each of the interrupt classes are independant and do NOT block the others. The > only exception to this is tty and net are ored together if you are using SLIP > or PPP (the reason should be obvious). Interesting. I wasn't aware that you could do this on a PC, since I was under the impression that you had to have a tiered scheme with the 8259. Obviously I was mis-informed since this would imply that no interrupt is given a higher priority over another interrupt. Is there any way this can be done short of OR'ing a lot of the different masks together to keep certain interrupts from happening? Is this how the sio driver does things? (I know, use the source...) Nate