DPDK usage discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: lvenyong <lvenyong@1218.com.cn>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] [dpdk-dev] QoS: The difference of traffic class between subport and	pipe in QoS
Date: Wed, 31 Aug 2016 17:44:00 +0000	[thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D8912647A549A1@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <005201d2037b$920bbff0$b6233fd0$@com.cn>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of lvenyong
> Sent: Wednesday, August 31, 2016 12:34 PM
> To: dev@dpdk.org
> Cc: users@dpdk.org
> Subject: [dpdk-dev] QoS: The difference of traffic class between subport and
> pipe in QoS
> 
> HI !
> 
> Is there difference of traffic class between subport and pipe in QOS ?
> 
> After read prog_guide-2.2.pdf we kown that the scheduling hierarchy is port,
> subport, pipe, traffic class and queue. But the traffic class both in
> subport and pipe appeared in example of qos_sched .
> 
> [subport 0]
> tb rate = 1250000000           ; Bytes per second
> tb size = 1000000              ; Bytes
> tc 0 rate = 1250000000         ; Bytes per second
> tc 1 rate = 1250000000         ; Bytes per second
> tc 2 rate = 1250000000         ; Bytes per second
> tc 3 rate = 1250000000         ; Bytes per second
> tc period = 10                 ; Milliseconds
> pipe 0-4095 = 0                ; These pipes are configured with pipe
> profile 0
> ; Pipe configuration
> [pipe profile 0]
> tb rate = 305175               ; Bytes per second
> tb size = 1000000              ; Bytes
> tc 0 rate = 305175             ; Bytes per second
> tc 1 rate = 305175             ; Bytes per second
> tc 2 rate = 305175             ; Bytes per second
> tc 3 rate = 305175             ; Bytes per second
> tc period = 40                 ; Milliseconds
> 
> Thanks
> 
> 

There are 4x traffic classes. You can enforce a limit on the amount of traffic belonging to each traffic class at the subport level, as well as at the level of each pipe if you want.

  reply	other threads:[~2016-08-31 17:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31 11:34 lvenyong
2016-08-31 17:44 ` Dumitrescu, Cristian [this message]
2016-09-01  2:58   ` lvenyong
2016-09-07 15:05     ` Dumitrescu, Cristian
     [not found]       ` <2016090810070075348716@1218.com.cn>
2016-09-08  2:11         ` lvenyong

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=3EB4FA525960D640B5BDFFD6A3D8912647A549A1@IRSMSX108.ger.corp.intel.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=lvenyong@1218.com.cn \
    --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).