diff options
author | Eric Dumazet <edumazet@google.com> | 2015-04-30 09:40:40 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2015-05-03 22:17:40 -0400 |
commit | a5d28090405038ca1f40c13f38d6d4285456efee (patch) | |
tree | 0ed77966629db018afd676eaec2e9dee99c79705 /net/netlink/af_netlink.c | |
parent | 6c3c1eb3c35e8856d6dcb01b412316a676f58bbe (diff) | |
download | op-kernel-dev-a5d28090405038ca1f40c13f38d6d4285456efee.zip op-kernel-dev-a5d28090405038ca1f40c13f38d6d4285456efee.tar.gz |
codel: fix maxpacket/mtu confusion
Under presence of TSO/GSO/GRO packets, codel at low rates can be quite
useless. In following example, not a single packet was ever dropped,
while average delay in codel queue is ~100 ms !
qdisc codel 0: parent 1:12 limit 16000p target 5.0ms interval 100.0ms
Sent 134376498 bytes 88797 pkt (dropped 0, overlimits 0 requeues 0)
backlog 13626b 3p requeues 0
count 0 lastcount 0 ldelay 96.9ms drop_next 0us
maxpacket 9084 ecn_mark 0 drop_overlimit 0
This comes from a confusion of what should be the minimal backlog. It is
pretty clear it is not 64KB or whatever max GSO packet ever reached the
qdisc.
codel intent was to use MTU of the device.
After the fix, we finally drop some packets, and rtt/cwnd of my single
TCP flow are meeting our expectations.
qdisc codel 0: parent 1:12 limit 16000p target 5.0ms interval 100.0ms
Sent 102798497 bytes 67912 pkt (dropped 1365, overlimits 0 requeues 0)
backlog 6056b 3p requeues 0
count 1 lastcount 1 ldelay 36.3ms drop_next 0us
maxpacket 10598 ecn_mark 0 drop_overlimit 0
Signed-off-by: Eric Dumazet <edumazet@google.com>
Cc: Kathleen Nichols <nichols@pollere.com>
Cc: Dave Taht <dave.taht@gmail.com>
Cc: Van Jacobson <vanj@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/netlink/af_netlink.c')
0 files changed, 0 insertions, 0 deletions