From owner-freebsd-current Sat Apr 25 11:29:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26366 for freebsd-current-outgoing; Sat, 25 Apr 1998 11:29:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26342 for ; Sat, 25 Apr 1998 11:29:18 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id SAA06256; Sat, 25 Apr 1998 18:29:14 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id UAA10858; Sat, 25 Apr 1998 20:29:13 +0200 (MET DST) Message-ID: <19980425202912.47672@follo.net> Date: Sat, 25 Apr 1998 20:29:12 +0200 From: Eivind Eklund To: Mikhail Teterin , current@FreeBSD.ORG Subject: Re: sysctl from Linux (*envy*) References: <19980425182642.30642@follo.net> <199804251631.MAA08608@rtfm.ziplink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199804251631.MAA08608@rtfm.ziplink.net>; from Mikhail Teterin on Sat, Apr 25, 1998 at 12:31:47PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 25, 1998 at 12:31:47PM -0400, Mikhail Teterin wrote: > Eivind Eklund once stated: > > => Wait. Then, I'm confused. Does linux's overcommit_memory affect kernel > => or libc's malloc? > > =kernel. > = > =It stop the kernel from giving out page-mappings it doesn't have > =backing for. > > Oh, so, strictly speaking, it does not have much to do with malloc > at all, but rather with sbrk(2)? Your initial posting confused me. Just to clarify: My initial posting was a quote from the Linux documentation, with a two-line comment at the end of my own. Basically, what would be nice was a model where one could avoid memory overcommit, both on an entire system and on a process-by-process basis. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message