From: jamal <[EMAIL PROTECTED]> Date: Wed, 07 Dec 2005 14:44:53 -0500
> so thats conclusion one. Copybreak oughta be off by default. People > who think it is useful can turn it on. I disagree, the socket buffering side effects of non-copybreak are severe especially during loss handling where it is important that the "buffer size / real data length" ratio is small. Otherwise, we go over the socket buffer limits quickly during a loss event and TCP spends all of this time copying data around to get the "buffer size / real data length" ratios in check. Furthermore, as a default, the loss in performance is relatively small for the router workloads with copybreak enabled and we can add a switch to turn it off and tweak it's value via ethtool. Ok? :-) - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
