Date: Mon, 26 Apr 1999 15:44:56 -0400 (EDT) From: mwlucas@exceptionet.com To: dennis@bbn.com (Dennis Rockwell) Cc: mwlucas@exceptionet.com, jonny@jonny.eng.br, stable@FreeBSD.ORG Subject: Re: nmbclusters=4096 doesn't increase mbufs Message-ID: <199904261944.PAA24025@easeway.com> In-Reply-To: <199904261856.OAA24961@po1.bbn.com> from Dennis Rockwell at "Apr 26, 99 02:56:45 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904261944.PAA24025>