From owner-freebsd-stable@FreeBSD.ORG  Tue Mar 27 20:29:06 2007
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id DBE7F16A402
	for <freebsd-stable@freebsd.org>; Tue, 27 Mar 2007 20:29:06 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42])
	by mx1.freebsd.org (Postfix) with ESMTP id A7F6713C45B
	for <freebsd-stable@freebsd.org>; Tue, 27 Mar 2007 20:29:06 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [209.31.154.41])
	by cyrus.watson.org (Postfix) with ESMTP id 38E904760A;
	Tue, 27 Mar 2007 15:03:55 -0500 (EST)
Date: Tue, 27 Mar 2007 21:03:55 +0100 (BST)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: "Marc G. Fournier" <scrappy@hub.org>
In-Reply-To: <442CBD51B75099133C8A26C5@ganymede.hub.org>
Message-ID: <20070327210207.F42335@fledge.watson.org>
References: <442CBD51B75099133C8A26C5@ganymede.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: freebsd-stable@freebsd.org
Subject: Re: socketpair: No buffer space available
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Mar 2007 20:29:06 -0000


On Fri, 23 Mar 2007, Marc G. Fournier wrote:

> I've checked nmbclusters between the two machines, and both are at 25600, 
> but not sure what sysctl to look at for how much is actually used out of 
> that 25600 ...

netstat -mb

nmbclusters directly affects the number of clusters available in the network 
stack; it also indirectly affects the scaling of other settings, such as 
resource limits on the number of sockets.  vmstat -z is also generally useful.

There are a few paths to ENOBUFS in the socket allocation code--one path is if 
you are over-committed on socket buffer resources with respect to the resource 
limits of the user.  Check the output of limits and the socket buffer size 
limit.

Robert N M Watson
Computer Laboratory
University of Cambridge