--- On Thu, 7/2/09, Larry Baird <lab@gta.com> wrote:There are few applications where dropping buckets of packets is preferable to losing the keyboard. If "livelock is a problem", then your systems are too slow for the task. Livelock can easity be tuned with the "work" parameter. fxp drivers are hard coded to (I think) 6000 ints per second, so its not rocket science to set your tuning parameters to whatever the system can handle before entering a livelock scenario. In reality, interrupt moderation is the equivalent of polling 6000 times per second, in the case of fxp. You wouldn't want to set hz to 6000 as you substantially increase system overhead. Moderation is a much more efficient way of managing your ethernet loads, because the "polls" are only directed at the driver, and if you dont have traffic then you don't need to get polled. Barney _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
| Ingo Molnar | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Roland Dreier | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| Linus Torvalds | Re: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49 |
