From owner-freebsd-arch@FreeBSD.ORG  Wed Apr 30 08:40:39 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 AFF1A37B401
	for <freebsd-arch@freebsd.org>; Wed, 30 Apr 2003 08:40:39 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BDB5943F85
	for <freebsd-arch@freebsd.org>; Wed, 30 Apr 2003 08:40:38 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h3UFeaNj012433;
	Wed, 30 Apr 2003 17:40:36 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: Andrew Gallatin <gallatin@cs.duke.edu>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Wed, 30 Apr 2003 11:20:34 EDT."
             <16047.59842.60959.352839@grasshopper.cs.duke.edu> 
Date: Wed, 30 Apr 2003 17:40:36 +0200
Message-ID: <12432.1051717236@critter.freebsd.dk>
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:40:40 -0000

In message <16047.59842.60959.352839@grasshopper.cs.duke.edu>, Andrew Gallatin 
writes:
>
>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..

I'm not sure you should infer too much yet...

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.