Re: Bad results for rate limiting with bidirectional traffic

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

 



> The guess is wrong, cbq counts byte rates, of course.

Uhh, thanks.

> 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.

How can I distinguish just ACK's?

---
Meelis Roos             e-mail: mroos@ut.ee
                        www:    http://www.cs.ut.ee/~mroos/

-
: 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