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 AFFBA4A59 for ; Wed, 7 Dec 2016 21:13:28 +0100 (CET) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga104.fm.intel.com with ESMTP; 07 Dec 2016 12:13:27 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,315,1477983600"; d="scan'208";a="909821723" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by orsmga003.jf.intel.com with ESMTP; 07 Dec 2016 12:13:25 -0800 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.159]) by IRSMSX102.ger.corp.intel.com ([169.254.2.79]) with mapi id 14.03.0248.002; Wed, 7 Dec 2016 20:13:24 +0000 From: "Dumitrescu, Cristian" To: Thomas Monjalon , Stephen Hemminger CC: "dev@dpdk.org" , Hemant Agrawal , Shreyansh Jain , Jerin Jacob , "adrien.mazarguil@6wind.com" , Olga Shern , Ajit Khaparde , Rahul Lakkireddy , Alejandro Lucero Thread-Topic: [dpdk-dev] [RFC] ethdev: abstraction layer for QoS hierarchical scheduler Thread-Index: AQHSSzXynsac9sXyqk++qsVVyCqc5aD7XdMAgAAn54CAAWrU4A== Date: Wed, 7 Dec 2016 20:13:24 +0000 Message-ID: <3EB4FA525960D640B5BDFFD6A3D891265271133E@IRSMSX108.ger.corp.intel.com> References: <1480529810-95280-1-git-send-email-cristian.dumitrescu@intel.com> <20161206115124.67ccc0c7@xeon-e3> <2204708.uGZ3ieR731@xps13> In-Reply-To: <2204708.uGZ3ieR731@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYTEyYjU5NzAtYjk3Mi00OWU5LWE2MWYtMDhkYzRkMGI1ZDc0IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjIuMTEuMCIsIlRydXN0ZWRMYWJlbEhhc2giOiJBdVhhWjQxS1BnbEs3Y0p6TElwaHNKVWNocmR6REM1VG1UblFWTFdRdnNVPSJ9 x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [RFC] ethdev: abstraction layer for QoS hierarchical scheduler X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2016 20:13:29 -0000 > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Tuesday, December 6, 2016 10:14 PM > To: Stephen Hemminger > Cc: dev@dpdk.org; Dumitrescu, Cristian > Subject: Re: [dpdk-dev] [RFC] ethdev: abstraction layer for QoS hierarchi= cal > scheduler >=20 > 2016-12-06 11:51, Stephen Hemminger: > > Rather than reinventing wheel which seems to be DPDK Standard > > Procedure, could an existing abstraction be used? >=20 > Stephen, you know that the DPDK standard procedure is to consider > reviews and good comments ;) Thomas, sorry for not CC-ing you (as the librte_ether maintainer) when the initial RFC was sent out, comments from you would be welcomed and much appreciated as well! Also same kind reminder for other people in the community as well. (CC-ing just a few). Some of you have expressed interest in the past for building an abstraction layer for QoS hierarchical scheduler, so here is th= e RFC for it which we can evolve together. Let's make sure we build a robust layer that fits well for all devices and vendors that are part of the DPDK community!