Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 19 Jan 2002 14:29:02 +0100
From:      Thomas Seck <tmseck@netcologne.de>
To:        stable@FreeBSD.ORG
Subject:   Re: what's vnlru?
Message-ID:  <20020119132902.GB676@laurel.seck.home>
In-Reply-To: <200201190102.g0J12MF37253@apollo.backplane.com>
References:  <200201151618468.SM01176@141.com> <200201160101.g0G117r64693@apollo.backplane.com> <20020116104904.A2800@shikima.mine.nu> <20020116135318.GA427@laurel.seck.home> <200201190102.g0J12MF37253@apollo.backplane.com>

next in thread | previous in thread | raw e-mail | index | archive | help
# Matthew Dillon (dillon@apollo.backplane.com):

[Relnotes description]

>     How about this (see at end).  Unfortunately, I have no idea how to make
>     the doc tree build, typing 'make' in /usr/src/release/doc in -stable
>     doesn't work.

You need to set DOC_PREFIX=/path/to/docprojfiles (usually /usr/doc) in
your environment or /etc/make.conf.

> Index: common/new.sgml
> ===================================================================
> RCS file: /home/ncvs/src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v
> retrieving revision 1.22.2.176
> diff -u -r1.22.2.176 new.sgml
> --- common/new.sgml	14 Jan 2002 16:00:20 -0000	1.22.2.176
> +++ common/new.sgml	19 Jan 2002 00:42:35 -0000
> @@ -149,6 +149,12 @@
>      the timing of samples, in order to avoid synchronization with
>      processes that run periodically.</para>
>  
> +    <para>The kernel now enforces the kern.maxvnodes limit with
> +    a new kernel process called <literal>vnlru</literal>.  The
> +    code typically only needs to do work on large-memory systems
> +    which access lots of tiny files and prevents us from overflowing
> +    the kernel malloc hoppers for vnodes or inodes.</para>
> +
>      <para>If a debugging kernel with modules is being built
>      (i.e. using <literal>makeoptions DEBUG=-g</literal>), the modules
>      will now be built with debugging support as well, for

Hmm, this sounds like one can turn it on or off (which is not the
case, right?) and people then tend to ask how to do it. How about
rewording the second sentence into something like "This code prevents
the system from overflowing the kernel malloc hoppers for vnodes or
inodes when a large number of small files are accessed on large memory
systems"? (Please apply grammar fixes as needed, apologies for my german
high-school english).

     --Thomas

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020119132902.GB676>