From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
Date: Tue, 06 May 2008 01:17:14 +0200
> Also, should there be some sort of timer that resets the rx_alloc_extra
> again so that when you bridge it once with p54 (needs heaps of headroom)
> you don't suffer forever?
We're talking about, what, up to 128 bytes or something like that?
If you're bridging over your wireless device you've already invested
in assuming those kinds of costs.
I don't think this aspect is really worth worrying about. The current
behavior is so much incredibly worse. :-)
> > @@ -255,11 +255,12 @@ struct sk_buff *__netdev_alloc_skb(struct net_device *dev,
> > unsigned int length, gfp_t gfp_mask)
> > {
> > int node = dev->dev.parent ? dev_to_node(dev->dev.parent) : -1;
> > + unsigned int extra = dev->rx_alloc_extra + NET_SKB_PAD;
> > struct sk_buff *skb;
> >
> > - skb = __alloc_skb(length + NET_SKB_PAD, gfp_mask, 0, node);
> > + skb = __alloc_skb(length + extra, gfp_mask, 0, node);
> > if (likely(skb)) {
> > - skb_reserve(skb, NET_SKB_PAD);
> > + skb_reserve(skb, extra);
>
> Doesn't that break alignment though?
Good catch, we'll have to align the rx_alloc_extra to some modulus or
similar. Ideally, at the spot where rx_alloc_extra is set instead
of here.
--
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
