From owner-freebsd-current  Sun Dec  7 16:44:41 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA08520
          for current-outgoing; Sun, 7 Dec 1997 16:44:41 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from ns1.yes.no (ns1.yes.no [195.119.24.10])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA08491;
          Sun, 7 Dec 1997 16:44:31 -0800 (PST)
          (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 AAA07989;
	Mon, 8 Dec 1997 00:44:28 GMT
Received: (from eivind@localhost)
	by bitbox.follo.net (8.8.6/8.8.6) id BAA10173;
	Mon, 8 Dec 1997 01:44:00 +0100 (MET)
To: dyson@FreeBSD.ORG
Cc: current@FreeBSD.ORG
Subject: Re: VM system info
References: <199712071829.NAA03407@dyson.iquest.net>
From: Eivind Eklund <perhaps@yes.no>
Date: 08 Dec 1997 01:43:59 +0100
In-Reply-To: "John S. Dyson"'s message of Sun, 7 Dec 1997 13:29:42 -0500 (EST)
Message-ID: <867m9gpsts.fsf@bitbox.follo.net>
Lines: 35
X-Mailer: Gnus v5.4.52/XEmacs 20.2
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

"John S. Dyson" <dyson@FreeBSD.ORG> writes:

> Joao Carlos Mendes Luis said:
> > #define quoting(John S. Dyson)
> > // Notes on VM tunables:
> > // 
> > // I have recently added some interesting VM tunables.  Since it would
> > // be nice if people other than me (or those who requested them) could
> > // use the features, I thought it would be nice to pass this info on:
> > 
> > Is there any place or URL where we can get this information always
> > updated ?  It's a pretty good form of documentation I've always
> > wanted to know.
> >
> Nope.  Unfortunately, the source code is the only place for it (by
> inference.)  The VFS sysctls also deserve some documentation.
> 
> > 
> > Maybe it deserves a handbook section ?
> > 
> Maybe, but it is extremely kernel version dependent, and would require
> some commitment to maintain.  Otherwise, the info could be confusing.

I'm going to be extremely politically incorrect here:

I want this info in the kernel.  At the very least, I want
documentation as a part of the SYSCTL_*() macro parameters, unused but 
available as a (mandatory) part of the source - better would be as a
part of the kernel that can be compiled away by setting a kernel
option (e.g. NO_SYSCTL_DOCS).

I don't care about the amount of hardwired memory it wastes - memory
is extremely cheap, people's time aren't.

Eivind.