On Wed, Jan 28, 2009 at 10:52:13AM +0100, Patrick Ohly wrote: > > Putting that into shinfo should work fine. I thought extending that > structure with information that isn't needed for all packets was as bad > as extending sk_buff itself. If that isn't the case, then extending > shinfo definitely is the simplest solution. Not at all, the sk_buff has its own slab while skb->head uses kmalloc. The latter has loads of free space due to padding for common MTUs such as 1500 or header-only. 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-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
