All of lore.kernel.org
 help / color / mirror / Atom feed
From: "lvenyong@1218.com.cn" <lvenyong@1218.com.cn>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: QoS: The difference of traffic class between subport and	pipe in QoS
Date: Thu, 1 Sep 2016 10:58:05 +0800	[thread overview]
Message-ID: <2016090110580424108711@1218.com.cn> (raw)
In-Reply-To: 3EB4FA525960D640B5BDFFD6A3D8912647A549A1@IRSMSX108.ger.corp.intel.com

Thanks for your answer!  But i haved not understand it. 
what is the role of traffic class in subport, and the  relationship with the traffic class in pipe ?
The  traffic class in function of rte_sched_port_pkt_write is subport's or pipe's ?
void rte_sched_port_pkt_write(struct rte_mbuf *pkt,
 uint32_t subport, uint32_t pipe, uint32_t traffic_class,
 uint32_t queue, enum rte_meter_color color);



lvenyong@1218.com.cn
 
From: Dumitrescu, Cristian
Date: 2016-09-01 01:44
To: lvenyong; dev@dpdk.org
CC: users@dpdk.org
Subject: RE: [dpdk-dev] QoS: The difference of traffic class between subport and pipe in QoS
 
 
> -----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-09-01  2:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31 11:34 QoS: The difference of traffic class between subport and pipe in QoS lvenyong
2016-08-31 17:44 ` Dumitrescu, Cristian
2016-09-01  2:58   ` lvenyong [this message]
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=2016090110580424108711@1218.com.cn \
    --to=lvenyong@1218.com.cn \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.