DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
	"Chautru, Nicolas" <nicolas.chautru@intel.com>,
	"Kinsella, Ray" <mdr@ashroe.eu>,
	David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, Akhil Goyal <gakhil@marvell.com>,
	Thomas Monjalon <thomas@monjalon.net>, Tom Rix <trix@redhat.com>,
	"Zhang, Mingshan" <mingshan.zhang@intel.com>,
	"Joshi, Arun" <arun.joshi@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] bbdev: remove experimental tag from API
Date: Tue, 14 Sep 2021 03:13:03 +0000	[thread overview]
Message-ID: <DU2PR04MB8630D3000BA50AF63F39873989DA9@DU2PR04MB8630.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <a4fd0560-b98e-6860-d7fe-1a9785d09b6f@redhat.com>

HI Maxime,

> 
> On 9/1/21 4:54 PM, Chautru, Nicolas wrote:
> >
> >
> >> -----Original Message-----
> >> From: Kinsella, Ray <mdr@ashroe.eu>
> >> Sent: Wednesday, September 1, 2021 4:15 AM
> >> To: Hemant Agrawal <hemant.agrawal@nxp.com>; David Marchand
> >> <david.marchand@redhat.com>; Chautru, Nicolas
> >> <nicolas.chautru@intel.com>
> >> Cc: dev <dev@dpdk.org>; Akhil Goyal <gakhil@marvell.com>; Thomas
> >> Monjalon <thomas@monjalon.net>; Tom Rix <trix@redhat.com>; Zhang,
> >> Mingshan <mingshan.zhang@intel.com>; Joshi, Arun
> >> <arun.joshi@intel.com>; Maxime Coquelin
> <maxime.coquelin@redhat.com>
> >> Subject: Re: [PATCH v1] bbdev: remove experimental tag from API
> >>
> >>
> >>
> >> On 01/09/2021 04:52, Hemant Agrawal wrote:
> >>>>
> >>>> On Tue, Aug 31, 2021 at 6:27 PM Nicolas Chautru
> >>>> <nicolas.chautru@intel.com> wrote:
> >>>>>
> >>>>> This was previously suggested last year
> >>>>>
> >>>>
> >> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpat
> >>>> c
> >>>>> hes.dpdk.org%2Fproject%2Fdpdk%2Fpatch%2F1593213242-157394-2-
> >> git-
> >>>> send-e
> >>>>> mail-
> >>>>
> >>
> nicolas.chautru%40intel.com%2F&amp;data=04%7C01%7Chemant.agrawal%
> >>>>>
> >>>>
> >>
> 40nxp.com%7Cfcdfb339ec284057db1508d96c9dd048%7C686ea1d3bc2b4c6f
> >>>> a92cd99
> >>>>>
> >>>>
> c5c301635%7C0%7C0%7C637660247324212288%7CUnknown%7CTWFpbGZ
> >>>> sb3d8eyJWIjo
> >>>>>
> >>>>
> >>
> iMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1
> >>>> 000&amp
> >>>>>
> >> ;sdata=%2FYwaT29I4XlUxedcdCeyvM5z1R5QeNGTLLPY3XQBKjU%3D&amp
> >>>> ;reserved=0
> >>>>> but there was request from community to wait another year to
> >>>>> confirm
> >>>> formally this api is mature.
> >>>>
> >>>> The request was to wait for a new vendor (i.e. non Intel) to
> >>>> implement a bbdev driver for their hw.
> >>>>
> >>>> NXP proposed a driver for this class:
> >>>>
> >> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpat
> >>>> ch
> >>
> work.dpdk.org%2Fproject%2Fdpdk%2Flist%2F%3Fseries%3D16642%26state
> >>>>
> >> %3D%252A%26archive%3Dboth&amp;data=04%7C01%7Chemant.agrawal%
> >>>>
> >>
> 40nxp.com%7Cfcdfb339ec284057db1508d96c9dd048%7C686ea1d3bc2b4c6f
> >>>>
> a92cd99c5c301635%7C0%7C0%7C637660247324212288%7CUnknown%7CT
> >>>>
> >>
> WFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLC
> >>>>
> >>
> JXVCI6Mn0%3D%7C1000&amp;sdata=iorsQ7wAXyU2%2FaqeV5CrDp9asl8ztZ
> >>>> nSrbDuJpCv9Gk%3D&amp;reserved=0
> >>>>
> >>>> What is the status of this driver?
> >>>
> >>> [Hemant]  We are in process of resending the patches in next few days.
> >>
> >> Ok - just so we are clear - the net-net of that, is that the bbdev
> >> APIs will be 'experimental'
> >> for another year, right?
> >
> > There is little reason to defer further I believe. Henant please confirm you
> are not looking at any ABI change based on discussion for the last few
> months.
> >
> >>
> >>>
> >>>> I see no update on the bbdev API, which seems good, but a
> >>>> confirmation is needed.
> >
> > Indeed that's all we need. Confirmation no change is require for new PMD.
> 
> Hemant, could you confirm this is good for you?

[Hemant] I am ok to remove experimental from these APIs. However, can that wait towards later part for this release. 

NXP will be sending few changes in next few days for the APIs. 

Regards,
Hemant  


> 
> Thanks,
> Maxime
> 
> >>>>
> >>>>
> >>>> --
> >>>> David Marchand
> >>>


  reply	other threads:[~2021-09-14  3:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31 16:25 Nicolas Chautru
2021-08-31 16:25 ` Nicolas Chautru
2021-10-08 19:29   ` [dpdk-dev] [EXT] " Akhil Goyal
2021-10-31 19:17     ` Akhil Goyal
2021-11-06  8:58       ` Thomas Monjalon
2021-08-31 16:38 ` [dpdk-dev] " David Marchand
2021-09-01  3:52   ` Hemant Agrawal
2021-09-01 11:14     ` Kinsella, Ray
2021-09-01 14:54       ` Chautru, Nicolas
2021-09-13 19:44         ` Maxime Coquelin
2021-09-14  3:13           ` Hemant Agrawal [this message]
2021-09-01 14:51     ` Chautru, Nicolas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DU2PR04MB8630D3000BA50AF63F39873989DA9@DU2PR04MB8630.eurprd04.prod.outlook.com \
    --to=hemant.agrawal@nxp.com \
    --cc=arun.joshi@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mdr@ashroe.eu \
    --cc=mingshan.zhang@intel.com \
    --cc=nicolas.chautru@intel.com \
    --cc=thomas@monjalon.net \
    --cc=trix@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).