From owner-freebsd-smp Sun Apr 27 20:04:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA15565 for smp-outgoing; Sun, 27 Apr 1997 20:04:23 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA15557 for ; Sun, 27 Apr 1997 20:04:20 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/8.7.3) with SMTP id XAA01565; Sun, 27 Apr 1997 23:04:18 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id XAA08741; Sun, 27 Apr 1997 23:04:15 -0400 Date: Sun, 27 Apr 1997 23:03:38 -0400 (EDT) From: Chuck Robey To: Ben Black cc: FreeBSD-SMP@FreeBSD.org Subject: Re: SMP In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-smp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 27 Apr 1997, Ben Black wrote: > 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). One per CPU? One lock total? How many copies of the kernel are running at once? How is caching handled, per cpu, or globally (forcing the two cpu's to look like one?) When a system call executes, what handles it, one cpu? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+-----------------------------------------------