home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!deimos.cis.ksu.edu!mccall!infopiz!cmkrnl!jeh
- From: jeh@cmkrnl.com
- Newsgroups: vmsnet.internals
- Subject: Re: global vs. private pages on the FPL (was: VMS Tuning)
- Message-ID: <1992Aug26.112311.647@cmkrnl.com>
- Date: 26 Aug 92 18:23:11 GMT
- References: <06D94B115A9F822B58@MAX.U.WASHINGTON.EDU> <1992Aug25.122200.644@cmkrnl.com>
- Organization: Kernel Mode Consulting, San Diego, CA
- Lines: 26
-
- In article <1992Aug25.122200.644@cmkrnl.com>, jeh@cmkrnl.com writes:
- > Pages are put at the top of the free page list when they are released at
- > image rundown, or, more generally, by deletion of the virtual address space
- > that describes them. In the case of global pages, this happens when no more
- > processes are mapped to the relevant global section. So, yes, what you call
- > "system owned" pages *can* be released to the top of the FPL. It all depends
- > on why the pages are being released -- working set replacement (to make room
- > for a newly-faulted-in page when the working set is full) or deletion of the
- > virtual address space.
-
- Oops. Turns out that global pages are normally released to the end of the FPL
- when the last image mapped to them runs down. (Another process might want
- them soon, so VMS tries to keep them around for a while.) But they are
- released to the top of the FPL if the global section that describes them is
- also deleted.
-
- > Lots of well-known "authorities" on VMS get these details wrong, repeatedly, in
- > print. Professional courtesy prevents me from naming names.
-
- Sigh!
-
- --- Jamie Hanrahan, Kernel Mode Consulting, San Diego CA
- uucp 'g' protocol guru and release coordinator, VMSnet (DECUS uucp) W.G., and
- Chair, VMS Programming and Internals Working Group, U.S. DECUS VAX Systems SIG
- Internet: jeh@cmkrnl.com, hanrahan@eisner.decus.org, or jeh@crash.cts.com
- Uucp: ...{crash,eisner,uunet}!cmkrnl!jeh
-