[LARTC] Re: htb traffic shaping problem

[Bugzilla-Redirect]

I was not aware that segmentation offloading would cause a problem... and I 
do believe it's on.

I think I'll just stuck with the high mtu for the moment then, as I would 
rather have the CPU savings
then more accurate traffic controlling.

Thanks.
-Ryan Power

At 07:48 AM 9/18/2006, Andy Furniss wrote:
>gypsy wrote:
>>Bugzilla-Redirect wrote:
>>
>>>Yes, the output is below:
>>>eth0      Link encap:Ethernet  HWaddr 00:11:09:2A:A6:F6
>>>           inet addr:10.0.0.50  Bcast:10.0.0.255  Mask:255.255.255.0
>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>           RX packets:4244867 errors:0 dropped:0 overruns:0 frame:0
>>>           TX packets:1306632 errors:0 dropped:0 overruns:0 carrier:0
>>>           collisions:0 txqueuelen:1000
>>>           RX bytes:3898905509 (3.6 GiB)  TX bytes:1756030081 (1.6 GiB)
>>>           Interrupt:19
>>
>>Try a "quantum 1514" then; that is correct for an ethernet device with
>>an MTU of 1500.
>>Perhaps reading the source code will give a clue about MPU and MTU? 
>>Frankly, I'd set it to whatever works as long as the rest of the status
>>info looks right and not give a damn that it is huge.
>
>Even if ifconfig says 1500 there have been posts that say you don't get it 
>with gig cards that do segmentation offload unless you can turn it off 
>with ethtool.
>
>Apologies if this has already been said as I don't have all the thread.
>
>Andy.