From owner-freebsd-arch@FreeBSD.ORG  Sat Jan 10 06:15:30 2004
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 18F2916A4CE; Sat, 10 Jan 2004 06:15:30 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 8D7AA43D1D; Sat, 10 Jan 2004 06:15:26 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i0AEFIFu060043;
	Sat, 10 Jan 2004 15:15:24 +0100 (CET)
	(envelope-from phk@phk.freebsd.dk)
To: Bruce Evans <bde@zeta.org.au>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Sun, 11 Jan 2004 01:09:49 +1100."
             <20040111005502.O22604@gamplex.bde.org> 
Date: Sat, 10 Jan 2004 15:15:18 +0100
Message-ID: <60042.1073744118@critter.freebsd.dk>
cc: arch@freebsd.org
Subject: Re: Interrupt API change 
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: Sat, 10 Jan 2004 14:15:30 -0000

In message <20040111005502.O22604@gamplex.bde.org>, Bruce Evans writes:
>> Heuristics
>> can then be built on this information to better detect things like
>> interrupt storms.
>
>That'a about all it can do.

Considering the fatality of interrupt storms, this alone is reason
enough to implement the change.

>In the non-shared case,
>individual handlers can better decide about interrupt storms in a
>device-specific way.

Considering that interrupt storms more often than not are caused
by driver bugs, expecting the driver to mitigate seems terminally
optimistic to me.


-- 
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.