[dpdk-dev] QoS config variables

[dpdk-dev] QoS config variables

[sreenaath vasudevan]

Hi
Can someone throw some light on the following DPDK QoS config variables?

A) In struct *rte_sched_subport_params* AND *rte_sched_pipe_params*
   1) tb_rate - Is the provisioned rate at which the TB can be filled while
enqueuing OR the TB rate slice allotted to this subport ?
   2) tb_size
   3) tc_rate - Is tc_period the time slice given to each class within a
subport?
   4) tc_period - Does tc_rate represent the bw rate provisioning for that
class?

It would be nice if someone could throw the relationship between the above
parameters and the QoS scheduling algorithm

Thanks !

-- 
regards
sreenaath

Re: [dpdk-dev] QoS config variables

[Dumitrescu, Cristian]

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of sreenaath
> vasudevan
> Sent: Saturday, July 9, 2016 12:23 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] QoS config variables
> 
> Hi
> Can someone throw some light on the following DPDK QoS config variables?
> 
> A) In struct *rte_sched_subport_params* AND *rte_sched_pipe_params*
>    1) tb_rate - Is the provisioned rate at which the TB can be filled while
> enqueuing OR the TB rate slice allotted to this subport ?
>    2) tb_size
>    3) tc_rate - Is tc_period the time slice given to each class within a
> subport?
>    4) tc_period - Does tc_rate represent the bw rate provisioning for that
> class?
> 
> It would be nice if someone could throw the relationship between the above
> parameters and the QoS scheduling algorithm
> 
> Thanks !
> 
> --
> regards
> sreenaath

Hi Sreenaath,

Please check out the QoS documentation: http://www.dpdk.org/doc/guides/prog_guide/qos_framework.html. There is a section on traffic shaping and a section on traffic classes where there parameters are explained in detail. These parameters are also explained by the comments in file "rte_sched.h". Also this Youtube video might be useful to you: https://youtu.be/_PPklkWGugs

TB stands for Token Bucket, TC stands for Traffic Class. The rate parameters are specified in bytes per second. The traffic classes share the subport/pipe bandwidth and are scheduled in strict priority.

Regards,
Cristian