From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Subject: Re: [PATCH v3 2/2] ethdev: add hierarchical scheduler API
Date: Fri, 10 Mar 2017 18:37:30 +0000
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891265275E105@IRSMSX108.ger.corp.intel.com>
References: <1488589820-206947-1-git-send-email-cristian.dumitrescu@intel.com>
 <6158991.OypYtkqGNY@xps13>
 <3EB4FA525960D640B5BDFFD6A3D891265275A053@IRSMSX108.ger.corp.intel.com>
 <3752751.fl3uBnnZGo@xps13>
 <3EB4FA525960D640B5BDFFD6A3D891265275BDC0@IRSMSX108.ger.corp.intel.com>
 <26FA93C7ED1EAA44AB77D62FBE1D27BA7231952B@IRSMSX108.ger.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: "dev@dpdk.org" <dev@dpdk.org>, "jerin.jacob@caviumnetworks.com"
 <jerin.jacob@caviumnetworks.com>, "balasubramanian.manoharan@cavium.com"
 <balasubramanian.manoharan@cavium.com>, "hemant.agrawal@nxp.com"
 <hemant.agrawal@nxp.com>, "shreyansh.jain@nxp.com" <shreyansh.jain@nxp.com>,
 "Wiles, Keith" <keith.wiles@intel.com>, "Richardson, Bruce"
 <bruce.richardson@intel.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>, Thomas Monjalon
 <thomas.monjalon@6wind.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mga01.intel.com (mga01.intel.com [192.55.52.88])
 by dpdk.org (Postfix) with ESMTP id 439F537B4
 for <dev@dpdk.org>; Fri, 10 Mar 2017 19:37:42 +0100 (CET)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA7231952B@IRSMSX108.ger.corp.intel.com>
Content-Language: en-US
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>



> -----Original Message-----
> From: O'Driscoll, Tim
> Sent: Wednesday, March 8, 2017 9:52 AM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Thomas Monjalon
> <thomas.monjalon@6wind.com>
> Cc: dev@dpdk.org; jerin.jacob@caviumnetworks.com;
> balasubramanian.manoharan@cavium.com; hemant.agrawal@nxp.com;
> shreyansh.jain@nxp.com; Wiles, Keith <keith.wiles@intel.com>; Richardson,
> Bruce <bruce.richardson@intel.com>
> Subject: RE: [PATCH v3 2/2] ethdev: add hierarchical scheduler API
>=20
> > From: Dumitrescu, Cristian
> >


...<snip>

> > > OK I better understand now.
> > > You should add this level of explanation in your patch.
> > >
> > > However I am reluctant to add an API if there is no user.
> > > I think we should wait to have at least one existing driver
> > implementing
> > > this API before integrating it.
> > > It was the approach of eventdev which has a dedicated next- tree.
> >
> > The next-tree solution could work, but IMO is not the best for this
> > case, as this is purely driver development. This is just a TX offload
> > feature that is well understood, as opposed to a new library with a hug=
e
> > design effort required like eventdev.
> >
> > I think we are reasonably close to get agreement on the API from Cavium=
,
> > Intel and NXP. When this is done, how about including it in DPDK with
> > the experimental tag attached to it until several drivers implement it?
> >
> > From Intel side, there are solid plans to implement it for ixgbe and
> > i40e drivers in next DPDK releases, I am CC-ing Tim to confirm this.
>=20
> That's correct. We plan to add support for this in the ixgbe and i40e dri=
vers in
> 17.08.

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 incl=
uding this API in 17.5 with experimental tag (subject to full API agreement=
 being reached)?

IMO this approach has the advantage of showing that API agreement has been =
reached and driver development is in progress. Having it in DPDK is also a =
better way to advertise this API to the developers that would otherwise be =
unaware about this effort.

>=20
> > On
> > Cavium and NXP side, Jerin and Hemant can comment on the plans to
> > implement this API.