From owner-freebsd-net@FreeBSD.ORG Fri Jul 4 09:10:20 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 510EA1065676 for ; Fri, 4 Jul 2008 09:10:20 +0000 (UTC) (envelope-from if@xip.at) Received: from chile.gbit.at (ns1.xip.at [193.239.188.99]) by mx1.freebsd.org (Postfix) with ESMTP id A4F9D8FC17 for ; Fri, 4 Jul 2008 09:10:18 +0000 (UTC) (envelope-from if@xip.at) Received: (qmail 27787 invoked from network); 4 Jul 2008 11:10:17 +0200 Received: from unknown (HELO filebunker.xip.at) (86.59.10.180) by chile.gbit.at with (DHE-RSA-AES256-SHA encrypted) SMTP; 4 Jul 2008 11:10:17 +0200 Date: Fri, 4 Jul 2008 11:10:17 +0200 (CEST) From: Ingo Flaschberger To: Paul In-Reply-To: <486D35A0.4000302@gtcomm.net> Message-ID: References: <4867420D.7090406@gtcomm.net> <20080701010716.GF3898@stlux503.dsto.defence.gov.au> <486986D9.3000607@monkeybrains.net> <48699960.9070100@gtcomm.net> <20080701033117.GH83626@cdnetworks.co.kr> <4869ACFC.5020205@gtcomm.net> <4869B025.9080006@gtcomm.net> <486A7E45.3030902@gtcomm.net> <486A8F24.5010000@gtcomm.net> <486A9A0E.6060308@elischer.org> <486B41D5.3060609@gtcomm.net> <486B4F11.6040906@gtcomm.net> <486BC7F5.5070604@gtcomm.net> <20080703160540.W6369@delplex.bde.org> <486C7F93.7010308@gtcomm.net> <20080703195521.O6973@delplex.bde.org> <486D35A0.4000302@gtcomm.net> User-Agent: Alpine 1.10 (LFD 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: FreeBSD Net Subject: Re: Freebsd IP Forwarding performance (question, and some info) [7-stable, current, em, smp] 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: Fri, 04 Jul 2008 09:10:20 -0000 Dear Paul, > Opteron 2222 UP mode, no polling > > input (em0) output > packets errs bytes packets errs bytes colls > 1071020 0 66403248 2 0 404 0 that looks good. (but seems to be near the limit). > Polling turned on provided better performance on 32 bit, but it gets strange > errors on 64 bit.. > Even at low pps I get small amounts of errors, and high pps same thing.. you > would think that if > it got errors at low pps it would get more errors at high pps but that isn't > the case.. > Polling on: > packets errs bytes packets errs bytes colls > 979736 963 60743636 1 0 226 0 > 991838 496 61493960 1 0 178 0 > 996125 460 61759754 1 0 178 0 > 979381 326 60721626 1 0 178 0 > 1022249 379 63379442 1 0 178 0 > 991468 557 61471020 1 0 178 0 > > lowering pps a little....... > input (em0) output > packets errs bytes packets errs bytes colls > 818688 151 50758660 1 0 226 0 > 837920 179 51951044 1 0 178 0 > 826217 168 51225458 1 0 178 0 > 801017 100 49663058 1 0 178 0 > 761857 287 47235138 1 0 178 0 > > > what could cause this? *) kern.polling.idle_poll enabled? *) kern.polling.user_frac ? *) kern.polling.reg_frac ? *) kern.polling.burst_max ? *) kern.polling.each_burst ? Kind regards, Ingo Flaschberger