diff options
| author | Eric Dumazet <[email protected]> | 2012-10-05 06:23:55 +0000 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2012-10-07 00:40:54 -0400 |
| commit | acb600def2110b1310466c0e485c0d26299898ae (patch) | |
| tree | 21036c7d0518601aba70dde0246ac229cd8dfc0c /scripts/stackusage | |
| parent | 809d5fc9bf6589276a12bd4fd611e4c7ff9940c3 (diff) | |
net: remove skb recycling
Over time, skb recycling infrastructure got litle interest and
many bugs. Generic rx path skb allocation is now using page
fragments for efficient GRO / TCP coalescing, and recyling
a tx skb for rx path is not worth the pain.
Last identified bug is that fat skbs can be recycled
and it can endup using high order pages after few iterations.
With help from Maxime Bizon, who pointed out that commit
87151b8689d (net: allow pskb_expand_head() to get maximum tailroom)
introduced this regression for recycled skbs.
Instead of fixing this bug, lets remove skb recycling.
Drivers wanting really hot skbs should use build_skb() anyway,
to allocate/populate sk_buff right before netif_receive_skb()
Signed-off-by: Eric Dumazet <[email protected]>
Cc: Maxime Bizon <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'scripts/stackusage')
0 files changed, 0 insertions, 0 deletions