From owner-freebsd-smp  Wed Sep  6 11:39:39 2000
Delivered-To: freebsd-smp@freebsd.org
Received: from crewsoft.com (ns.aenet.net [157.22.214.1])
	by hub.freebsd.org (Postfix) with ESMTP id 2532037B424
	for <smp@freebsd.org>; Wed,  6 Sep 2000 11:39:37 -0700 (PDT)
Received: from [63.197.8.222] (HELO wireless-networks.com)
  by crewsoft.com (CommuniGate Pro SMTP 3.3b5)
  with ESMTP id 285138; Wed, 06 Sep 2000 11:41:17 -0700
Message-ID: <39B68F61.6B528751@wireless-networks.com>
Date: Wed, 06 Sep 2000 11:39:29 -0700
From: Cedric Berger <cedric@wireless-networks.com>
X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: adagio_v@pacbell.net
Cc: smp@freebsd.org
Subject: Re: Sept 5th patch ...
References: <20000906180520.8B54A37B422@hub.freebsd.org> <39B68C5C.3C21C55E@pacbell.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>   FreeBSD has always used the notion of a "class" mask for interrupts
>   and not priorities. Ie, all network devices fell under the net class and
>
>   only a member of this class would block the rest of the members in the
>   same class. How's this handled?

I guess that you have to figure out why it this "class" of device is protected

at some point, (for example, access to the stack input queue), and protect
that specific *object* (i.e. the stack input queue) with a mutex.

Cedric




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