From owner-freebsd-current Mon Jun 26 3:41:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 2E38637BBEF; Mon, 26 Jun 2000 03:41:15 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 136WKG-000Ixi-0K; Mon, 26 Jun 2000 10:41:12 +0000 Received: from henny.webweaving.org (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id LAA53232; Mon, 26 Jun 2000 11:42:43 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id LAA11165; Mon, 26 Jun 2000 11:29:39 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Mon, 26 Jun 2000 11:29:39 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Mike Smith Cc: FreeBSD CURRENT Mailing List Subject: Re: irunning, width in bits. In-Reply-To: <200006260823.BAA00624@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >From what I understood from dfr, when switching away from an interrupt > > handler it is converted into a full thread. When the second piece of > > hardware fires an interrupt it could then run at the same time. > > I thought of this almost immediately - it's a bad idea though because it > makes it hard to determine when to EOI an interrupt. > > If you expect to perform significant processing in your interrupt > handler, you should consider a taskq. Right. It would be nice however to not have to go through the trouble of moving things onto different interrupts. Current BIOS's do not quite let you decide on which interrupt you would like to have assigned to the various cards. It will spread them in some way, but that might not spread the two high interrupt count cards onto separate interrupts. You have to move the hardware around in the slots to get things sorted in some cases. I guess that the perfect solution is to be able to hardwire the PCI irqs in some way once FreeBSD is doing the PnP resource allocation. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message