Date: Tue, 21 Nov 2000 18:46:15 -0700 From: Drew Eckhardt <drew@PoohSticks.ORG> To: freebsd-hackers@freebsd.org Subject: Interrupt threads Message-ID: <200011220146.eAM1kFh09832@chopper.Poohsticks.ORG>
next in thread | raw e-mail | index | archive | help
For reasons beyond my control, I'm stuck using FreeBSD in a real time system and am violating my timing constraints when too many SCSI commands complete in a short time frame and starve one of my userland real time processes. If the interrupt handler wokeup a kernel thread running at a lower real-time priority than my application which disabled the interrupt on the PIC/APIC, ran the handler, and re-enabled the line on the PIC/APIC my problems should go away. -CURRENT supposedly uses threads for interrupts. Is there a more specific description of what it does archived somewhere? Assuming familiarity with the interrupt code and a cursory but improving understanding of the scheduler, how messy would it be to retrofit that code to -stable or 3.1-stable ? -- <a href="http://www.poohsticks.org/drew/">Home Page</a> For those who do, no explanation is necessary. For those who don't, no explanation is possible. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011220146.eAM1kFh09832>