Date: Fri, 24 Apr 1998 19:07:00 -0500 (EST) From: "John S. Dyson" <toor@dyson.iquest.net> To: eivind@yes.no (Eivind Eklund) Cc: current@FreeBSD.ORG Subject: Re: sysctl from Linux (*envy*) Message-ID: <199804250007.TAA03846@dyson.iquest.net> In-Reply-To: <19980424224346.35645@follo.net> from Eivind Eklund at "Apr 24, 98 10:43:46 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > overcommit_memory: > > This file contains only one value. The following algorithm > is used to decide if there's enough memory. If the value > of overcommit_memory > 0, then there's always enough > memory :-). This is a useful feature, since programs often > malloc() huge amounts of memory 'just in case', while they > only use a small part of it. Leaving this value at 0 will > lead to the failure of such a huge malloc(), when in fact > the system has enough memory for the program to run... > On the other hand, enabling this feature can cause you to > run out of memory and thrash the system to death, so large > and/or important servers will want to set this value to 0. > > > > This supposedly also handles things like fork() etc. Linux shouldn't > have any server-directed features FreeBSD doesn't! > Agreed. I have been working on it, until I had my programming breakdown early this week. Look for it soon. I have the accounting in my kernel (but it is broken right now.) I haven't implemented the limit yet. John 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?199804250007.TAA03846>