From owner-freebsd-current  Mon Jun 26 15:25:41 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id PAA09631
          for current-outgoing; Mon, 26 Jun 1995 15:25:41 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA09621
          for <freebsd-current@freefall.cdrom.com>; Mon, 26 Jun 1995 15:25:38 -0700
Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id PAA05572; Mon, 26 Jun 1995 15:25:33 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id PAA17617; Mon, 26 Jun 1995 15:26:00 -0700
Message-Id: <199506262226.PAA17617@corbin.Root.COM>
To: John Capo <jc@irbs.com>
cc: tom@uniserve.com (Tom Samplonius),
        freebsd-current@freefall.cdrom.com (freebsd-current)
Subject: Re: mb_map full with GATEWAY and maxusers 64! 
In-reply-to: Your message of "Mon, 26 Jun 95 15:35:36 EDT."
             <199506261935.PAA12035@irbs.irbs.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Mon, 26 Jun 1995 15:25:58 -0700
Sender: current-owner@FreeBSD.org
Precedence: bulk

>I agree with Tom here.  But, it seems to me that there is an
>underlying problem of some sort.  Why do I have to allow for 4Megs
>of mbuf clusters to service some unknown transient event.  Once
>this memory is in the mbuf map, its there forever.

   Well, the usage is a function of the number of TCP connections. If you do a
"netstat" and find a whole pile of connections (even ones in a closing state),
then this explains it. This can easily happen to people using HTTP.

>Is this a valid way to examine a running kernel?  It appears that
>it is.

   I suppose, but "netstat -m" should provide you with enough information.

-DG