From: Nic Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, gakhil@marvell.com
Cc: Nic Chautru <nicolas.chautru@intel.com>
Subject: [PATCH v1 1/1] doc: release note update for the bbdev change
Date: Thu, 22 Sep 2022 13:58:33 -0700 [thread overview]
Message-ID: <20220922205833.41496-2-nicolas.chautru@intel.com> (raw)
In-Reply-To: <20220922205833.41496-1-nicolas.chautru@intel.com>
To be squashed by Akhil.
Signed-off-by: Nic Chautru <nicolas.chautru@intel.com>
---
doc/guides/rel_notes/release_22_11.rst | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/doc/guides/rel_notes/release_22_11.rst b/doc/guides/rel_notes/release_22_11.rst
index 8c021cf050..22c0f23e39 100644
--- a/doc/guides/rel_notes/release_22_11.rst
+++ b/doc/guides/rel_notes/release_22_11.rst
@@ -84,6 +84,14 @@ API Changes
Also, make sure to start the actual text at the margin.
=======================================================
+* bbdev: Added new operation for FFT processing with notably the new functions
+ ``rte_bbdev_enqueue_fft_ops`` and ``rte_bbdev_dequeue_fft_ops`` and related structures.
+
+* bbdev: Updated enums such as ``rte_bbdev_op_type`` to include padding and to allow for
+ futureproof enum insertion.
+
+* bbdev: Updated structures to allow for new parameters for device status, queue topology and
+ queue status being exposed using ``rte_bbdev_enqueue_status `` and ``rte_bbdev_device_status``.
ABI Changes
-----------
--
2.37.1
prev parent reply other threads:[~2022-09-22 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 20:58 [PATCH v1 0/1] doc: release note update related to bbdev Nic Chautru
2022-09-22 20:58 ` Nic Chautru [this message]
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=20220922205833.41496-2-nicolas.chautru@intel.com \
--to=nicolas.chautru@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.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).