We discuss increasing NMBCLUSTERS in the Handbook.
Don't have separate, old instructions in the FAQ, point to the authoritative Handbook instead.
This commit is contained in:
parent
1a44e592e9
commit
dd193d1279
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=24562
1 changed files with 3 additions and 13 deletions
|
@ -3284,19 +3284,9 @@ quit</programlisting>
|
|||
<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>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. 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>1024 + MAXUSERS * 64</literal>.</para>
|
||||
following the instructions in the <ulink
|
||||
url="&url.books.handbook;/configtuning-kernel-limits.html#NMBCLUSTERS">Network
|
||||
Limits</ulink> section of the Handbook.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
Loading…
Reference in a new issue