From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: sreenaath vasudevan <sreenaathkv@gmail.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] QoS config variables
Date: Mon, 11 Jul 2016 13:44:46 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D8912647A27686@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAJXCTam-f2DvQMyvgfzg7Zv1Z-jNHu9H0XfhA8m-dH0og8e05A@mail.gmail.com>
> -----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
prev parent reply other threads:[~2016-07-11 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 23:22 sreenaath vasudevan
2016-07-11 13:44 ` Dumitrescu, Cristian [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EB4FA525960D640B5BDFFD6A3D8912647A27686@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=sreenaathkv@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).