From owner-freebsd-hackers Wed Nov 6 20:52:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA27015 for hackers-outgoing; Wed, 6 Nov 1996 20:52:22 -0800 (PST) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA27009 for ; Wed, 6 Nov 1996 20:52:17 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id XAA03133; Wed, 6 Nov 1996 23:50:28 -0500 (EST) From: "John S. Dyson" Message-Id: <199611070450.XAA03133@dyson.iquest.net> Subject: Re: frame allocation To: cskim@cslsun10.sogang.ac.kr (Kim Chang Seob) Date: Wed, 6 Nov 1996 23:50:27 -0500 (EST) Cc: freebsd-hackers@freebsd.org, cskim@cslsun10.sogang.ac.kr In-Reply-To: <9611070259.AA18137@cslsun10.sogang.ac.kr> from "Kim Chang Seob" at Nov 7, 96 11:59:08 am Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > hello there . > l have some question about FreeBSD memory management. > i would that know how many memory(physical memory) to provide to each process > to minimize the latter's page fault behavior. > Right now, there isn't a closed form method for finding a processes optimum working set. > > i know, freebsd memory management does not use the working set model > because it lacks accurate infomation about the reference pattern > of a process. > Yes, you are right. > then, in freebsd memory management , how many physical memory is allocated > about requested memory. > allocated all the page allocation size is static, > or allocated all the page allocation size is dynamic. The processes compete for available memory. There are usage statistics gathered (beyond the simple LRU scheme), that help make an estimation of the probability of future use. John