DPDK usage discussions
 help / color / mirror / Atom feed
From: waqas ahmed <waqasahmed1471@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Bit rate problem of pipe traffic classes in DPDK19.11 QOS app
Date: Fri, 10 Apr 2020 12:07:17 +0500	[thread overview]
Message-ID: <CAMr3K=da-ohvkG44y_oCEwS6dnh+byV3ZnOmF+BTq9MJ2SuA-Q@mail.gmail.com> (raw)

G'day,
we are working with dpdk19.11 qos application and tries to understand its
working at pipe level. it is configured with 4096 pipes under subport 0 and
currently we are using only one pipe0.
pipe is given with 13 traffic classes (tc) and each of tc is configured
with pipe profile as given below. we are putting single RTP stream into
each of tc one by one to see its guaranteed bit rate specified.
if we use queue = tc# than bit rate of respective traffic class doesn't
match, but if we put any of tc packets into queue 0 of pipe than each of tc
bit rate guarantees to its upper limit.
can any one explain this behavior? how can we get exact bit rate of tc by
forwarding pkts to its own queue?

; Pipe configuration
[pipe profile 0]

tb rate = 1750000              ; 1750000 X 8 = 14 mbits/sec
tb size = 1000000              ; Bytes

tc 0 rate = 1750000            ; 14
tc 1 rate = 1625000            ; 13
tc 2 rate = 1500000            ; 12
tc 3 rate = 1375000            ; 11
tc 4 rate = 1125000            ; 9
tc 5 rate = 1000000            ; 8
tc 6 rate = 875000             ; 7
tc 7 rate = 750000             ; 6
tc 8 rate = 625000             ; 5
tc 9 rate = 500000             ; 4
tc 10 rate = 375000            ; 3
tc 11 rate = 250000            ; 2
tc 12 rate = 125000            ; (125000 X 8 = 1000000) 1 mbits/sec
Regards

                 reply	other threads:[~2020-04-10  7:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAMr3K=da-ohvkG44y_oCEwS6dnh+byV3ZnOmF+BTq9MJ2SuA-Q@mail.gmail.com' \
    --to=waqasahmed1471@gmail.com \
    --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).