[Cerowrt-devel] [Cake] openwrt build with latest cake and other qdiscs
dave.taht at gmail.com
Thu May 14 09:48:49 EDT 2015
On Thu, May 14, 2015 at 6:35 AM, Alan Jenkins
<alan.christopher.jenkins at gmail.com> wrote:
> On 14/05/15 14:14, Jonathan Morton wrote:
>>>> This implies that adding GRO peeling to cake might be a worthwhile
I saw 64k sized packets out of the GRO implementation on the mvneta
driver on the linksys 1900ac.
I think this explains a lot about the performance of the qos system on
that box's native firmware, dropping
big chunks and not fq-ing well.
disabling GRO packets on all interfaces is hard to get right, and has
a significant cost if
you have more than one interface (as in the edgerouters).
So yes, peeling.
Also I note that at the higher inbound rates (e.g. 100mbit+) policing
is not horrible.
let me discuss that in a different mail.
>>>> - Jonathan Morton
>>> Ah, not on my account, it seems.
>>> # tc -stat qdisc |grep maxpacket
>>> maxpacket 590 drop_overlimit 0 new_flow_count 1 ecn_mark 0
>>> maxpacket 256 drop_overlimit 0 new_flow_count 0 ecn_mark 0
>>> maxpacket 1696 drop_overlimit 0 new_flow_count 305 ecn_mark 0
>>> maxpacket 1749 drop_overlimit 0 new_flow_count 274 ecn_mark 0
>> A maxpacket of 1749 *does* imply that GRO or GSO is in use. Otherwise I’d
>> expect to see 1514 or less.
>> - Jonathan Morton
> Look at the exact difference between the two maxpackets :p (without getting
> into why it's there). It must be including all the ATM estimation. For GSO
> we should be seeing 2x or more... not a multiplier of 53/48.
> Cerowrt-devel mailing list
> Cerowrt-devel at lists.bufferbloat.net
Open Networking needs **Open Source Hardware**
More information about the Cerowrt-devel