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 v2 0/5] bbdev: API extension for 23.11
Date: Thu, 15 Jun 2023 16:48:56 +0000	[thread overview]
Message-ID: <20230615164901.40845-1-nicolas.chautru@intel.com> (raw)

v2: moving the new mld functions at the end of struct rte_bbdev to avoid
ABI offset changes based on feedback with Maxime.
Adding a commit to waive the FFT ABI warning since that experimental function
could break ABI (let me know if preferred to be merged with the FFT
commit causing the FFT change). 


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 (5):
  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
  devtools: ignore changes into bbdev experimental API

 devtools/libabigail.abignore    |   4 +-
 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 ++
 6 files changed, 323 insertions(+), 14 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-06-15 16:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15 16:48 Nicolas Chautru [this message]
2023-06-15 16:48 ` [PATCH v2 1/5] bbdev: add operation type for MLDTS procession Nicolas Chautru
2023-09-18 15:03   ` Maxime Coquelin
2023-06-15 16:48 ` [PATCH v2 2/5] bbdev: add new capabilities for FFT processing Nicolas Chautru
2023-09-18 15:08   ` Maxime Coquelin
2023-09-18 15:42     ` Maxime Coquelin
2023-09-18 20:50       ` Chautru, Nicolas
2023-06-15 16:48 ` [PATCH v2 3/5] bbdev: add new capability for FEC 5G UL processing Nicolas Chautru
2023-09-18 15:09   ` Maxime Coquelin
2023-06-15 16:49 ` [PATCH v2 4/5] bbdev: improving error handling for queue configuration Nicolas Chautru
2023-09-18 15:20   ` Maxime Coquelin
2023-06-15 16:49 ` [PATCH v2 5/5] devtools: ignore changes into bbdev experimental API Nicolas Chautru
2023-09-06  6:17   ` Hemant Agrawal
2023-09-12 20:32     ` Vargas, Hernan
2023-09-13  9:31       ` Hemant Agrawal
2023-09-18 15:22   ` Maxime Coquelin
2023-07-17 22:28 ` [PATCH v2 0/5] bbdev: API extension for 23.11 Chautru, Nicolas
2023-08-04 16:14   ` Vargas, Hernan
2023-09-05 17:48     ` Chautru, Nicolas
2023-07-18  9:18 ` Hemant Agrawal
2023-09-06  6:20 ` Hemant Agrawal
2023-09-21  7:35 ` Maxime Coquelin

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=20230615164901.40845-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).