From owner-freebsd-current Wed Mar 13 10:14:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA14165 for current-outgoing; Wed, 13 Mar 1996 10:14:34 -0800 (PST) Received: (from dyson@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA14159 Wed, 13 Mar 1996 10:14:33 -0800 (PST) From: John Dyson Message-Id: <199603131814.KAA14159@freefall.freebsd.org> Subject: Re: Questions for current hackers.. To: jehamby@lightside.com (Jake Hamby) Date: Wed, 13 Mar 1996 10:14:32 -0800 (PST) Cc: current@FreeBSD.org In-Reply-To: from "Jake Hamby" at Mar 13, 96 08:41:59 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > 2) Over the last several months, various changes have been made to the VM > code that have, at times, left -current in a rather unstable state (Sig > 11's and whatnot). A number of people experienced problems just recently, > with the 3/3 SNAP and kernels built around this time. What exactly is the > reasoning behind all of these VM changes, are they to boost performance, > reduce swap utilization, or what? > Performance boost, code cleanup, decrease memory usage under certain circumstances (forks), etc... Remember, -current != -stable :-). The changes were tested for a few weeks, and it is impossible to simulate all usages of the system. There are more changes going in after the next SNAP. John