Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice!sun-spots-request
From: dilworth@presto.ig.com (Mike Dilworth)
Newsgroups: comp.sys.sun
Subject: Memory
Keywords: Miscellaneous
Message-ID: <347@brchh104.bnr.ca>
Date: 20 Nov 90 18:00:01 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 20
Approved: Sun-Spots@rice.edu
X-Original-Date: 6 Nov 90 22:44:34 GMT
X-Sun-Spots-Digest: Volume 9, Issue 371, message 15
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

I am in the process of building a program which can allocate large amounts
of memory (>32 megs).   The problem,  It will be running on small machines
(<32 megs {surprise}).  But that's ok, the kernel of this program can
compress it's memory image. 

What I am looking for is a method to monitor the total amount of memory
allocated (both real and virtual), and the total amount of memory avail
(both real and virtual),  system wide. 

When my program is quite fat and the system resources are thin the kernel
would begin compressing itself.  Thus allowing the user to run both my
program and emacs etc...

I have looked at the source code to a bunch of "perfmeters" but none seem
to provide the correct info.  kmem seems to have the info but I can't
locate it.  Can you?

Michael Dilworth                     /.         dilworth@presto.ig.com
Clove Productions Ltd.              .\                  
Santa Cruz Ca.                       /          Save a life, Teabag a Sponge