tree 5d14f74159121ee2474fae0f1f22c9438ed94065
parent 8e6e596b06db164ece4c0f0225b72ba661d53d6c
author Eric Dumazet <edumazet@google.com> 1478545947 -0800
committer David S. Miller <davem@davemloft.net> 1478735334 -0500

net-gro: avoid reorders

Receiving a GSO packet in dev_gro_receive() is not uncommon
in stacked devices, or devices partially implementing LRO/GRO
like bnx2x. GRO is implementing the aggregation the device
was not able to do itself.

Current code causes reorders, like in following case :

For a given flow where sender sent 3 packets P1,P2,P3,P4

Receiver might receive P1 as a single packet, stored in GRO engine.

Then P2-P4 are received as a single GSO packet, immediately given to
upper stack, while P1 is held in GRO engine.

This patch will make sure P1 is given to upper stack, then P2-P4
immediately after.

Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>