From owner-freebsd-smp  Sun Apr 27 20:57:45 1997
Return-Path: <owner-smp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id UAA18957
          for smp-outgoing; Sun, 27 Apr 1997 20:57:45 -0700 (PDT)
Received: from nyx.pr.mcs.net (nyx.pr.mcs.net [204.95.55.81])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA18946
          for <FreeBSD-SMP@FreeBSD.org>; Sun, 27 Apr 1997 20:57:39 -0700 (PDT)
Received: from nyx.pr.mcs.net (localhost [127.0.0.1])
	by nyx.pr.mcs.net (8.8.5/8.8.5) with ESMTP id WAA12920;
	Sun, 27 Apr 1997 22:57:12 -0500 (CDT)
Message-Id: <199704280357.WAA12920@nyx.pr.mcs.net>
X-Mailer: exmh version 1.6.9 8/22/96
To: Ben Black <black@zen.cypher.net>
cc: Chuck Robey <chuckr@mat.net>, FreeBSD-SMP@FreeBSD.org
Subject: Re: SMP 
In-reply-to: Your message of Sun, 27 Apr 1997 22:53:57 -0400.
             <Pine.LNX.3.91.970427225228.32065M-100000@zen.cypher.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 27 Apr 1997 22:57:12 -0500
From: Chris Csanady <ccsanady@nyx.pr.mcs.net>
Sender: owner-smp@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk


>freebsd-smp is not the best example of how to do SMP.  it uses the 
>simplest method: one giant kernel lock.  i don't know that it is 
>particularly representative of advanced SMP operating systems (though 
>linux also uses a giant kernel lock).

Actually, linux has moved to a slightly finer grain system.  Now they
have seperate locks for the run queues, scheduler, and some other
things..

--Chris Csanady