From: satish amara <satishkamara@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: users@dpdk.org, jasvinder.singh@intel.com, cristian.dumitrescu@intel.com
Subject: Re: Fwd: QOS sample example.
Date: Thu, 31 Mar 2022 16:26:53 -0400 [thread overview]
Message-ID: <CAGSLe_FK6wfFYSoOsxFe7mbDxs72CNJSORgV14xsxGH+OKw07g@mail.gmail.com> (raw)
In-Reply-To: <10708365.BaYr0rKQ5T@thomas>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
Thanks, Thomas for forwarding this to the group.
I have one more question. Does DPDK QOS uses any internal threads/timers
for the token bucket implementation?. The token
buckets can be implemented in different ways. When are the tokens are
filled, I see there is tb_period?
It looks like the tokens are filled when the HQOS thread is trying to find
the next active pipe?
Regards,
Satish Amara
On Thu, Mar 31, 2022 at 3:39 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> +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
> >
>
>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1886 bytes --]
next prev parent reply other threads:[~2022-03-31 20:27 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 [this message]
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
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=CAGSLe_FK6wfFYSoOsxFe7mbDxs72CNJSORgV14xsxGH+OKw07g@mail.gmail.com \
--to=satishkamara@gmail.com \
--cc=cristian.dumitrescu@intel.com \
--cc=jasvinder.singh@intel.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).