From owner-freebsd-current  Sat Apr 25 09:31:54 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA12745
          for freebsd-current-outgoing; Sat, 25 Apr 1998 09:31:54 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from aldan.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12739
          for <current@freebsd.org>; Sat, 25 Apr 1998 09:31:50 -0700 (PDT)
          (envelope-from mi@rtfm.ziplink.net)
Received: from rtfm.ziplink.net (rtfm [199.232.255.52])
	by aldan.ziplink.net (8.8.8/8.8.7) with ESMTP id QAA16158
	for <current@freebsd.org>; Sat, 25 Apr 1998 16:31:48 GMT
	(envelope-from mi@rtfm.ziplink.net)
Received: (from mi@localhost)
	by rtfm.ziplink.net (8.8.8/8.8.5) id MAA08608
	for current@freebsd.org; Sat, 25 Apr 1998 12:31:47 -0400 (EDT)
From: Mikhail Teterin <mi@aldan.algebra.com>
Message-Id: <199804251631.MAA08608@rtfm.ziplink.net>
Subject: Re: sysctl from Linux (*envy*)
In-Reply-To: <19980425182642.30642@follo.net> from "Eivind Eklund" at "Apr 25, 98 06:26:42 pm"
To: current@FreeBSD.ORG
Date: Sat, 25 Apr 1998 12:31:47 -0400 (EDT)
X-Face: 
	%UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
		 hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
		 y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL39 (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

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.

	-mi

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