From owner-freebsd-commit  Thu May 25 12:28:34 1995
Return-Path: commit-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id MAA07803
          for commit-outgoing; Thu, 25 May 1995 12:28:34 -0700
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id MAA07790
          for cvs-sys-outgoing; Thu, 25 May 1995 12:28:32 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA07779
          ; Thu, 25 May 1995 12:28:17 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id FAA06296; Fri, 26 May 1995 05:27:48 +1000
Date: Fri, 26 May 1995 05:27:48 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199505251927.FAA06296@godzilla.zeta.org.au>
To: CVS-commiters@freefall.cdrom.com, cvs-sys@freefall.cdrom.com,
        davidg@freefall.cdrom.com
Subject: Re: cvs commit: src/sys/i386/include param.h vmparam.h
Sender: commit-owner@FreeBSD.org
Precedence: bulk

>  Modified:    sys/conf  param.c
>  Log:
>  Made "NMBCLUSTERS" calculation dynamic and fixed bogus use of "NMBCLUSTERS"
>  in machdep.c (it should use the global nmbclusters). Moved the calculation
>  of nmbclusters into conf/param.c (same place where nmbclusters has always
>  been assigned), and made the calculation include an extra amount based
>  on "maxusers". NMBCLUSTERS can still be overrided in the kernel config
      ^^^^^^^^^^
>  file as always, but this change will make that generally unnecessary. This
>  fixes the "bug" reports from people who have misconfigured kernels seeing
>  the network "hang" when the mbuf cluster pool runs out.

Shouldn't it depend on `physmem'?  The GENERIC default of (256 + 10 * 16)
for NMBCLUSTERS allows almost half of memory to be consumed by mbuf clusters
on a 4MB system.

Bruce