From owner-freebsd-current Tue Apr 24 8:36:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 837CA37B422 for ; Tue, 24 Apr 2001 08:36:24 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f3OFZGU59444; Tue, 24 Apr 2001 17:35:16 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Garrett Wollman Cc: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: vm_mtx In-Reply-To: Your message of "Tue, 24 Apr 2001 11:27:24 EDT." <200104241527.LAA95978@khavrinen.lcs.mit.edu> Date: Tue, 24 Apr 2001 17:35:16 +0200 Message-ID: <59442.988126516@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200104241527.LAA95978@khavrinen.lcs.mit.edu>, Garrett Wollman write s: >< said: > >> You can find the work I've done so far to make a giant vm mutex >> here: > >The Mach code we originally inherited was supposed to already by >multiprocessor safe. Did we manage to eliminate that capability? I'm sure you are fully aware of the implications of the strategically placed "supposed" in your own sentence. I have never heard anybody get Mach code multithreaded yet. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message