From owner-freebsd-net@FreeBSD.ORG  Fri Apr 30 21:02:18 2010
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id ADC41106566C
	for <freebsd-net@FreeBSD.ORG>; Fri, 30 Apr 2010 21:02:18 +0000 (UTC)
	(envelope-from sobomax@sippysoft.com)
Received: from sippysoft.com (gk1.360sip.com [72.236.70.240])
	by mx1.freebsd.org (Postfix) with ESMTP id 5D7118FC1A
	for <freebsd-net@FreeBSD.ORG>; Fri, 30 Apr 2010 21:02:18 +0000 (UTC)
Received: from [192.168.1.38] (S0106005004e13421.vs.shawcable.net
	[70.71.175.212]) (authenticated bits=0)
	by sippysoft.com (8.14.3/8.14.3) with ESMTP id o3UKN1gC093955
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 30 Apr 2010 13:23:02 -0700 (PDT)
	(envelope-from sobomax@sippysoft.com)
Message-ID: <4BDB3C31.4050709@sippysoft.com>
Date: Fri, 30 Apr 2010 13:23:13 -0700
From: Maxim Sobolev <sobomax@sippysoft.com>
Organization: Sippy Software
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "current@freebsd.org" <current@FreeBSD.ORG>, freebsd-net@FreeBSD.ORG
Content-Type: text/plain; charset=KOI8-U; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 
Subject: Making IFQ_MAXLEN tunable
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: Fri, 30 Apr 2010 21:02:18 -0000

Hi,

Many network drivers in the FreeBSD kernel use the IFQ_MAXLEN value to 
set length of the outgoing packets queue. The default value for that 
parameter is only 50, which is pretty low especially for the cases when 
the system handles lot of small packets and can cause ENOBUFS in 
applications under the load. The following patch makes IFQ_MAXLEN a 
tunable. I am also tempted to bump the default value for IFQ_MAXLEN 
10-fold, but would like to hear what do people think about it first.

http://sobomax.sippysoft.com/IFQ_MAXLEN.diff

-Maxim