Re: Bad results for rate limiting with bidirectional traffic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello!

> My guess: You give the system average packet size so it can actually work on
> packet counter level.

The guess is wrong, cbq counts byte rates, of course.
Average packet size contributes only to second order effects sort of bursts. 


Probably, he configured shaping allowing too large latency
and ACKs are messed with data of another connection, randomly delayed
and, maybe, even dropped. Also, most likely, this triggers bugs in rtt
estimation in linux-2.2. One way is to select sane latency bounds,
another is to classify ACKs to separate class.


> Can anyone explain what is going on? 

No. Such questions REQUIRE tcpdumps.

Alexey
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux