From owner-freebsd-smp Wed Sep 6 11:32:55 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id 6175637B423 for ; Wed, 6 Sep 2000 11:32:53 -0700 (PDT) Received: from pacbell.net ([63.194.212.226]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0G0H006XTA4XLO@mta6.snfc21.pbi.net> for smp@freebsd.org; Wed, 6 Sep 2000 11:31:45 -0700 (PDT) Date: Wed, 06 Sep 2000 11:26:36 -0700 From: Adagio Vangogh Subject: Re: Sept 5th patch ... To: joel boutros Cc: smp@freebsd.org Reply-To: adagio_v@pacbell.net Message-id: <39B68C5C.3C21C55E@pacbell.net> MIME-version: 1.0 X-Mailer: Mozilla 4.74 [en] (Win98; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en References: <20000906180520.8B54A37B422@hub.freebsd.org> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org joel boutros wrote: > the general trick is locking critical sections of code or data. > previously when you did an splXXX(), you were assured that you > weren't going to get interrupted by anything of specified priority > or lower, so it was safe to assume your data probably wasn't going > to change out from under you. 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? --adagio v. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message