From owner-freebsd-current Fri Apr 16 6: 4:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (Postfix) with ESMTP id 4D3BC15409 for ; Fri, 16 Apr 1999 06:04:32 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.9.3/8.9.3) with ESMTP id IAA05979; Fri, 16 Apr 1999 08:50:26 -0400 (EDT) Date: Fri, 16 Apr 1999 08:50:26 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Don Lewis Cc: Chuck Robey , Anthony Kimball , phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: swap-related problems In-Reply-To: <199904152349.QAA11653@salsa.gv.tsc.tdk.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 15 Apr 1999, Don Lewis wrote: > SunOS 4 doesn't do memory overcommit. I get the impression from Vahalia's _UNIX Internals_ that this is true of SunOS 5 as well. > This could be shaved down a bit if SunOS didn't require > (swap > total VM) instead of (swap + RAM > total VM). Again, from my readings it seems that Solaris has the latter policy. Does anyone know if this is true? This would seem to put paid to the idea that overcommit is the only way to go. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message