Date: Tue, 18 Jul 2000 21:58:57 -0600 From: Chuck Paterson <cp@bsdi.com> To: Greg Lehey <grog@lemis.com> Cc: Warner Losh <imp@village.org>, arch@freebsd.org, smp@freebsd.org Subject: Re: Tidying up the interrupt registration process Message-ID: <200007190358.VAA09445@berserker.bsdi.com>
next in thread | raw e-mail | index | archive | help
}That's what I thought. Does anybody else see a reason to convert fast }interrupts into threads? The short answer is no, you absolutely don't want to convert them to fully instantiated threads, especially when you only have a heavy wait solution. There is another middle ground that is less clear, and it depends partially on what you deem a thread. If you just switch the stack pointer and curproc, but use spin locks and don't allow for a context switch are you converting it to a thread. At this point the statistical stuff will charge time properly to interrupts rather than user processes, or other kernel processes, you also don't have to worry about pathological cases blowing out the stack. Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200007190358.VAA09445>