On Wed, May 07, 2008 at 10:50:17AM +0200, Johannes Berg wrote: > > But you're right, it doesn't work this way. I'll have to think of > something. Maybe I can rip out all the retry logic and just store an skb > myself (like dev->gso_skb) and return NETDEV_TX_BUSY when I used that > one and the queue got full because of it. That'll requeue a lot when > non-gso skbs are coming in, but mind you this is not a common case, most > of the time fragmentation will not be enabled and even when it is device > queues should be long enough. Yes keeping your own gso_skb sounds like a good solution. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- 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
