I'm beginning to think that where we store the skb_shared_info() is a weakness of the SKB design.
It makes it more difficult to have local memory management schemes and to just wrap SKB's around arbitrary pieces of data. The e1000 issue is just one example of this, another would be any attempt to consolidate the TCP retransmit queue data management. How to deal with data refcounting and destruction is the primary matter to deal with if we want to move skb_shared_info() somewhere else. But that can probably be handled with a data destructor callback of some sort which we're always talking about adding anyways. :) - 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
