From owner-freebsd-current Sat Apr 25 08:51:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08566 for freebsd-current-outgoing; Sat, 25 Apr 1998 08:51:36 -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 IAA08557 for ; Sat, 25 Apr 1998 08:51:33 -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 PAA03077; Sat, 25 Apr 1998 15:51:25 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id RAA10475; Sat, 25 Apr 1998 17:51:24 +0200 (MET DST) Message-ID: <19980425175123.12564@follo.net> Date: Sat, 25 Apr 1998 17:51:23 +0200 From: Eivind Eklund To: Mikhail Teterin , current@FreeBSD.ORG Subject: Re: sysctl from Linux (*envy*) References: <19980425081621.59822@follo.net> <199804251332.JAA08229@rtfm.ziplink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199804251332.JAA08229@rtfm.ziplink.net>; from Mikhail Teterin on Sat, Apr 25, 1998 at 09:32:36AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 25, 1998 at 09:32:36AM -0400, Mikhail Teterin wrote: > Eivind Eklund once stated: > > => =overcommit_memory: > => = > => =This file contains only one value. > => > => I prefer the value of /etc/malloc.conf link and the corresponding > => environment variables. > = > =That doesn't solve this problem - it doesn't handle e.g. fork. > > Does not currently, but this, IMHO, is where to add it. And then, > the man page for overcommit_memory (very short) will point to the > malloc's man page, where all the possible values will be described. This is not a technically feasible place to add _kernel_ control variables. /etc/malloc.conf controls the behvaiour of a part of libc - it should _not_ have impact for the kernel operation (POLA), and it would also be expensive to read this for each invocation of fork() (this could be solved through notification, but notification is not yet in the FreeBSD kernel). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message