From owner-freebsd-net@FreeBSD.ORG  Fri Apr  4 09:46:30 2003
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 916)
	id 1F94E37B404; Fri,  4 Apr 2003 09:46:29 -0800 (PST)
Date: Fri, 4 Apr 2003 09:46:28 -0800
From: Prafulla Deuskar <pdeuskar@freebsd.org>
To: freebsd-net@freebsd.org
Message-ID: <20030404094628.A59969@hub.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
X-Operating-System: FreeBSD 4.8-RC on an i386
Subject: Disable/Enable Interrupts in ISR
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2003 17:46:30 -0000

All,

foo_intr()
{
...
disable_intr;
...
process data;
...
enable_intr;
}

Most of the network drivers currently do something like this in the ISR.
Is this really necessary as by the time ISR is called interrupts have already been
disabled on APIC and disabling interrupts on network card has no effect.

Is there an issue on non-x86 architectures?

Thanks,
Prafulla