DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, gakhil@marvell.com
Cc: thomas@monjalon.net, trix@redhat.com, hemant.agrawal@nxp.com,
	mingshan.zhang@intel.com, arun.joshi@intel.com,
	Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [dpdk-dev] [PATCH v3 5/6] doc: clarification of usage of HARQ in bbdev doc
Date: Tue,  7 Sep 2021 18:15:40 -0700	[thread overview]
Message-ID: <1631063741-28631-6-git-send-email-nicolas.chautru@intel.com> (raw)
In-Reply-To: <1631063741-28631-1-git-send-email-nicolas.chautru@intel.com>

New paragraph detailing typical VRAN usecase and mapping
to bbdev API usage.

Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
---
 doc/guides/prog_guide/bbdev.rst | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/doc/guides/prog_guide/bbdev.rst b/doc/guides/prog_guide/bbdev.rst
index 8bd7cba..f39b62f 100644
--- a/doc/guides/prog_guide/bbdev.rst
+++ b/doc/guides/prog_guide/bbdev.rst
@@ -1054,6 +1054,29 @@ capability RTE_BBDEV_LDPC_INTERNAL_HARQ_MEMORY_OUT_ENABLE is set
 then the HARQ is stored in memory internal to the device and not visible
 to BBDEV.
 
+.. note::
+    More explicitly for a typical usage of HARQ retransmission in a VRAN
+    application using a HW PMD, there will be 2 cases.
+
+    For 1st transmission, only the HARQ output is enabled :
+
+    - the harq_combined_output.offset is provided to a given address. ie. typically an integer index * 32K, where the index is tracked by the application based on code block index for a given UE and HARQ process.
+
+    - the related operation flag would notably include RTE_BBDEV_LDPC_HQ_COMBINE_OUT_ENABLE and RTE_BBDEV_LDPC_HARQ_6BIT_COMPRESSION.
+
+    - note that not explicit flush or reset of the memory is required.
+
+    For 2nd transmission, an input is also required to benefit from HARQ combination gain:
+
+    - the changes mentioned above are the same (note that rvIndex may be adjusted).
+
+    - the operation flag would additionally include the LDPC_HQ_COMBINE_IN_ENABLE flag.
+
+    - the harq_combined_input.offset must set to the address of the related code block (ie. same as the harq_combine_output index above for the same code block, HARQ process, UE).
+
+    - the harq_combined_input.length must be set to the length which was provided back in the related harq_combined_output.length when it has processed and dequeued (previous HARQ iteration).
+
+
 The output mbuf data structures are expected to be allocated by the
 application with enough room for the output data.
 
-- 
1.8.3.1


  parent reply	other threads:[~2021-09-08  1:16 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
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 ` Nicolas Chautru [this message]
2021-09-12 12:44   ` [dpdk-dev] [PATCH v3 5/6] doc: clarification of usage of HARQ in bbdev doc 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=1631063741-28631-6-git-send-email-nicolas.chautru@intel.com \
    --to=nicolas.chautru@intel.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=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 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).