From owner-freebsd-net@FreeBSD.ORG  Wed Aug  3 03:59:47 2005
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
X-Original-To: freebsd-net@freebsd.org
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8D2F316A41F
	for <freebsd-net@freebsd.org>; Wed,  3 Aug 2005 03:59:47 +0000 (GMT)
	(envelope-from silby@silby.com)
Received: from relay01.pair.com (relay01.pair.com [209.68.5.15])
	by mx1.FreeBSD.org (Postfix) with SMTP id 15B0043D45
	for <freebsd-net@freebsd.org>; Wed,  3 Aug 2005 03:59:46 +0000 (GMT)
	(envelope-from silby@silby.com)
Received: (qmail 53564 invoked from network); 3 Aug 2005 03:59:45 -0000
Received: from unknown (HELO localhost) (unknown)
	by unknown with SMTP; 3 Aug 2005 03:59:45 -0000
X-pair-Authenticated: 209.68.2.70
Date: Tue, 2 Aug 2005 22:59:45 -0500 (CDT)
From: Mike Silbersack <silby@silby.com>
To: Dave+Seddon <dave-sender-1932b5@seddon.ca>
In-Reply-To: <1123040973.95445.TMDA@seddon.ca>
Message-ID: <20050802225518.G53516@odysseus.silby.com>
References: <1123040973.95445.TMDA@seddon.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: freebsd-net@freebsd.org
Subject: Re: running out of mbufs?
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2005 03:59:47 -0000


On Wed, 3 Aug 2005, Dave+Seddon wrote:

> For some reason, the 'current' can be WAAAY higher than the 'max' which
> seems very odd.  I've tried putting the 'max' right up to 5 billion, however
> it only goes to 2.1 billion.

Argh, kris beat me to mentioning the statistics problem.

Well, I'd add another potentially useful piece of data:

> net.inet.tcp.sendspace=1024000
> net.inet.tcp.recvspace=1024000
> kern.ipc.maxsockbuf=20480000

I don't think large socket buffers have been tested well, it's possible 
that you're exhausting almost all of your mbufs with just a few 
connections - if you're really stuffing that much data in.  I'd go back to 
the default settings for the above and try again.

Mike "Silby" Silbersack