On Saturday 15 April 2006 13:17, Hisham Kotry wrote: > I just read David S. Miller's skb redundancy page and in it he seems to > suggest > taking an approach similar to that of BSD's mbufs to reduce the skb's > size. I was going to do some janitor work on the network stack and I > thought that maybe I could start by adding a tag list to the skb > similar to BSD's mbuf tags and change the code to store its private > variables in tags rather than in skb->cb. That should save 40 bytes > per skb and maybe later the tc and nf related variables could go in > tags too. The transition shouldn't be hard for the most part, many > users of skb->cb use macros like FRAG_CB(skb) so I could redefine > those macros to search the tag-list for the appropriate tag and return > its contents. Is this approach acceptable or is there a consensus on > another approach?
Where would that tag list be stored if you want to remove the 40 bytes of ->cb? In general I don't think it will help much even if you find a magic way to store it without using memory @) because ->cb is already private to each layer, so it's only the single 40 bytes which is reused as needed. You seem to think they accumulate which is not the case. Linux 2.0 did something like this, but that was removed for good reasons. Now TCP always clones skbs before sending it out. And optimizing for uncommon cases (not TCP) doesn't seem too useful. -Andi - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
