[dpdk-dev] Increasing the number of traffic classes

["Sridhar.V.Iyer" <sridhariyer@versa-networks.com>]

Hi,

I know that this topic have been covered in the youtube video and mailing list (http://dpdk.org/ml/archives/dev/2015-June/018875.html <http://dpdk.org/ml/archives/dev/2015-June/018875.html>) in the past. The solution suggested was to have 4 queues per traffic classes and each of those could be construed as a sub traffic class (and that a WRR or 1:4 will ensure a strict priority order).

However, this solution doesn’t take into account the fact that we can only have 4 schedulers (for the main traffic classes). If I’m not changing the total number of queues, i.e. I’m aiming for 8 TC with 2 queues each or 16 TC with 1 queue each (in which case WRR logic can be optimized out), how much effort would it be to have a configurable (compile time) set of traffic classes? The changes would be largely limited to rte_sched.c right?

I’m trying to make these changes to dpdk lib, but am hitting issues in grinder updates. Any pointers/help would be great.

Regards,

Sridhar V Iyer
Versa Networks
315-560-4566 <callto:3155604566> (mobile)
408-385-7627 <callto:4083857627> (desk)
sridhariyer@versa-networks.com
 <mailto:sridhariyer@versa-networks.com>











 <http://www.versa-networks.com/>









 <http://www.versa-networks.com/>