Date: Mon, 26 Aug 2002 13:17:24 -0400 From: Bosko Milekic <bmilekic@unixdaemons.com> To: Maksim Yevmenkin <myevmenk@exodus.net> Cc: John Baldwin <jhb@FreeBSD.ORG>, "M. Warner Losh" <imp@bsdimp.com>, hackers@FreeBSD.ORG Subject: Re: Fast interrupts Message-ID: <20020826131724.A48213@unixdaemons.com> In-Reply-To: <3D6A61F7.872038E5@exodus.net>; from myevmenk@exodus.net on Mon, Aug 26, 2002 at 10:14:32AM -0700 References: <XFMail.20020826112635.jhb@FreeBSD.org> <3D6A5A47.57672729@exodus.net> <20020826130611.A48166@unixdaemons.com> <3D6A61F7.872038E5@exodus.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 26, 2002 at 10:14:32AM -0700, Maksim Yevmenkin wrote: > Bosko Milekic wrote: > > > > On Mon, Aug 26, 2002 at 09:41:43AM -0700, Maksim Yevmenkin wrote: > > > John Baldwin wrote: > > > > > > > > On 26-Aug-2002 M. Warner Losh wrote: > > > > > can you call wakeup(9) from a fast interrupt handler? > > > > > > [ ...] > > > > > > > > The only reason I ask is because sio seems to go out of its way to > > > > > schedule a soft interrupt to deal with waking up processes, which then > > > > > calls wakeup... > > > > > > > > Since wakeup only needs a spin lock, it is probably ok. You just can't call > > > > anything that would sleep (in any interrupt handler) or block on a non-spin > ^^^^^^^^^^^^^^^^^^^^^^^^^^ > my understanding is that John was talking about any > interrupt handler. Not just fast interrupt hander. Yeah, you can't call anything that would _sleep_ (e.g., msleep()). You could still grab a MTX_DEF mutex for a non-fast interrupt handler and possibly block waiting to get it. -- Bosko Milekic * bmilekic@unixdaemons.com * bmilekic@FreeBSD.org 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?20020826131724.A48213>