From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 816523989; Wed, 31 Aug 2016 19:44:04 +0200 (CEST) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga104.fm.intel.com with ESMTP; 31 Aug 2016 10:44:04 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,263,1470726000"; d="scan'208";a="3190820" Received: from irsmsx103.ger.corp.intel.com ([163.33.3.157]) by fmsmga006.fm.intel.com with ESMTP; 31 Aug 2016 10:44:02 -0700 Received: from irsmsx156.ger.corp.intel.com (10.108.20.68) by IRSMSX103.ger.corp.intel.com (163.33.3.157) with Microsoft SMTP Server (TLS) id 14.3.248.2; Wed, 31 Aug 2016 18:44:02 +0100 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.71]) by IRSMSX156.ger.corp.intel.com ([169.254.3.234]) with mapi id 14.03.0248.002; Wed, 31 Aug 2016 18:44:01 +0100 From: "Dumitrescu, Cristian" To: lvenyong , "dev@dpdk.org" CC: "users@dpdk.org" Thread-Topic: [dpdk-dev] QoS: The difference of traffic class between subport and pipe in QoS Thread-Index: AdIDe5GuelZrKAfJTaW6FT4spKu7dAAM4pDw Date: Wed, 31 Aug 2016 17:44:00 +0000 Message-ID: <3EB4FA525960D640B5BDFFD6A3D8912647A549A1@IRSMSX108.ger.corp.intel.com> References: <005201d2037b$920bbff0$b6233fd0$@com.cn> In-Reply-To: <005201d2037b$920bbff0$b6233fd0$@com.cn> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZmNkN2Q5YzgtYmVjMy00NzQ0LTk0NzYtNzk0OTNlMGY3ZGEyIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6InROZWVmS1BoOEhFb3JhRitkWVhUMld3Y0lcLzZNNFlRNVdmYjAreUJvOGpnPSJ9 x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] [dpdk-dev] QoS: The difference of traffic class between subport and pipe in QoS X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2016 17:44:05 -0000 > -----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 >=20 > HI ! >=20 > Is there difference of traffic class between subport and pipe in QOS ? >=20 > 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 . >=20 > [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 >=20 > Thanks >=20 >=20 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.