> The qdiscs would ideally exist at the layer 2 / layer 3 boundary like > existing qdiscs, but the problem is getting the scheduling parameters down > that far. Perhaps a transport protocol could create a tagged route entry > with the appropriate parameters, the routing layer could assign skbs to it > by flow tag, and the qdisc could refer to the route entry and some sort of > skb sequence number to derive the appropriate scheduling information. > I'm trying to do something a little bit different but I send expiry time down through the msg structure with dccp_sendmsg and then check it in dccp_write_xmit and discard there. This is trivial to implement (even I managed it!) but I think you are wanting to do it down one layer.
If you want further info or sourcecode then feel free to take this discussion further with me offline... Ian -- Ian McDonald Web: http://wand.net.nz/~iam4 Blog: http://imcdnzl.blogspot.com WAND Network Research Group Department of Computer Science University of Waikato New Zealand - 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
