From owner-freebsd-arch@FreeBSD.ORG  Thu May  1 08:14:11 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 B6A6B37B401
	for <freebsd-arch@freebsd.org>; Thu,  1 May 2003 08:14:11 -0700 (PDT)
Received: from mx0.freebsd-services.com (survey.codeburst.net
	[195.149.39.161])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2F9E343FA3
	for <freebsd-arch@freebsd.org>; Thu,  1 May 2003 08:14:11 -0700 (PDT)
	(envelope-from paul@freebsd-services.com)
Received: by mx0.freebsd-services.com (Postfix, from userid 1002)
	id 04FEE1B214; Thu,  1 May 2003 16:14:09 +0100 (BST)
Date: Thu, 1 May 2003 16:14:09 +0100
From: Paul Richards <paul@freebsd-services.com>
To: Bruce Evans <bde@zeta.org.au>
Message-ID: <20030501151409.GD1869@survey.codeburst.net>
References: <200304290438.h3T4cdHE069528@arch20m.dellroad.org>
	<16047.59314.532227.475952@grasshopper.cs.duke.edu>
	<20030501144708.I18220@gamplex.bde.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030501144708.I18220@gamplex.bde.org>
User-Agent: Mutt/1.4.1i
cc: Andrew Gallatin <gallatin@cs.duke.edu>
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: Thu, 01 May 2003 15:14:12 -0000

On Thu, May 01, 2003 at 04:31:08PM +1000, Bruce Evans wrote:
> On Wed, 30 Apr 2003, Andrew Gallatin wrote:
> 
> > 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
> 
> (This is about normal interrupt handlers, not INTR_FAST ones.)
> 
> > 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()?

What exactly defines a INTR_FAST interrupt context in the first
place. Do we have any rules for when it should be used, it just
seems to me that all interrupt handlers should be INTR_FAST and
that we'd then just have interrupt handlers.

-- 
Paul Richards