From owner-freebsd-net@FreeBSD.ORG Tue May 2 01:11:45 2006 Return-Path: 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 C88A816A401 for ; Tue, 2 May 2006 01:11:45 +0000 (UTC) (envelope-from tpeixoto@widesoft.com.br) Received: from srv1.netconsultoria.com.br (srv1.netconsultoria.com.br [200.230.201.252]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8776F43D48 for ; Tue, 2 May 2006 01:11:43 +0000 (GMT) (envelope-from tpeixoto@widesoft.com.br) Received: from [192.168.0.1] (mailgw.netconsultoria.com.br [200.230.201.249]) by srv1.netconsultoria.com.br (8.13.6/8.13.3) with ESMTP id k421Bd86061361; Mon, 1 May 2006 22:11:41 -0300 (BRT) (envelope-from tpeixoto@widesoft.com.br) Message-ID: <4456B1E0.9040408@widesoft.com.br> Date: Mon, 01 May 2006 22:12:00 -0300 From: tpeixoto@widesoft.com.br User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: ferdinand.goldmann@jku.at References: <49594.200.230.201.250.1146063341.squirrel@www.widemail.com.br> <444F8E89.2050905@wildcard.net.uk> <56286.200.230.201.250.1146067775.squirrel@www.widemail.com.br> <1146073590.1089.80.camel@sky.mediasat.ro> <59615.200.230.201.250.1146083577.squirrel@www.widemail.com.br> <44506D87.1020808@jku.at> In-Reply-To: <44506D87.1020808@jku.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.1/1431/Sun Apr 30 14:46:15 2006 on srv1.netconsultoria.com.br X-Virus-Status: Clean Cc: freebsd-net@freebsd.org Subject: Re: Packet loss with traffic shaper and routing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 01:11:45 -0000 Ferdinand Goldmann wrote: > tpeixoto@widesoft.com.br wrote: >> Hello. >> >> I did that and compiled the kernel. >> Then I restarted the system and enabled sysctl kern.polling.enable=1 >> >> It seems that it has no effect in the system. Maybe bge driver doesn't >> like polling? > > At least from a quick glance in the polling(4) manpage I cannot see that bge > is among the supported devices. > You're right. I read that too but I found something in Google (http://unix.derkeiler.com/Mailing-Lists/FreeBSD/net/2003-08/0241.html) and wanted to give it a shot. > If you want to use polling, I suppose that you need to enable it via ifconfig, > too: > > polling > If the driver has user-configurable polling(4) support, select > the polling mode on the interface. > It seems to be default when you enable polling, then you can switch it off and on with -polling and polling via ifconfig. > >> At this moment, I'm getting more than 50% interrupts and 20% packets lost. >> I also disabled HT in BIOS and the interrupts are now passing 80% mark. >> Don't know what else to do. Aren't these cards supposed to work at >> 100Mbits or 1Gbit? They are failing with 12Mbits traffic on a 100Mbits >> LAN. Something is wrong and I am having a hard time trying to identify the >> problem. >> >> Thanks for the hints, anything else would be greatly appreciated. > > Several wild guesses from my own experiences here: > - SMP + networking in 5.x does not work too well, using em(4) I experienced > VERY poor performance (only ~5MB/s over a Gbit link) > - Try upgrading to 6.x (as others have already suggested). I experienced all > kind of weird problems with 5.x, and although there is no proof that the > problems were actually related to 5.x, 6.x seems to work better. We did. Now we're running 6.0-RELEASE. > - What's the value of nmbclusters? Have you checked netstat -m? Do you see > memory requests for network memory denied? AFAIK, nmbclusters aren't informed properly on SMP systems. Memory requests are always 0. > - 50% interrupts on such a fast machine is quite high. I currently experience > about 30% interrupt load using two em(4) cards, shaping for about ~2000 > clients on a 3.8GHz Xeon. > Please, take a look in my previous post. I guess the problem lies with IPFW and dummynet. How do you shape your clients? Here we have (for each client): ipfw pipe 1 config bw 512Kbit/s ipfw pipe 2 config bw 512Kbit/s ipfw add pipe 1 ip from any to any mac any 00:11:22:33:44:55 in ipfw add pipe 2 ip from any to any mac 00:11:22:33:44:55 any out > Kind regards Thank you.