Christopher Snook <csnook@redhat.com> writes:The nagle delay you're seeing is really the delayed ack delay which is variable on Linux (unlike a lot of other stacks). Unfortunately due to the way delayed ack works on other stacks (especially traditional BSD with its fixed 200ms delay) there are nasty interactions with that. Making it too short could lead to a lot more packets even in non nagle situations. Ok in theory you could split the two, but that would likely have other issues and also make nagle be a lot less useful. -Andi -- ak@linux.intel.com -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Linus Torvalds | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Eric Paris | [RFC 0/5] [TALPA] Intro to a linux interface for on access scanning |
| Ingo Molnar | Re: [patch 00/13] Syslets, "Threadlets", generic AIO support, v3 |
git: | |
| Gerrit Renker | [PATCH 18/37] dccp: Support for Mandatory options |
| David Miller | [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Andrew Morton | Re: [BUG] New Kernel Bugs |
