From owner-freebsd-current Tue Apr 28 21:04:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04153 for freebsd-current-outgoing; Tue, 28 Apr 1998 21:04:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04140 for ; Tue, 28 Apr 1998 21:04:09 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id XAA00316 for current@freebsd.org; Tue, 28 Apr 1998 23:04:01 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199804290404.XAA00316@dyson.iquest.net> Subject: Warning, but good VM news To: current@FreeBSD.ORG Date: Tue, 28 Apr 1998 23:04:00 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am about to commit some VM improvements that should get rid of some of the pseudo-memory leaks that some people have been seeing. I was spurred on by Chuck Cranor from NetBSD, regarding some criticisms of the MACH VM code. The problems aren't impossible to solve, and these changes to be committed in about 1Hr, should mitigate most of them. Note that I would ask that you torture your -current system(s) before deploying after the changes. Please walk carefully, but the new code should really cause many problems. It is not in its (:-)) final form yet, but should be functional. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message