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 C907E1075 for ; Thu, 16 Mar 2017 18:40:40 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intel.com; i=@intel.com; q=dns/txt; s=intel; t=1489686040; x=1521222040; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=ucy+UBnDn1lexsasJIQq++yLHdr+l4qLYyNEt4YXUI0=; b=j+HBIcW9E+LkT1s48fnJw5YKnxYsb5Ka0srOPspFx375J+qCfhkFgM2M 8V056VeJffwlyGU5NiOd+zmLmiJLoQ==; Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Mar 2017 10:40:39 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,173,1486454400"; d="scan'208";a="237177418" Received: from irsmsx106.ger.corp.intel.com ([163.33.3.31]) by fmsmga004.fm.intel.com with ESMTP; 16 Mar 2017 10:40:38 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.173]) by IRSMSX106.ger.corp.intel.com ([169.254.8.197]) with mapi id 14.03.0248.002; Thu, 16 Mar 2017 17:40:37 +0000 From: "Dumitrescu, Cristian" To: Thomas Monjalon CC: "O'Driscoll, Tim" , "dev@dpdk.org" , "jerin.jacob@caviumnetworks.com" , "balasubramanian.manoharan@cavium.com" , "hemant.agrawal@nxp.com" , "shreyansh.jain@nxp.com" , "Wiles, Keith" , "Richardson, Bruce" Thread-Topic: [PATCH v3 2/2] ethdev: add hierarchical scheduler API Thread-Index: AQHSlmXkX5aIvTYL1U6GZzZccGSDv6GIAuLQgAA63gCAAYJR4IAA9luAgAOvgTCAB4DRgIABtthggAArfYCAAACBcA== Date: Thu, 16 Mar 2017 17:40:37 +0000 Message-ID: <3EB4FA525960D640B5BDFFD6A3D891265276121D@IRSMSX108.ger.corp.intel.com> References: <1488589820-206947-1-git-send-email-cristian.dumitrescu@intel.com> <106399437.xFH6ZF6NRJ@xps13> <3EB4FA525960D640B5BDFFD6A3D8912652761170@IRSMSX108.ger.corp.intel.com> <4544430.1vcQTJXfeh@xps13> In-Reply-To: <4544430.1vcQTJXfeh@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMzhhMDUyNDEtNjQxYy00ODNhLWI1ZDctYTRiZDBmNjJkZDczIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IkUyOXZHTTFiXC9HbmRsSkx4QmwxcFNRVlhIcDdGZCt1WGhUZ0hveTlBVlY0PSJ9 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-dev] [PATCH v3 2/2] ethdev: add hierarchical scheduler API 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: Thu, 16 Mar 2017 17:40:41 -0000 > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Thursday, March 16, 2017 5:30 PM > To: Dumitrescu, Cristian > Cc: O'Driscoll, Tim ; dev@dpdk.org; > jerin.jacob@caviumnetworks.com; > balasubramanian.manoharan@cavium.com; hemant.agrawal@nxp.com; > shreyansh.jain@nxp.com; Wiles, Keith ; Richardson, > Bruce > Subject: Re: [PATCH v3 2/2] ethdev: add hierarchical scheduler API >=20 > 2017-03-16 16:23, Dumitrescu, Cristian: > > ... > > > > > > Thomas, given Tim's confirmation of Intel's plans to implement this= API > for > > > the ixgbe and i40e drivers in DPDK release 17.8, are you in favour of > including > > > this API in 17.5 with experimental tag (subject to full API agreement= being > > > reached)? > > > > > > I think starting a branch in a dedicated "next" repo is a better appr= oach. > > > rte_flow and eventdev were (and will be) integrated only when at leas= t > one > > > hardware device is supported. > > > I suggest to follow the same workflow. > > > > > > > Thomas, if this is the only path forward you are willing to support, th= en let's > go this way, but let's make sure we are all on the same page with the ter= ms > and conditions that apply. > > > > Do you agree now to merge this next-tree to DPDK once this API is > implemented for at least one PMD? We would like to avoid getting any last > minute objections from you or anybody else on the fundamentals; if you > have any, please let's discuss them now. >=20 > At least one "hardware" PMD, yes. It would prove the API can work for rea= l. > About accepting it definitely in a given release, it will be checked > with the technical board on Monday. >=20 OK, great, thank you. Is the agenda of the technical board meetings publish= ed in advance somewhere? > > How do we manage the API freeze on the next-tree? Once the API is > agreed, we would like to freeze it so the driver development can proceed; > we can then do some reasonably small changes to the API based on the > learnings we get during driver development. We would like to welcome any > parties interested in contributing to join Cavium, Intel and NXP in this = effort, > but we would like to avoid any last minute major API change requests. >=20 > You are taking it the wrong way. Your main concern is to not be disturbed > with change requests. It should be the contrary: you have a chance to > work with other vendors to test and improve the API. > You should embrace this chance and delay the API freeze as much as > possible. Not really. We definitely welcome change requests done in a timely manner. = My concern is about last minute change requests, such as major API change r= equests just a few days before the release when driver development is compl= ete. Is there a policy in place to prevent against such events for next-tre= e type of development?