> Hi Cristian, > > The way qos works just now should be feasible for dynamic targets. That is > similar functions > to rte_sched_port_enqueue() and rte_sched_port_dequeue() would be > called. The first to > enqueue the mbufs onto the queues the second to dequeue. The qos > structures and scheduler > don't need to be as functionally rich though. I would have thought a simple > pipe with child > nodes should suffice for most. That would allow each tunnel/session to be > shaped and the > queueing and drop logic inherited from what is there just now. > > Thanks, > Alan.
Hi Alan, So just to make sure I get this right: you suggest that tunnels/sessions could simply be mapped as one of the layers under the port hierarchy? Thanks, Cristian
