From: "Singh, Jasvinder" <jasvinder.singh@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
satish amara <satishkamara@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Subject: RE: Fwd: QOS sample example.
Date: Thu, 31 Mar 2022 20:28:00 +0000 [thread overview]
Message-ID: <CY4PR11MB15896DBC9D5FBB226D56AE5AE0E19@CY4PR11MB1589.namprd11.prod.outlook.com> (raw)
In-Reply-To: <10708365.BaYr0rKQ5T@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Thursday, March 31, 2022 8:39 PM
> To: satish amara <satishkamara@gmail.com>
> Cc: users@dpdk.org; Singh, Jasvinder <jasvinder.singh@intel.com>;
> Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Subject: Re: Fwd: QOS sample example.
>
> +Cc QoS scheduler maintainers (see file MAINTAINERS)
>
> 31/03/2022 18:59, satish amara:
> > Hi,
> > I am trying to understand the QOS sample scheduler application code.
> > Trying to understand what is tc_period in the config.
> > 30. QoS Scheduler Sample Application — Data Plane Development Kit
> > 21.05.0 documentation (dpdk.org)
> > <https://doc.dpdk.org/guides-
> 21.05/sample_app_ug/qos_scheduler.html>
> > Is tc_period same as tb_period tb_period Bytes Time period that
> > should elapse since the last credit update in order for the bucket to
> > be awarded tb_credits_per_period worth or credits.
> > Regards,
> > Satish Amara
> >
tc_period and tb_period are different. TC period is related to pipe tc rate limiting mechanism while tb period relates to traffic shaping mechanism (token bucket) implemented at pipe level. tc_period represents the time interval to compute pipe TC credits (bytes). In each interval (tc_period value), credits are initialised to a fixed value. It is configurable parameter and should be carefully selected to avoid deadlock situation which arises when number of pipe TC credits (computed using tc_period) is smaller than the MTU. Please refer https://doc.dpdk.org/guides/prog_guide/qos_framework.html for more details.
prev parent reply other threads:[~2022-03-31 20:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 20:20 satish amara
2022-03-31 16:59 ` Fwd: " satish amara
2022-03-31 19:39 ` Thomas Monjalon
2022-03-31 20:26 ` satish amara
2022-04-01 8:36 ` Singh, Jasvinder
2022-04-01 13:34 ` satish amara
2022-04-06 15:32 ` satish amara
2022-04-06 16:34 ` Singh, Jasvinder
2022-04-06 18:06 ` satish amara
2022-04-07 17:29 ` Singh, Jasvinder
2022-04-11 17:19 ` satish amara
2022-03-31 20:28 ` Singh, Jasvinder [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=CY4PR11MB15896DBC9D5FBB226D56AE5AE0E19@CY4PR11MB1589.namprd11.prod.outlook.com \
--to=jasvinder.singh@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=satishkamara@gmail.com \
--cc=thomas@monjalon.net \
--cc=users@dpdk.org \
/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).