On Wed, 2012-04-11 at 08:30 +0200, Eric Dumazet wrote: > Marc Merlin reported many order-1 allocations failures in TX path on its > wireless setup, that dont make any sense with MTU=1500 network, and non > SG capable hardware. > > After investigation, it turns out TCP uses sk_stream_alloc_skb() and > used as a convention skb_tailroom(skb) to know how many bytes of data > payload could be put in this skb (for non SG capable devices) > ... > > Reported-by: Marc MERLIN <marc@xxxxxxxxxxx> > Tested-by: Marc MERLIN <marc@xxxxxxxxxxx> > Signed-off-by: Eric Dumazet <eric.dumazet@xxxxxxxxx> David, I forgot to say this should be backported to 3.2 & 3.3 commit 87fb4b7b533073 (net: more accurate skb truesize) did the placement of skb_shared_info at the end of skb head, so sk_stream_alloc_skb() had to reserve more room so that tailroom stayed at MSS -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
