From owner-freebsd-current  Mon May  7 11: 7:40 2001
Delivered-To: freebsd-current@freebsd.org
Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67])
	by hub.freebsd.org (Postfix) with ESMTP id A349037B423
	for <freebsd-current@FreeBSD.ORG>; Mon,  7 May 2001 11:07:31 -0700 (PDT)
	(envelope-from dillon@earth.backplane.com)
Received: (from dillon@localhost)
	by earth.backplane.com (8.11.2/8.11.2) id f47I73l62730;
	Mon, 7 May 2001 11:07:03 -0700 (PDT)
	(envelope-from dillon)
Date: Mon, 7 May 2001 11:07:03 -0700 (PDT)
From: Matt Dillon <dillon@earth.backplane.com>
Message-Id: <200105071807.f47I73l62730@earth.backplane.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Sheldon Hearn <sheldonh@uunet.co.za>,
	Kris Kennaway <kris@obsecurity.org>,
	Dennis Glatting <dennis.glatting@software-munitions.com>,
	<freebsd-stable@frebsd.org>, <freebsd-current@FreeBSD.ORG>
Subject: Re: pgm to kill 4.3 via vm 
References:  <Pine.LNX.4.33.0105071455200.18102-100000@duckman.distro.conectiva>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

:Indeed, this is an interesting area. In the process of
:researching how to best implement this for Linux I have
:found various reasons why both FreeBSD's and NetBSD's
:load control systems cannot work in various realistic
:scenarios.

    It's not a load control system.  It's an emergency measure, period.  A
    load control system is something like... oh, the 20 second enforced swap
    out that can be triggered when the VM system is under extreme memory
    pressure.  Load control is a completely different issue from swap
    exhaustion.  The two are entirely unrelated to each other.

					-Matt


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message