From owner-freebsd-stable  Mon Apr 26 12:55: 4 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from easeway.com (ns1.easeway.com [209.69.39.1])
	by hub.freebsd.org (Postfix) with ESMTP id 4D2C415352
	for <stable@FreeBSD.ORG>; Mon, 26 Apr 1999 12:54:58 -0700 (PDT)
	(envelope-from mwlucas@easeway.com)
Received: (from mwlucas@localhost)
	by easeway.com (8.8.8/8.8.5) id PAA24025;
	Mon, 26 Apr 1999 15:44:57 -0400 (EDT)
Message-Id: <199904261944.PAA24025@easeway.com>
Subject: Re: nmbclusters=4096 doesn't increase mbufs
In-Reply-To: <199904261856.OAA24961@po1.bbn.com> from Dennis Rockwell at "Apr 26, 99 02:56:45 pm"
To: dennis@bbn.com (Dennis Rockwell)
Date: Mon, 26 Apr 1999 15:44:56 -0400 (EDT)
Cc: mwlucas@exceptionet.com, jonny@jonny.eng.br, stable@FreeBSD.ORG
From: mwlucas@exceptionet.com
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

The machine in question frequently slows to a crawl.  The IPFilter people
have specifically cited mbuf starvation as a classic cause of this
symptom.

How can I determine how many mbufs a FreeBSD machine has at a given time?

If 132 is the current high-water mark, and we actually have 4096
available, I'll shut up and go away happy.

==ml

> In most Unix kernels I've diddled with (and I can't say for
> sure about FreeBSD), and cluster count numbers (here as
> 128/132) should be labelled "in use" and "allocated".  The
> limit for "allocated" (4096) is not given by netstat -m in
> most cases, since that's not kept in the tables that netstat
> -m examines.
> 
> In other words, the 132 is simply the current high-water
> mark for cluster allocations.


-- 
Michael Lucas			|
Exceptionet, Inc.		|	www.exceptionet.com
"Exceptional Networking"	|


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