All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>
Cc: dev <dev@dpdk.org>, Akhil Goyal <gakhil@marvell.com>,
	 Thomas Monjalon <thomas@monjalon.net>, Tom Rix <trix@redhat.com>,
	 Hemant Agrawal <hemant.agrawal@nxp.com>,
	mingshan.zhang@intel.com, arun.joshi@intel.com,
	 Ray Kinsella <mdr@ashroe.eu>,
	Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v1] bbdev: remove experimental tag from API
Date: Tue, 31 Aug 2021 18:38:33 +0200	[thread overview]
Message-ID: <CAJFAV8xahpTizuFCGzqhrKAguyjNz-oewo16TaG-ZbLpB_yb3w@mail.gmail.com> (raw)
In-Reply-To: <1630427130-63903-1-git-send-email-nicolas.chautru@intel.com>

On Tue, Aug 31, 2021 at 6:27 PM Nicolas Chautru
<nicolas.chautru@intel.com> wrote:
>
> This was previously suggested last year https://patches.dpdk.org/project/dpdk/patch/1593213242-157394-2-git-send-email-nicolas.chautru@intel.com/
> 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://patchwork.dpdk.org/project/dpdk/list/?series=16642&state=%2A&archive=both

What is the status of this driver?
I see no update on the bbdev API, which seems good, but a confirmation
is needed.


-- 
David Marchand


  parent reply	other threads:[~2021-08-31 16:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31 16:25 [dpdk-dev] [PATCH v1] bbdev: remove experimental tag from API 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 ` David Marchand [this message]
2021-09-01  3:52   ` [dpdk-dev] " 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
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=CAJFAV8xahpTizuFCGzqhrKAguyjNz-oewo16TaG-ZbLpB_yb3w@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=arun.joshi@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hemant.agrawal@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.