[prev in list] [next in list] [prev in thread] [next in thread]
List: dpdk-dev
Subject: Re: [dpdk-dev] QoS: The difference of traffic class between subport and pipe in QoS
From: "Dumitrescu, Cristian" <cristian.dumitrescu () intel ! com>
Date: 2016-08-31 17:44:00
Message-ID: 3EB4FA525960D640B5BDFFD6A3D8912647A549A1 () IRSMSX108 ! ger ! corp ! intel ! com
[Download RAW message or body]
> -----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.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic