Date: Sat, 25 Apr 1998 17:51:23 +0200 From: Eivind Eklund <eivind@yes.no> To: Mikhail Teterin <mi@aldan.algebra.com>, current@FreeBSD.ORG Subject: Re: sysctl from Linux (*envy*) Message-ID: <19980425175123.12564@follo.net> In-Reply-To: <199804251332.JAA08229@rtfm.ziplink.net>; from Mikhail Teterin on Sat, Apr 25, 1998 at 09:32:36AM -0400 References: <19980425081621.59822@follo.net> <199804251332.JAA08229@rtfm.ziplink.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980425175123.12564>