From: Tom Rix <trix@redhat.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>,
dev@dpdk.org, gakhil@marvell.com
Cc: thomas@monjalon.net, hemant.agrawal@nxp.com,
mingshan.zhang@intel.com, arun.joshi@intel.com
Subject: Re: [dpdk-dev] [PATCH v3 3/6] bbdev: add capability for 4G CB CRC DROP
Date: Sun, 12 Sep 2021 05:39:48 -0700 [thread overview]
Message-ID: <6fbc24fb-2174-e286-76a7-15ad3a22715d@redhat.com> (raw)
In-Reply-To: <1631063741-28631-4-git-send-email-nicolas.chautru@intel.com>
On 9/7/21 6:15 PM, Nicolas Chautru wrote:
> Adding option to drop CRC24B to align with existing
> feature for 5G
>
> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> ---
> app/test-bbdev/test_bbdev_vector.c | 2 ++
> lib/bbdev/rte_bbdev_op.h | 5 ++++-
> 2 files changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/app/test-bbdev/test_bbdev_vector.c b/app/test-bbdev/test_bbdev_vector.c
> index 8d796b1..f020836 100644
> --- a/app/test-bbdev/test_bbdev_vector.c
> +++ b/app/test-bbdev/test_bbdev_vector.c
> @@ -149,6 +149,8 @@
> *op_flag_value = RTE_BBDEV_TURBO_DEC_SCATTER_GATHER;
> else if (!strcmp(token, "RTE_BBDEV_TURBO_DEC_TB_CRC_24B_KEEP"))
> *op_flag_value = RTE_BBDEV_TURBO_DEC_TB_CRC_24B_KEEP;
> + else if (!strcmp(token, "RTE_BBDEV_TURBO_DEC_CRC_24B_DROP"))
> + *op_flag_value = RTE_BBDEV_TURBO_DEC_CRC_24B_DROP;
> else {
> printf("The given value is not a turbo decoder flag\n");
> return -1;
> diff --git a/lib/bbdev/rte_bbdev_op.h b/lib/bbdev/rte_bbdev_op.h
> index 7c44ddd..5512859 100644
> --- a/lib/bbdev/rte_bbdev_op.h
> +++ b/lib/bbdev/rte_bbdev_op.h
> @@ -114,7 +114,10 @@ enum rte_bbdev_op_td_flag_bitmasks {
> /** Set to keep CRC24B bits appended while decoding. Only usable when
> * decoding Transport Block mode.
> */
> - RTE_BBDEV_TURBO_DEC_TB_CRC_24B_KEEP = (1ULL << 16)
> + RTE_BBDEV_TURBO_DEC_TB_CRC_24B_KEEP = (1ULL << 16),
> + /** Set to drop CRC24B bits not to be appended while decoding.
> + */
> + RTE_BBDEV_TURBO_DEC_CRC_24B_DROP = (1ULL << 17)
> };
>
>
This is ok, thanks.
Reviewed-by: Tom Rix <trix@redhat.com>
next prev parent reply other threads:[~2021-09-12 12:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 1:15 [dpdk-dev] [PATCH v3 0/6] bbdev update related to CRC usage Nicolas Chautru
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 1/6] bbdev: add capability for CRC16 check Nicolas Chautru
2021-09-12 12:35 ` Tom Rix
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 2/6] baseband/turbo_sw: add support for CRC16 Nicolas Chautru
2021-09-12 12:38 ` Tom Rix
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 3/6] bbdev: add capability for 4G CB CRC DROP Nicolas Chautru
2021-09-12 12:39 ` Tom Rix [this message]
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 4/6] baseband/acc100: add support for 4G CRC drop Nicolas Chautru
2021-09-12 12:42 ` Tom Rix
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 5/6] doc: clarification of usage of HARQ in bbdev doc Nicolas Chautru
2021-09-12 12:44 ` Tom Rix
2021-10-11 20:29 ` Thomas Monjalon
2021-10-11 20:33 ` Chautru, Nicolas
2021-09-08 1:15 ` [dpdk-dev] [PATCH v3 6/6] bbdev: reduce warning level for one scenario Nicolas Chautru
2021-09-12 12:54 ` Tom Rix
2021-09-13 17:03 ` Chautru, Nicolas
2021-09-13 20:01 ` Tom Rix
2021-10-04 23:40 ` Chautru, Nicolas
2021-10-05 10:05 ` 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=6fbc24fb-2174-e286-76a7-15ad3a22715d@redhat.com \
--to=trix@redhat.com \
--cc=arun.joshi@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=mingshan.zhang@intel.com \
--cc=nicolas.chautru@intel.com \
--cc=thomas@monjalon.net \
/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.