From owner-freebsd-hackers Mon Aug 26 10:14:38 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D371537B400; Mon, 26 Aug 2002 10:14:34 -0700 (PDT) Received: from scl8owa02.int.exodus.net (scl8out02.exodus.net [66.35.230.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A0A143E9E; Mon, 26 Aug 2002 10:14:34 -0700 (PDT) (envelope-from Maksim.Yevmenkin@exodus.net) Received: from scl8owa01.int.exodus.net ([66.35.230.241]) by scl8owa02.int.exodus.net with Microsoft SMTPSVC(5.0.2195.4905); Mon, 26 Aug 2002 10:16:19 -0700 Received: from exodus.net ([206.220.227.147]) by scl8owa01.int.exodus.net over TLS secured channel with Microsoft SMTPSVC(5.0.2195.4905); Mon, 26 Aug 2002 10:16:18 -0700 Message-ID: <3D6A61F7.872038E5@exodus.net> Date: Mon, 26 Aug 2002 10:14:32 -0700 From: Maksim Yevmenkin X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Bosko Milekic Cc: John Baldwin , "M. Warner Losh" , hackers@FreeBSD.ORG Subject: Re: Fast interrupts References: <3D6A5A47.57672729@exodus.net> <20020826130611.A48166@unixdaemons.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 26 Aug 2002 17:16:18.0678 (UTC) FILETIME=[4AAC9160:01C24D24] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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. > > > mutex. > > > > what is the general locking technique for interrupt handlers? > > there must be some sort of locking, right? > > You are allowed to use mutex locks (both spin and MTX_DEF), only you > are only allowed to user the former for fast interrupt handlers. thanks, max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message