Date: Thu, 1 May 2003 16:14:09 +0100 From: Paul Richards <paul@freebsd-services.com> To: Bruce Evans <bde@zeta.org.au> Cc: freebsd-arch@freebsd.org Subject: Re: lots of malloc(M_WAITOK)'s in interrupt context from camisr Message-ID: <20030501151409.GD1869@survey.codeburst.net> In-Reply-To: <20030501144708.I18220@gamplex.bde.org> References: <200304290438.h3T4cdHE069528@arch20m.dellroad.org> <16047.59314.532227.475952@grasshopper.cs.duke.edu> <20030501144708.I18220@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 01, 2003 at 04:31:08PM +1000, Bruce Evans wrote: > On Wed, 30 Apr 2003, Andrew Gallatin wrote: > > > John Baldwin writes: > > > > > If you need to do more work in your interrupt routine than just wakeups > > > and dinking with registers, you can always wake up a software interrupt > > > handler or some other random kthread to do things that take a long amount > > (This is about normal interrupt handlers, not INTR_FAST ones.) > > > Dumb question: Exactly what is one allowed to do in an INTR_FAST > > interrupt context? Obviously, you can't sleep. But can you call > > wakeup()? What exactly defines a INTR_FAST interrupt context in the first place. Do we have any rules for when it should be used, it just seems to me that all interrupt handlers should be INTR_FAST and that we'd then just have interrupt handlers. -- Paul Richards
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030501151409.GD1869>