Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!rice!rice!sun-spots-request
From: mark@drd.com (Mark Lawrence)
Newsgroups: comp.sys.sun
Subject: Sun 4 & MMU: further inquiry
Keywords: SunOS
Message-ID: <1990Oct7.234458.8120@rice.edu>
Date: 7 Oct 90 21:30:00 GMT
Sender: sun-spots-request@rice.edu
Organization: Sun-Spots
Lines: 27
Approved: Sun-Spots@rice.edu
Originator: spots@psyche.rice.edu
X-Sun-Spots-Digest: Volume 9, Issue 351, message 4

We're in the middle of analysis of some troubling behaviour from one of
our heavily used sparcstations and in reading this extremely useful and
well written exposition on Sun's implementation and use of the MMU in the
Sun 4 line, some questions have been raised.

For programs dynamically linked (involving shared libraries), are pmegs
allocated for all potential members of the shared library?  Is this the
rationale for savings by linking statically (wherein only the object
referenced is linked in and therefore, pmegs allocated only on an as
needed basis).  I think this is implied, but not stated explicitly.

The point is made that shared text and data between processes still
involves non-shared pmegs (i.e., pmegs mapping the same pages aren't
shared).  Is this also true for multiple processes attaching to System V
shared memory segments?  Does each process have its own set of pmegs
mapping the shared memory? (This could be disastrous in systems with large
shared memory segments).

It is implied that more than 16 megabytes of physical memory is typically
going to be used as a disk cache (rather than for text, data and
what-not).  What's the basis for this claim?  That the virtual memory
pages mapped by the pmegs is only 50% utilized on the average?  This one
escaped me.

Thanks in advance for any illumination.

mark@DRD.Com uunet!apctrc!drd!mark$B!J%^!<%/!!!&%m!<%l%s%9!K(B