From owner-freebsd-hackers Thu Dec 5 11:46: 7 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DA3E37B401 for ; Thu, 5 Dec 2002 11:46:06 -0800 (PST) Received: from web41207.mail.yahoo.com (web41207.mail.yahoo.com [66.218.93.40]) by mx1.FreeBSD.org (Postfix) with SMTP id 121FA43E4A for ; Thu, 5 Dec 2002 11:46:05 -0800 (PST) (envelope-from gathorpe79@yahoo.com) Message-ID: <20021205194604.79160.qmail@web41207.mail.yahoo.com> Received: from [24.114.70.137] by web41207.mail.yahoo.com via HTTP; Thu, 05 Dec 2002 14:46:04 EST Date: Thu, 5 Dec 2002 14:46:04 -0500 (EST) From: Gary Thorpe Subject: Re: maxusers and random system freezes To: Terry Lambert Cc: freebsd-hackers@freebsd.org In-Reply-To: <3DEEB45A.BEDF8EA5@mindspring.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --- Terry Lambert wrote: > Marc Recht wrote: > > Every now and this I hear people saying (mostly you :)) that some > problems > > are KVA related or that the KVA must be increased. This makes me a > bit > > curious, since I've never seen problems like that on Linux. It > sounds for > > me, the not kernel hacker, a bit like something which should be set > at boot > > time (or via sysctl). Have you got some pointers which explain > FreeBSD's > > KVA ? As far as I know, Linux maps all the memory in the machine into the kernel address space, so there is never a problem of it running out while there is free memory (if you run out of it, there isn't any at all left in the machine). It also permits the kernel to directly modify processes' address spaces??? > > I have written documentation for FreeBSD 4.3/4.4. Unfortunately, > everyone keeps substituting activity for action, and hacking away > at the code, so it doesn't sit still long enough to match any > useful documentation; otherwise, I would have published what I > wrote in Pentad Embedded Systems Journal already (example: the > KVA_PAGES stuff came in after FreeBSD 4.3/4.4, and blew out two > paragraphs on what to modify where, and how to calculate the > values to use). > > The best documentation is probably Matt Dillon's article in Daemon > News, the FreeBSD Developer's handbook, or the German guy's article > in English (sorry for not remembering your name), depending on what > part of things you are interested in. > > If you could get people to leave the damn code alone for a while, > I'd be willing to update my article to FreeBSD RELENG_4 (-STABLE), > and publish it. One of the major problems with undocumented code > is that weenies are unwilling to sit down and understand it, so > they rewrite it to understand it, instead, and then you are still > without documentation. > > Documentation that's "almost right" is unbelievably worse than no > documentation at all. > > -- Terry > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message