From owner-freebsd-hackers  Tue Jun  1 18: 8:37 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66])
	by hub.freebsd.org (Postfix) with ESMTP id 34C9714DBD
	for <hackers@freebsd.org>; Tue,  1 Jun 1999 18:08:36 -0700 (PDT)
	(envelope-from adsharma@c62443-a.frmt1.sfba.home.com)
Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165])
          by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111)
          with ESMTP
          id <19990602010835.QGYE13307.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com>
          for <hackers@freebsd.org>; Tue, 1 Jun 1999 18:08:35 -0700
Received: (from adsharma@localhost)
	by c62443-a.frmt1.sfba.home.com (8.8.7/8.8.7) id SAA27250
	for hackers@freebsd.org; Tue, 1 Jun 1999 18:08:35 -0700
Date: Tue, 1 Jun 1999 18:08:35 -0700
From: Arun Sharma <adsharma@home.com>
To: hackers@freebsd.org
Subject: pv_table/pv_entry
Message-ID: <19990601180835.A27151@home.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Going through the 4.4 BSD book, I learnt that the purpose of the pv_table
is to be able to locate all the mappings to a given physical page.

However, comparing this to the Linux approach, which chains vm_area_struct
(analogous to vm_map_entry in FreeBSD) together to locate the shared
mappings, it appears to me that the Linux approach is more space efficient.

So why not eliminate pv_table and chain vm_map_entries together to represent
the sharing information ?

	-Arun
 


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