DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tom Rix <trix@redhat.com>
To: "Chautru, Nicolas" <nicolas.chautru@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"gakhil@marvell.com" <gakhil@marvell.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
	"Zhang, Mingshan" <mingshan.zhang@intel.com>,
	"Joshi, Arun" <arun.joshi@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/6] bbdev: add capability for CRC16 check
Date: Sat, 11 Sep 2021 12:11:38 -0700	[thread overview]
Message-ID: <f08ea83d-c497-9d5f-527a-a0b36f2aa1e1@redhat.com> (raw)
In-Reply-To: <BY5PR11MB4451D1660EEAB4658467CB45F8CD9@BY5PR11MB4451.namprd11.prod.outlook.com>


On 9/1/21 8:00 AM, Chautru, Nicolas wrote:
>
>> -----Original Message-----
>> From: Tom Rix <trix@redhat.com>
>> Sent: Wednesday, September 1, 2021 6:37 AM
>> To: Chautru, Nicolas <nicolas.chautru@intel.com>; dev@dpdk.org;
>> gakhil@marvell.com
>> Cc: thomas@monjalon.net; hemant.agrawal@nxp.com; Zhang, Mingshan
>> <mingshan.zhang@intel.com>; Joshi, Arun <arun.joshi@intel.com>
>> Subject: Re: [PATCH v2 1/6] bbdev: add capability for CRC16 check
>>
>>
>> On 8/19/21 2:10 PM, Nicolas Chautru wrote:
>>> Adding a missing operation when CRC16
>>> is being used for TB CRC check.
>>>
>>> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
>>> ---
>>>    app/test-bbdev/test_bbdev_vector.c     |  2 ++
>>>    doc/guides/prog_guide/bbdev.rst        |  3 +++
>>>    doc/guides/rel_notes/release_21_11.rst |  1 +
>>>    lib/bbdev/rte_bbdev_op.h               | 34 ++++++++++++++++++--------------
>> --
>>>    4 files changed, 24 insertions(+), 16 deletions(-)
>>>
>>> diff --git a/app/test-bbdev/test_bbdev_vector.c
>>> b/app/test-bbdev/test_bbdev_vector.c
>>> index 614dbd1..8d796b1 100644
>>> --- a/app/test-bbdev/test_bbdev_vector.c
>>> +++ b/app/test-bbdev/test_bbdev_vector.c
>>> @@ -167,6 +167,8 @@
>>>    		*op_flag_value = RTE_BBDEV_LDPC_CRC_TYPE_24B_CHECK;
>>>    	else if (!strcmp(token, "RTE_BBDEV_LDPC_CRC_TYPE_24B_DROP"))
>>>    		*op_flag_value = RTE_BBDEV_LDPC_CRC_TYPE_24B_DROP;
>>> +	else if (!strcmp(token, "RTE_BBDEV_LDPC_CRC_TYPE_16_CHECK"))
>>> +		*op_flag_value = RTE_BBDEV_LDPC_CRC_TYPE_16_CHECK;
>>>    	else if (!strcmp(token,
>> "RTE_BBDEV_LDPC_DEINTERLEAVER_BYPASS"))
>>>    		*op_flag_value =
>> RTE_BBDEV_LDPC_DEINTERLEAVER_BYPASS;
>>>    	else if (!strcmp(token,
>> "RTE_BBDEV_LDPC_HQ_COMBINE_IN_ENABLE"))
>>> diff --git a/doc/guides/prog_guide/bbdev.rst
>>> b/doc/guides/prog_guide/bbdev.rst index 9619280..8bd7cba 100644
>>> --- a/doc/guides/prog_guide/bbdev.rst
>>> +++ b/doc/guides/prog_guide/bbdev.rst
>>> @@ -891,6 +891,9 @@ given below.
>>>    |RTE_BBDEV_LDPC_CRC_TYPE_24B_DROP                                    |
>>>    | Set to drop the last CRC bits decoding output                      |
>>>
>>> +--------------------------------------------------------------------+
>>> +|RTE_BBDEV_LDPC_CRC_TYPE_16_CHECK                                    |
>>> +| Set for code block CRC-16 checking                                 |
>>> ++--------------------------------------------------------------------+
>>>    |RTE_BBDEV_LDPC_DEINTERLEAVER_BYPASS                                 |
>>>    | Set for bit-level de-interleaver bypass on input stream            |
>>>
>>> +--------------------------------------------------------------------+
>>> diff --git a/doc/guides/rel_notes/release_21_11.rst
>>> b/doc/guides/rel_notes/release_21_11.rst
>>> index d707a55..69dd518 100644
>>> --- a/doc/guides/rel_notes/release_21_11.rst
>>> +++ b/doc/guides/rel_notes/release_21_11.rst
>>> @@ -84,6 +84,7 @@ API Changes
>>>       Also, make sure to start the actual text at the margin.
>>>       =======================================================
>>>
>>> +* bbdev: Added capability related to more comprehensive CRC options.
>>>
>>>    ABI Changes
>>>    -----------
>>> diff --git a/lib/bbdev/rte_bbdev_op.h b/lib/bbdev/rte_bbdev_op.h index
>>> f946842..7c44ddd 100644
>>> --- a/lib/bbdev/rte_bbdev_op.h
>>> +++ b/lib/bbdev/rte_bbdev_op.h
>>> @@ -142,51 +142,53 @@ enum rte_bbdev_op_ldpcdec_flag_bitmasks {
>>>    	RTE_BBDEV_LDPC_CRC_TYPE_24B_CHECK = (1ULL << 1),
>>>    	/** Set to drop the last CRC bits decoding output */
>>>    	RTE_BBDEV_LDPC_CRC_TYPE_24B_DROP = (1ULL << 2),
>>> +	/** Set for transport block CRC-16 checking */
>>> +	RTE_BBDEV_LDPC_CRC_TYPE_16_CHECK = (1ULL << 3),
>> Changing these enums will break the abi backwards.
>>
>> Why not add the new one at the end ?
> To keep all the CRC related flags next to each other for better readability and logical clarity. The ABI is still marked as experimental.

Ok

>
>> Tom
>>
>>>    	/** Set for bit-level de-interleaver bypass on Rx stream. */
>>> -	RTE_BBDEV_LDPC_DEINTERLEAVER_BYPASS = (1ULL << 3),
>>> +	RTE_BBDEV_LDPC_DEINTERLEAVER_BYPASS = (1ULL << 4),
>>>    	/** Set for HARQ combined input stream enable. */
>>> -	RTE_BBDEV_LDPC_HQ_COMBINE_IN_ENABLE = (1ULL << 4),
>>> +	RTE_BBDEV_LDPC_HQ_COMBINE_IN_ENABLE = (1ULL << 5),
>>>    	/** Set for HARQ combined output stream enable. */
>>> -	RTE_BBDEV_LDPC_HQ_COMBINE_OUT_ENABLE = (1ULL << 5),
>>> +	RTE_BBDEV_LDPC_HQ_COMBINE_OUT_ENABLE = (1ULL << 6),
>>>    	/** Set for LDPC decoder bypass.
>>>    	 *  RTE_BBDEV_LDPC_HQ_COMBINE_OUT_ENABLE must be set.
>>>    	 */
>>> -	RTE_BBDEV_LDPC_DECODE_BYPASS = (1ULL << 6),
>>> +	RTE_BBDEV_LDPC_DECODE_BYPASS = (1ULL << 7),
>>>    	/** Set for soft-output stream enable */
>>> -	RTE_BBDEV_LDPC_SOFT_OUT_ENABLE = (1ULL << 7),
>>> +	RTE_BBDEV_LDPC_SOFT_OUT_ENABLE = (1ULL << 8),
>>>    	/** Set for Rate-Matching bypass on soft-out stream. */
>>> -	RTE_BBDEV_LDPC_SOFT_OUT_RM_BYPASS = (1ULL << 8),
>>> +	RTE_BBDEV_LDPC_SOFT_OUT_RM_BYPASS = (1ULL << 9),
>>>    	/** Set for bit-level de-interleaver bypass on soft-output stream. */
>>> -	RTE_BBDEV_LDPC_SOFT_OUT_DEINTERLEAVER_BYPASS = (1ULL <<
>> 9),
>>> +	RTE_BBDEV_LDPC_SOFT_OUT_DEINTERLEAVER_BYPASS = (1ULL <<
>> 10),
>>>    	/** Set for iteration stopping on successful decode condition
>>>    	 *  i.e. a successful syndrome check.
>>>    	 */
>>> -	RTE_BBDEV_LDPC_ITERATION_STOP_ENABLE = (1ULL << 10),
>>> +	RTE_BBDEV_LDPC_ITERATION_STOP_ENABLE = (1ULL << 11),
>>>    	/** Set if a device supports decoder dequeue interrupts. */
>>> -	RTE_BBDEV_LDPC_DEC_INTERRUPTS = (1ULL << 11),
>>> +	RTE_BBDEV_LDPC_DEC_INTERRUPTS = (1ULL << 12),
>>>    	/** Set if a device supports scatter-gather functionality. */
>>> -	RTE_BBDEV_LDPC_DEC_SCATTER_GATHER = (1ULL << 12),
>>> +	RTE_BBDEV_LDPC_DEC_SCATTER_GATHER = (1ULL << 13),
>>>    	/** Set if a device supports input/output HARQ compression. */
>>> -	RTE_BBDEV_LDPC_HARQ_6BIT_COMPRESSION = (1ULL << 13),
>>> +	RTE_BBDEV_LDPC_HARQ_6BIT_COMPRESSION = (1ULL << 14),
>>>    	/** Set if a device supports input LLR compression. */
>>> -	RTE_BBDEV_LDPC_LLR_COMPRESSION = (1ULL << 14),
>>> +	RTE_BBDEV_LDPC_LLR_COMPRESSION = (1ULL << 15),
>>>    	/** Set if a device supports HARQ input from
>>>    	 *  device's internal memory.
>>>    	 */
>>> -	RTE_BBDEV_LDPC_INTERNAL_HARQ_MEMORY_IN_ENABLE = (1ULL
>> << 15),
>>> +	RTE_BBDEV_LDPC_INTERNAL_HARQ_MEMORY_IN_ENABLE = (1ULL
>> << 16),
>>>    	/** Set if a device supports HARQ output to
>>>    	 *  device's internal memory.
>>>    	 */
>>> -	RTE_BBDEV_LDPC_INTERNAL_HARQ_MEMORY_OUT_ENABLE =
>> (1ULL << 16),
>>> +	RTE_BBDEV_LDPC_INTERNAL_HARQ_MEMORY_OUT_ENABLE =
>> (1ULL << 17),
>>>    	/** Set if a device supports loop-back access to
>>>    	 *  HARQ internal memory. Intended for troubleshooting.
>>>    	 */
>>> -	RTE_BBDEV_LDPC_INTERNAL_HARQ_MEMORY_LOOPBACK = (1ULL
>> << 17),
>>> +	RTE_BBDEV_LDPC_INTERNAL_HARQ_MEMORY_LOOPBACK = (1ULL
>> << 18),
>>>    	/** Set if a device includes LLR filler bits in the circular buffer
>>>    	 *  for HARQ memory. If not set, it is assumed the filler bits are not
>>>    	 *  in HARQ memory and handled directly by the LDPC decoder.
>>>    	 */
>>> -	RTE_BBDEV_LDPC_INTERNAL_HARQ_MEMORY_FILLERS = (1ULL <<
>> 18)
>>> +	RTE_BBDEV_LDPC_INTERNAL_HARQ_MEMORY_FILLERS = (1ULL <<
>> 19)
>>>    };
>>>
>>>    /** Flags for LDPC encoder operation and capability structure */


  reply	other threads:[~2021-09-11 19:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19 21:10 [dpdk-dev] [PATCH v2 0/6] bbdev update related to CRC usage Nicolas Chautru
2021-08-19 21:10 ` [dpdk-dev] [PATCH v2 1/6] bbdev: add capability for CRC16 check Nicolas Chautru
2021-09-01 13:36   ` Tom Rix
2021-09-01 15:00     ` Chautru, Nicolas
2021-09-11 19:11       ` Tom Rix [this message]
2021-08-19 21:10 ` [dpdk-dev] [PATCH v2 2/6] baseband/turbo_sw: add support for CRC16 Nicolas Chautru
2021-09-01 14:00   ` Tom Rix
2021-09-08  0:54     ` Chautru, Nicolas
2021-08-19 21:10 ` [dpdk-dev] [PATCH v2 3/6] bbdev: add capability for 4G CB CRC DROP Nicolas Chautru
2021-08-19 21:10 ` [dpdk-dev] [PATCH v2 4/6] baseband/acc100: add support for 4G CRC drop Nicolas Chautru
2021-09-01 14:20   ` Tom Rix
2021-09-08  1:04     ` Chautru, Nicolas
2021-09-11 19:13       ` Tom Rix
2021-08-19 21:10 ` [dpdk-dev] [PATCH v2 5/6] doc: clarification of usage of HARQ in bbdev doc Nicolas Chautru
2021-08-19 21:10 ` [dpdk-dev] [PATCH v2 6/6] bbdev: reduce warning level for one scenario Nicolas Chautru
2021-08-20  2:15   ` Zhang, Mingshan
2021-09-01 14:29   ` Tom Rix
2021-09-08  1:12     ` Chautru, Nicolas

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=f08ea83d-c497-9d5f-527a-a0b36f2aa1e1@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 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).