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
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Reply via email to