From owner-freebsd-net@FreeBSD.ORG Fri Jan 14 07:02:09 2011 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 16807106566C for ; Fri, 14 Jan 2011 07:02:09 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from fallbackmx08.syd.optusnet.com.au (fallbackmx08.syd.optusnet.com.au [211.29.132.10]) by mx1.freebsd.org (Postfix) with ESMTP id 231D58FC16 for ; Fri, 14 Jan 2011 07:02:07 +0000 (UTC) Received: from mail04.syd.optusnet.com.au (mail04.syd.optusnet.com.au [211.29.132.185]) by fallbackmx08.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p0E4sgt8000524 for ; Fri, 14 Jan 2011 15:54:42 +1100 Received: from c122-106-165-206.carlnfd1.nsw.optusnet.com.au (c122-106-165-206.carlnfd1.nsw.optusnet.com.au [122.106.165.206]) by mail04.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p0E4sbL9004858 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Jan 2011 15:54:38 +1100 Date: Fri, 14 Jan 2011 15:54:37 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Chuck Swiger In-Reply-To: <0B45B324-A819-4230-BBE3-F8468F2DA88F@mac.com> Message-ID: <20110114154326.E27511@besplex.bde.org> References: <20100729215649.GB2615@icir.org> <20110103210209.GA13091@icir.org> <4D2E66C4.5090607@greatbaysoftware.com> <4D2F20BB.5080204@greatbaysoftware.com> <4D2F71BE.2080801@greatbaysoftware.com> <0B45B324-A819-4230-BBE3-F8468F2DA88F@mac.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Charles Owens , freebsd-net Subject: Re: igb watchdog timeouts 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, 14 Jan 2011 07:02:09 -0000 On Thu, 13 Jan 2011, Chuck Swiger wrote: > On Jan 13, 2011, at 1:42 PM, Charles Owens wrote: >> This is very good news overall, in that we can certainly disable polling for igb. This begs the question, though, as to whether polling is recommended these days at all for em/igb NICs... or even in general. From other conversations we've seen there seems to be some general debate about this. In testing we've done in the past (circa 7.0) there certainly seemed to be benefit to using this feature. What are your thoughts about this? > > To quote an earlier post: > > "Polling mode operation generally performs better when using older 100Mbs ethernet NICs which do not support interrupt mitigation and various capabilities like TSO4; gigabit ethernet NICs are smarter hardware and can generally outperform polling mode." I think "older 100Mbs" means "low-end 100Mbps". Mega-bit-seconds are strange units, and 100Mbps NICs with enough buffers don't benefit much from polling mode. They even avoid dropping the *nix newline character. > Polling is well-suited for dedicated routers, firewalls, and other boxes which have a constant flow of traffic and for which you are looking for well-bounded latency. End-user machines, servers, and the like which have bursty traffic tend to do better using normal NIC operation, especially if you have decent gigabit NICs which support interrupt mitigation and have larger buffers than the old 100Mbs NICs had. I never saw any problem with interrupt mode fxp 100 Mbps NICs. They have enough buffers (128 for each of tx and rx IIRC). The only thing polling mode gave for them was lower latency, but this cost enabling polling in the idle loop, which wastes 100% of at least 1 CPU and some power. Without polling in idle, polling gives very high latency (even worse than low-quality interrupt moderation does). Bruce