From owner-freebsd-current  Tue Apr 24  9:52:54 2001
Delivered-To: freebsd-current@freebsd.org
Received: from cs.rice.edu (cs.rice.edu [128.42.1.30])
	by hub.freebsd.org (Postfix) with ESMTP id 0FF9B37B422
	for <current@freebsd.org>; Tue, 24 Apr 2001 09:52:52 -0700 (PDT)
	(envelope-from alc@cs.rice.edu)
Received: (from alc@localhost)
	by cs.rice.edu (8.9.0/8.9.0) id LAA18154;
	Tue, 24 Apr 2001 11:52:35 -0500 (CDT)
Date: Tue, 24 Apr 2001 11:52:35 -0500
From: Alan Cox <alc@cs.rice.edu>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
	current@freebsd.org
Subject: Re: vm_mtx
Message-ID: <20010424115235.I28547@cs.rice.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5us
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> The Mach code we originally inherited was supposed to already by
> multiprocessor safe.  Did we manage to eliminate that capability?

Yes and no.  The vm_map layer still has the necessary locking calls,
but the vm_object and pmap layers don't.  The pmap is still similar
enough that the original locking scheme could be reapplied, perhaps
mechanically.

Alan


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