From: Akhil Goyal <akhil.goyal@nxp.com>
To: Aidan Goddard <aidan.goddard@accelercomm.com>
Cc: "nicolas.chautru@intel.com" <nicolas.chautru@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] BBDEV: add LDPC op parameters and flags to support CBGT
Date: Thu, 12 Nov 2020 21:13:53 +0000 [thread overview]
Message-ID: <VI1PR04MB31683F08CBAD6DFD1098F02CE6E70@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1604586344-25634-1-git-send-email-aidan.goddard@accelercomm.com>
> This commit adds support to BBDEV for LDPC Code Block Group Transmission
> (CBGT) as defined in 3GPP TS 38.214. The following changes facilitate this:
> - add RTE_BBDEV_LDPC_[ENC/DEC]_CBGT feature flag
> - add CBGT input parameters to LDPC encode transport block op structure
> - add CBGT input and output parameters to LDPC decode transport block op
> - add support for reading these parameters from test vector files
> - add sanity tests for RTE_BBDEV_LDPC_[ENC/DEC]_CBGT flag in test vector
> - update user guide with the flags and parameters
>
> CBGT parameters are only required when the
> RTE_BBDEV_LDPC_[ENC/DEC]_CBGT
> op flag is specified.
>
> Reported-by: Rob Maunder <rob.maunder@accelercomm.com>
> Signed-off-by: Aidan Goddard <aidan.goddard@accelercomm.com>
> Acked-by: Dave Burley <dave.burley@accelercomm.com>
> ---
> app/test-bbdev/test_bbdev_vector.c | 46 +++++++++++++++++++---
> app/test-bbdev/test_bbdev_vector.h | 3 ++
> doc/guides/prog_guide/bbdev.rst | 29 ++++++++++++++
> lib/librte_bbdev/rte_bbdev_op.h | 80
> +++++++++++++++++++++++++++++++++++++-
> 4 files changed, 151 insertions(+), 7 deletions(-)
>
I believe this patch is for next release.
next prev parent reply other threads:[~2020-11-12 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 13:57 [dpdk-dev] [PATCH] " Aidan Goddard
2020-11-05 14:25 ` [dpdk-dev] [PATCH v3] " Aidan Goddard
2020-11-12 21:13 ` Akhil Goyal [this message]
2020-11-13 23:19 ` Chautru, Nicolas
2021-01-11 19:22 ` Akhil Goyal
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=VI1PR04MB31683F08CBAD6DFD1098F02CE6E70@VI1PR04MB3168.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=aidan.goddard@accelercomm.com \
--cc=dev@dpdk.org \
--cc=nicolas.chautru@intel.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).