Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA1679 ; Tue, 23 Feb 93 14:53:14 EST Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!bogus.sura.net!udel!sbcs.sunysb.edu!stark.UUCP!gene From: gene@stark.uucp (Gene Stark) Newsgroups: comp.os.386bsd.misc Subject: Re: A comment on 0.1 + 0.2.1 patchkit's stability Followup-To: comp.os.386bsd.misc Date: 18 Feb 93 17:15:00 Organization: Gene Stark's home system Lines: 23 Message-ID: <GENE.93Feb18171500@stark.stark.uucp> References: <CGD.93Feb17150814@gaia.CS.Berkeley.EDU> NNTP-Posting-Host: stark.uucp In-reply-to: cgd@gaia.CS.Berkeley.EDU's message of 17 Feb 93 15:08:14 Chris Demetriou writes: >under the 0.2.1 patchkit, that'll run at least 3 or 4 times >straight thru (killed it myself, after that; each "make -k" >takes abour 1 hour 50 min on my machine)... I was wondering if others were seeing this type of problem. I have noticed that if a process allocates a large amount of memory so that its RSS is increased, then those page frames seem to become permanently attached to that process, even once they leave the RSS. For example, try starting Emacs and reading in a couple of MB. Then kill the buffer with the stuff in it and wait for things to settle down. You will see Emacs with a low RSS, but active processes do not get the page frames that Emacs once had. I haven't yet studied the VM code, so I didn't try to find this. Also, I wondered if it would be a waste of time, since the word on the net seemed to be that the Jolitz's were revamping the VM code for 0.2. Does anybody already familiar with this part of the system know where to look for this problem? - Gene Stark -- stark@cs.sunysb.edu