Hello, On 7/28/06, Patrick McHardy <kaber@xxxxxxxxx> wrote:
Right, the "problem" is related to TCP segmentation offloading (or GSO in current kernels). The card gets large chunks of data and is responsible for creating MTU-sized packets, which essentially means qdiscs get to see those large chunks of data. You can disable TSO using ethtool (but it will cost you performance) or configure your qdisc appropriately.
Thanks a lot. It was exactly that. I turned the tso off and HTB is working properly. How can I know the largest chunk of data the kernel sends to the card, so that I can configure qdisc appropriately? In the last post, Jake Altchill recommended using mtu 16500 in the qdiscs, but I'm not sure whether that's a real or just a big number. Regards. -- Marlon _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
