From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, maxime.coquelin@redhat.com
Cc: hemant.agrawal@nxp.com, david.marchand@redhat.com,
hernan.vargas@intel.com,
Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [PATCH v1 0/3] bbdev: new k0 parameter
Date: Mon, 1 Jul 2024 14:27:00 -0700 [thread overview]
Message-ID: <20240701212703.417094-1-nicolas.chautru@intel.com> (raw)
Hi Maxime, Hemant,
Capturing below an extension for 24.11.
This includes bbdev api change and related change for
test application and acc/vrb PMD.
This provides the ability which was introduced in 3gPP
standard to have an alternate way to compute k0 no longer
always computed just from rv_index. When that parameter
is set, then it is used a k0 value (starting position
in circular index), if null the legacy computation
from rv index (more common) is maintained.
Nicolas Chautru (3):
bbdev: new k0 parameter for LDPC decoder operation
test/bbdev: add support for k0 parameter
baseband/acc: add support for k0 parameter
app/test-bbdev/test_bbdev_perf.c | 7 +++++--
app/test-bbdev/test_bbdev_vector.c | 4 ++++
app/test-bbdev/test_bbdev_vector.h | 1 +
doc/guides/prog_guide/bbdev.rst | 2 ++
drivers/baseband/acc/acc_common.h | 6 ++++--
drivers/baseband/acc/rte_acc100_pmd.c | 2 +-
drivers/baseband/acc/rte_vrb_pmd.c | 4 ++--
lib/bbdev/rte_bbdev_op.h | 4 ++++
8 files changed, 23 insertions(+), 7 deletions(-)
--
2.34.1
next reply other threads:[~2024-07-01 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 21:27 Nicolas Chautru [this message]
2024-07-01 21:27 ` [PATCH v1 1/3] bbdev: new k0 parameter for LDPC decoder operation Nicolas Chautru
2024-08-29 8:00 ` Maxime Coquelin
2024-07-01 21:27 ` [PATCH v1 2/3] test/bbdev: add support for k0 parameter Nicolas Chautru
2024-08-29 8:01 ` Maxime Coquelin
2024-07-01 21:27 ` [PATCH v1 3/3] baseband/acc: " Nicolas Chautru
2024-08-29 8:01 ` Maxime Coquelin
2024-07-02 6:50 ` [PATCH v1 0/3] bbdev: new " Hemant Agrawal
2024-09-13 13:50 ` 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=20240701212703.417094-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 \
/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).