From owner-freebsd-current  Wed Feb 17  4:42:30 1999
Delivered-To: freebsd-current@freebsd.org
Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33])
	by hub.freebsd.org (Postfix) with ESMTP id C2CD910E6B
	for <current@FreeBSD.ORG>; Wed, 17 Feb 1999 04:42:27 -0800 (PST)
	(envelope-from luoqi@watermarkgroup.com)
Received: (from luoqi@localhost)
	by lor.watermarkgroup.com (8.8.8/8.8.8) id HAA27848;
	Wed, 17 Feb 1999 07:42:26 -0500 (EST)
	(envelope-from luoqi)
Date: Wed, 17 Feb 1999 07:42:26 -0500 (EST)
From: Luoqi Chen <luoqi@watermarkgroup.com>
Message-Id: <199902171242.HAA27848@lor.watermarkgroup.com>
To: julian@whistle.com
Subject: Re: VM patch..  SMP and SO5.0
Cc: current@FreeBSD.ORG, doconnor@gsoft.com.au
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> who's looked at this.
Tor Egge, he has been very helpful during the development of the code. The
pmap change was a result of discussions with him.

> It looks to me that this is serious stuff....
> spliting the pmap out of the vmspace structure is a big change.
> caertainly a logical move but requires checking..
> 
> I guess it should be refered to the VM cabal.
> 
> I presume that this is to be done in conjunction with the linuxthreads
> (and native threads) code already committed... 
> 
> What exactly is the reason for separating them?
> 
First, pmap is not split out of vmspace structure, it's just a trick to keep
struct kinfo_proc constant size (i.e. independent of NCPU), vmspace_alloc()
has been changed to allocate sizeof(struct vmspace)+sizeof(struct pmap)
amount of space and pmap lives at the bottom half.

> julian
> 

-lq


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