Browse Prior Art Database

Isolate Frame Manager from the Virtual Memory Manager

IP.com Disclosure Number: IPCOM000115679D
Original Publication Date: 1995-Jun-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 2 page(s) / 32K

Publishing Venue

IBM

Related People

Shapiro, B: AUTHOR [+2]

Abstract

Separating page frame management from the virtual memory system helps portability and tunability.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 100% of the total text.

Isolate Frame Manager from the Virtual Memory Manager

      Separating page frame management from the virtual memory system
helps portability and tunability.

      A Page Frame Manager's function is to manage page allocation.
It keeps track of the free frames and does page stealing.

      The page Frame Manager is separated from the Virtual Memory
Manager and has its own format interface.  Resident pages are
associated with a paging object (and, hence, with a pager).  The
interface consists of various function calls (to, for example, insert
a free frame on the free list or on an objects resident page list),
which take page frames and/or paging objects as parameters.

      By making the Page Frame Manager a separate component, it can
be used as the primary buffering mechanism for ALL files--temporary
working storage files as well as file system files.  As a separate
component, it can easily be tuned independently and ported to other
systems.  The interface is simple and easy to use.

      In the UNIX* Operating System, Mach Operating System and AIX**
version 3, page frame management is integrated with virtual memory
management.
   *  Trademark of Novell Corp.
  **  Trademark of IBM Corp.