Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!wb1.cs.cmu.edu!avie
From: avie@wb1.cs.cmu.edu (Avadis Tevanian)
Newsgroups: comp.sys.next
Subject: Re: lpd vsize 16.5 Mb !!!
Keywords: Can somebody explain this?
Message-ID: <6942@pt.cs.cmu.edu>
Date: 11 Nov 89 22:56:43 GMT
References: <1989Nov11.064549.18374@nueces.cactus.org>
Organization: NeXT, Inc.
Lines: 14

In article <1989Nov11.064549.18374@nueces.cactus.org> chari@nueces.cactus.org (Chris Whatley) writes:
>Can somebody explain the ENOURMOUS process sizes on the NeXT. It is
>simply amazing how large things can get. My lpd is 16.5 megs!

Yes, all virtual sizes on a NeXT include the stack size that the process has
asked for.  In the case of lpd, it has a 16 meg stack.  Shared libraries
also add a few hundred K.  In all of these cases, these are virtual sizes.
So they often don't consume any physical resources, or as in the case of
shared libraries, shared resources with other processes.
-- 
Avadis Tevanian, Jr.    (Avie)
Manager, System Software
NeXT, Inc.
avie@NeXT.COM