summaryrefslogtreecommitdiffstats
path: root/firmware
diff options
context:
space:
mode:
authorEric Dumazet <edumazet@google.com>2012-07-14 03:16:27 +0000
committerDavid S. Miller <davem@davemloft.net>2012-07-16 23:08:33 -0700
commit5a308f40bfe27fcfd1db3970afe18b635f23c182 (patch)
tree2d2a596e36a3f6c46405c18982d9f4536b24c204 /firmware
parent7ff65cdea72bdf9af0b9c57cd003211875ca4142 (diff)
downloadblackbird-op-linux-5a308f40bfe27fcfd1db3970afe18b635f23c182.tar.gz
blackbird-op-linux-5a308f40bfe27fcfd1db3970afe18b635f23c182.zip
netem: refine early skb orphaning
netem does an early orphaning of skbs. Doing so breaks TCP Small Queue or any mechanism relying on socket sk_wmem_alloc feedback. Ideally, we should perform this orphaning after the rate module and before the delay module, to mimic what happens on a real link : skb orphaning is indeed normally done at TX completion, before the transit on the link. +-------+ +--------+ +---------------+ +-----------------+ + Qdisc +---> Device +--> TX completion +--> links / hops +-> + + + xmit + + skb orphaning + + propagation + +-------+ +--------+ +---------------+ +-----------------+ < rate limiting > < delay, drops, reorders > If netem is used without delay feature (drops, reorders, rate limiting), then we should avoid early skb orphaning, to keep pressure on sockets as long as packets are still in qdisc queue. Ideally, netem should be refactored to implement delay module as the last stage. Current algorithm merges the two phases (rate limiting + delay) so its not correct. Signed-off-by: Eric Dumazet <edumazet@google.com> Cc: Hagen Paul Pfeifer <hagen@jauu.net> Cc: Mark Gordon <msg@google.com> Cc: Andreas Terzis <aterzis@google.com> Cc: Yuchung Cheng <ycheng@google.com> Acked-by: Stephen Hemminger <shemminger@vyatta.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud