From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 205DA8E99; Wed, 7 Sep 2016 17:06:09 +0200 (CEST) Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga102.fm.intel.com with ESMTP; 07 Sep 2016 08:05:48 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,296,1470726000"; d="scan'208,217";a="6008771" Received: from irsmsx152.ger.corp.intel.com ([163.33.192.66]) by orsmga004.jf.intel.com with ESMTP; 07 Sep 2016 08:05:45 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.71]) by IRSMSX152.ger.corp.intel.com ([169.254.6.43]) with mapi id 14.03.0248.002; Wed, 7 Sep 2016 16:05:44 +0100 From: "Dumitrescu, Cristian" To: "lvenyong@1218.com.cn" , "dev@dpdk.org" , "users@dpdk.org" Thread-Topic: RE: [dpdk-dev] QoS: The difference of traffic class between subport and pipe in QoS Thread-Index: AdIDe5GuelZrKAfJTaW6FT4spKu7dAAgTUylAUbABlA= Date: Wed, 7 Sep 2016 15:05:44 +0000 Message-ID: <3EB4FA525960D640B5BDFFD6A3D8912647A662B9@IRSMSX108.ger.corp.intel.com> References: <005201d2037b$920bbff0$b6233fd0$@com.cn>, <3EB4FA525960D640B5BDFFD6A3D8912647A549A1@IRSMSX108.ger.corp.intel.com> <2016090110580424108711@1218.com.cn> In-Reply-To: <2016090110580424108711@1218.com.cn> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYjMyNGVmOGYtM2UzYy00M2M4LWJmODgtYjIwMmVjZDJhM2I0IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6ImdTVWZ6V3FoakNkMmR2ZWxBaVlJN0N3Qmd6NG1jRjJSTEdvZXI0VlFEaU09In0= x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.180] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] QoS: The difference of traffic class between subport and pipe in QoS X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2016 15:06:11 -0000 Traffic class is really the type of traffic, e.g. voice, real-time video (l= ike RTP), best effort (TCP-based video, file downloads, etc). Each traffic = type has different requirements in terms on latency/delay, jitter/delay var= iation, loss rate, bandwidth, etc. The levels of our scheduling hierarchy are: (1) port (output network interf= ace), (2) subport (port slide, i.e. group of pipes/users), (3) pipe (user/s= ubscriber), (4) traffic class (type of traffic), (5) packet queue. The rati= onale for having a TC limit at subport and pipe levels is to rate limit the= about of that traffic type that the user (pipe level TC rate) or the group= of users (subport level TC rate) are allowed to send. For example, you mig= ht want to restrict the amount of real-time video each user is sending to 1= Mbps, but also the amount to real-time video the group of e.g. 1000 users = to 500Mbps; then packets might be restricted from being scheduled by either= the user-level limit or the group-level limit, whichever is hit first. Here is a Youtube video on DPDK QoS in case you're tired of reading the doc= s or the code: https://youtu.be/_PPklkWGugs Regards, Cristian From: lvenyong@1218.com.cn [mailto:lvenyong@1218.com.cn] Sent: Thursday, September 1, 2016 3:58 AM To: Dumitrescu, Cristian ; dev@dpdk.org; use= rs@dpdk.org Subject: Re: RE: [dpdk-dev] QoS: The difference of traffic class between su= bport and pipe in QoS Thanks for your answer! But i haved not understand it. what is the role of traffic class in subport, and the relationship with th= e 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 col= or); ________________________________ 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 subpor= t 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 po= rt, > 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 =3D 1250000000 ; Bytes per second > tb size =3D 1000000 ; Bytes > tc 0 rate =3D 1250000000 ; Bytes per second > tc 1 rate =3D 1250000000 ; Bytes per second > tc 2 rate =3D 1250000000 ; Bytes per second > tc 3 rate =3D 1250000000 ; Bytes per second > tc period =3D 10 ; Milliseconds > pipe 0-4095 =3D 0 ; These pipes are configured with pipe > profile 0 > ; Pipe configuration > [pipe profile 0] > tb rate =3D 305175 ; Bytes per second > tb size =3D 1000000 ; Bytes > tc 0 rate =3D 305175 ; Bytes per second > tc 1 rate =3D 305175 ; Bytes per second > tc 2 rate =3D 305175 ; Bytes per second > tc 3 rate =3D 305175 ; Bytes per second > tc period =3D 40 ; Milliseconds > > Thanks > > There are 4x traffic classes. You can enforce a limit on the amount of traf= fic belonging to each traffic class at the subport level, as well as at the= level of each pipe if you want.