From owner-freebsd-arch@FreeBSD.ORG  Wed Apr 30 08:20:40 2003
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7F75D37B401
	for <freebsd-arch@freebsd.org>; Wed, 30 Apr 2003 08:20:40 -0700 (PDT)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9B97543FBF
	for <freebsd-arch@freebsd.org>; Wed, 30 Apr 2003 08:20:39 -0700 (PDT)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu
	[152.3.145.30])
	by duke.cs.duke.edu (8.12.9/8.12.9) with ESMTP id h3UFKdMS029125
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 30 Apr 2003 11:20:39 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h3UFKYE85847;
	Wed, 30 Apr 2003 11:20:34 -0400 (EDT)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16047.59842.60959.352839@grasshopper.cs.duke.edu>
Date: Wed, 30 Apr 2003 11:20:34 -0400 (EDT)
To: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: <8764.1051715905@critter.freebsd.dk>
References: <16047.59314.532227.475952@grasshopper.cs.duke.edu>
	<8764.1051715905@critter.freebsd.dk>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
cc: freebsd-arch@freebsd.org
Subject: Re: lots of malloc(M_WAITOK)'s in interrupt context from camisr 
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2003 15:20:40 -0000


Poul-Henning Kamp writes:
 > In message <16047.59314.532227.475952@grasshopper.cs.duke.edu>, Andrew Gallatin
 >  writes:
 > >
 > >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
 > >
 > >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()?
 > 
 > Calling wakeup() is just about it, but we should actually define it
 > more precisely in a suitable man-page.

That would be cool.  Since wakeup() uses a spinlock,  I assume that
spinlocks are generally OK too..

Drew