Date: Mon, 26 Jun 2000 11:29:39 +0100 (BST) From: Nick Hibma <n_hibma@calcaphon.com> To: Mike Smith <msmith@FreeBSD.ORG> Cc: FreeBSD CURRENT Mailing List <current@FreeBSD.ORG> Subject: Re: irunning, width in bits. Message-ID: <Pine.BSF.4.20.0006261125350.11136-100000@localhost> In-Reply-To: <200006260823.BAA00624@mass.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > >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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.20.0006261125350.11136-100000>