From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, gakhil@marvell.com, trix@redhat.com
Cc: thomas@monjalon.net, hemant.agrawal@nxp.com,
mingshan.zhang@intel.com, david.marchand@redhat.com,
Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [PATCH v1] bbdev: add new operation for FFT processing
Date: Thu, 10 Mar 2022 15:49:16 -0800 [thread overview]
Message-ID: <1646956157-245769-1-git-send-email-nicolas.chautru@intel.com> (raw)
Hi,
This contributions adds a new operation type to the existing ones
already supported by the bbdev PMDs.
This set of operation is FFT-based processing for 5GNR baseband
processing acceleration. This operates in the same lookaside fashion
as other existing bbdev operation with a dedicated set of capabilities
and parameters (marked as experimental).
I plan to also include a new PMD supporting this operation (and most of
the related capabilities) in the next couple of months (either in 22.06
or 22.09) as well as extending the related bbdev-test.
I can update the release notes for 22.06 on subsequent patch vs or separate
commit (not there yet). Thanks for review feedback.
Nicolas Chautru (1):
bbdev: add new operation for FFT processing
doc/guides/prog_guide/bbdev.rst | 130 +++++++++++++++++++++++++++++++++++
lib/bbdev/rte_bbdev.c | 8 +++
lib/bbdev/rte_bbdev.h | 76 ++++++++++++++++++++
lib/bbdev/rte_bbdev_op.h | 149 ++++++++++++++++++++++++++++++++++++++++
lib/bbdev/version.map | 10 +++
5 files changed, 373 insertions(+)
--
1.8.3.1
next reply other threads:[~2022-03-11 0:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 23:49 Nicolas Chautru [this message]
2022-03-10 23:49 ` [PATCH v1] bbdev: add new operation for FFT processing Nicolas Chautru
2022-03-11 1:12 ` Stephen Hemminger
2022-03-17 18:42 ` Chautru, Nicolas
2022-05-25 22:07 ` Chautru, Nicolas
2022-05-26 6:05 ` Hemant Agrawal
2022-06-07 11:29 ` David Marchand
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=1646956157-245769-1-git-send-email-nicolas.chautru@intel.com \
--to=nicolas.chautru@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=mingshan.zhang@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.