Date: Fri, 12 Aug 2011 13:15:21 +0530 From: Ninad Adi <adi.ninad@gmail.com> To: Julian Elischer <julian@freebsd.org> Cc: "freebsd-threads@freebsd.org" <freebsd-threads@freebsd.org> Subject: Re: Urgent interrupt thread Message-ID: <CAEOZPkbi0vvvASpnf_wLqrfPCUTTRp_yr5b%2B6pOW=WZdTgR--Q@mail.gmail.com> In-Reply-To: <4E44CBA6.9050809@freebsd.org> References: <CAEOZPkYPQeBv7t0vUDN%2BY6jXUQ6HdK7eJb05gfXNUwb49Wphag@mail.gmail.com> <4E44CBA6.9050809@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
So in the routine bus_setup_intr the isr runs as ithread but then if its a thread why its not allowed to sleep it aquires mutex lock , disables all interrupts and continues. My last question is in that case do we need to Use taskqueues or we can completely write the Isr in one thread itself without using deferring Primitives. I.e can we refrain from using deferring mechanism. awaiting the reply. Ninad Adi. On Friday, August 12, 2011, Julian Elischer <julian@freebsd.org> wrote: > On 8/11/11 3:13 AM, Ninad Adi wrote: >> >> To, >> Freebsd greats, >> >> Dear sirs, >> In freebsd 8.2 kernel architecture >> Do interrupt handlers run as threads by >> default or do they run in interrupt context ?? >> >> Ninad. >> Freebsd developer. >> _______________________________________________ >> freebsd-threads@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-threads < http://lists.freebsd.org/mailman/listinfo/freebsd-threads>; >> To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org " >> > you have the choice to do either. > > > key words to look up are 'fast' interrupts and "interrrupt threads" > > I've not used either for many years. so I hope that helps enough that you can find hte right answer. > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAEOZPkbi0vvvASpnf_wLqrfPCUTTRp_yr5b%2B6pOW=WZdTgR--Q>