os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update an FAQ that was never really 2.0 specific to reflect reality.

Browse source
This commit is contained in:
Ceri Davies 2004-11-08 19:22:25 +00:00
parent a2f3dc1df9
commit 163083d41a
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=22870
1 changed files with 4 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -3667,32 +3667,27 @@ quit</programlisting>
<qandaentry>
<question id="panic-kmemmap-too-small">
<para>Why does FreeBSD 2.0 panic with
<para>Why does FreeBSD panic with
<errorname>kmem_map too small!</errorname>?</para>
</question>
<answer>
<note>
<para>The message may also be
<literal>mb_map too small!</literal></para>
</note>
<para>The panic indicates that the system ran out of virtual
memory for network buffers (specifically, mbuf clusters). You
can increase the amount of VM available for mbuf clusters by
adding:</para>
<para><literal>options "NMBCLUSTERS=<replaceable>n</replaceable>"</literal></para>
<para><literal>options NMBCLUSTERS=<replaceable>n</replaceable></literal></para>
<para>to your kernel config file, where
<replaceable>n</replaceable> is a number in the range
512-4096, depending on the number of concurrent TCP
connections you need to support. I would recommend trying
connections you need to support. We recommend trying
2048 - this should get rid of the panic completely. You
can monitor the number of mbuf clusters allocated/in use
on the system with <command>netstat -m</command> (see
&man.netstat.1;). The default value for NMBCLUSTERS is
<literal>512 + MAXUSERS * 16</literal>.</para>
<literal>1024 + MAXUSERS * 64</literal>.</para>
</answer>
</qandaentry>