DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, maxime.coquelin@redhat.com
Cc: trix@redhat.com, hemant.agrawal@nxp.com,
	david.marchand@redhat.com, hernan.vargas@intel.com,
	Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [PATCH v1 0/4] bbdev: API extension for 23.11
Date: Thu, 25 May 2023 23:23:27 +0000	[thread overview]
Message-ID: <20230525232331.34645-1-nicolas.chautru@intel.com> (raw)

Hi, 

Including v1 for extending the bbdev api for 23.11.
The new MLD-TS is expected to be non ABI compatible, the other
ones should not break ABI. 
I will send a deprecation notice in parallel.

This introduces a new operation (on top of FEC and FFT) to
support equalization for MLD-TS. There also more modular
API extension for existing FFT and FEC operation. 

Thanks
Nic

Nicolas Chautru (4):
  bbdev: add operation type for MLDTS procession
  bbdev: add new capabilities for FFT processing
  bbdev: add new capability for FEC 5G UL processing
  bbdev: improving error handling for queue configuration

 doc/guides/prog_guide/bbdev.rst |  83 ++++++++++++++++++
 lib/bbdev/rte_bbdev.c           |  26 +++---
 lib/bbdev/rte_bbdev.h           |  76 +++++++++++++++++
 lib/bbdev/rte_bbdev_op.h        | 143 +++++++++++++++++++++++++++++++-
 lib/bbdev/version.map           |   5 ++
 5 files changed, 320 insertions(+), 13 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-05-25 23:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25 23:23 Nicolas Chautru [this message]
2023-05-25 23:23 ` [PATCH v1 1/4] bbdev: add operation type for MLDTS procession Nicolas Chautru
2023-05-25 23:23 ` [PATCH v1 2/4] bbdev: add new capabilities for FFT processing Nicolas Chautru
2023-05-25 23:23 ` [PATCH v1 3/4] bbdev: add new capability for FEC 5G UL processing Nicolas Chautru
2023-05-25 23:23 ` [PATCH v1 4/4] bbdev: improving error handling for queue configuration Nicolas Chautru

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=20230525232331.34645-1-nicolas.chautru@intel.com \
    --to=nicolas.chautru@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=hernan.vargas@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --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).