From owner-freebsd-current  Tue Apr 17 18:48:37 2001
Delivered-To: freebsd-current@freebsd.org
Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3])
	by hub.freebsd.org (Postfix) with ESMTP id 24DAA37B43F
	for <current@FreeBSD.ORG>; Tue, 17 Apr 2001 18:48:33 -0700 (PDT)
	(envelope-from eddy+public+spam@noc.everquick.net)
Received: from localhost (eddy@localhost)
	by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f3I1m7B14438;
	Wed, 18 Apr 2001 01:48:07 GMT
X-EverQuick-No-Abuse: Report any e-mail abuse to <abuse@noc.everquick.net>
Date: Wed, 18 Apr 2001 01:48:06 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: Alfred Perlstein <bright@wintelcom.net>
Cc: Matt Dillon <dillon@earth.backplane.com>,
	Greg Lehey <grog@lemis.com>, "Justin T. Gibbs" <gibbs@scsiguy.com>,
	Doug Barton <DougB@DougBarton.net>,
	"current @ freebsd . org" <current@FreeBSD.ORG>
Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge
 performance boost)
In-Reply-To: <20010417182840.A976@fw.wintelcom.net>
Message-ID: <Pine.LNX.4.20.0104180143210.14364-100000@www.everquick.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Date: Tue, 17 Apr 2001 18:28:40 -0700
> From: Alfred Perlstein <bright@wintelcom.net>
> 
>     1) interrupts are again fan-in, meaning if you block an interrupt
>     class on one cpu you block them on all cpus

When would this be a bad case?  i.e., if an interrupt [class] must be
blocked, would we not it blocked across the board?


Eddy

---------------------------------------------------------------------------

Brotsman & Dreger, Inc.
EverQuick Internet / EternalCommerce Division

Phone: (316) 794-8922

---------------------------------------------------------------------------


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message