From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 660B9A0471 for ; Thu, 18 Jul 2019 15:28:02 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 2944C1DBE; Thu, 18 Jul 2019 15:28:02 +0200 (CEST) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 0E983F04 for ; Thu, 18 Jul 2019 15:27:59 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Jul 2019 06:27:59 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,278,1559545200"; d="scan'208";a="176019043" Received: from skx-5gnr-sc12-4.sc.intel.com ([172.25.69.210]) by FMSMGA003.fm.intel.com with ESMTP; 18 Jul 2019 06:27:56 -0700 From: Nicolas Chautru To: dev@dpdk.org, thomas@monjalon.net, john.mcnamara@intel.com, marko.kovacevic@intel.com Cc: Nicolas Chautru Date: Wed, 17 Jul 2019 23:24:39 -0700 Message-Id: <1563431079-14170-1-git-send-email-nicolas.chautru@intel.com> X-Mailer: git-send-email 1.8.3.1 Subject: [dpdk-dev] [PATCH] doc: fix PDF build of bbdev prog guide X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Some machine (like on dpdk.org) may fail to build the prog guide PDF because of the complex table inserted in the bbdev chapter. Fixes: 3f3f608142cf ("doc: update bbdev guide for 5GNR operations") Signed-off-by: Nicolas Chautru --- doc/guides/prog_guide/bbdev.rst | 32 ++++++++++++++++---------------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/doc/guides/prog_guide/bbdev.rst b/doc/guides/prog_guide/bbdev.rst index ef05dcb..6c0bb3c 100644 --- a/doc/guides/prog_guide/bbdev.rst +++ b/doc/guides/prog_guide/bbdev.rst @@ -800,21 +800,21 @@ The LDPC encode parameters are set out in the table below. |op_flags |bitmask of all active operation capabilities | +----------------+--------------------------------------------------------------------+ |**cb_params** |code block specific parameters (code block mode only) | -+----------------+------------+-------------------------------------------------------+ -| |e |E, length of the rate matched output sequence in bits | -+----------------+------------+-------------------------------------------------------+ ++----------------+--------------------------------------------------------------------+ +|e |E, length of the rate matched output sequence in bits | ++----------------+--------------------------------------------------------------------+ |**tb_params** | transport block specific parameters (transport block mode only) | -+----------------+------------+-------------------------------------------------------+ -| |c |number of CBs in the TB or partial TB | -+----------------+------------+-------------------------------------------------------+ -| |r |index of the first CB in the inbound mbuf data | -+----------------+------------+-------------------------------------------------------+ -+ +c_ab +number of CBs that use Ea before switching to Eb | -+----------------+------------+-------------------------------------------------------+ -| |ea |Ea, length of the RM output sequence in bits, r < cab | -+----------------+------------+-------------------------------------------------------+ -| |eb |Eb, length of the RM output sequence in bits, r >= cab | -+----------------+------------+-------------------------------------------------------+ ++----------------+--------------------------------------------------------------------+ +|c |number of CBs in the TB or partial TB | ++----------------+--------------------------------------------------------------------+ +|r |index of the first CB in the inbound mbuf data | ++----------------+--------------------------------------------------------------------+ ++c_ab +number of CBs that use Ea before switching to Eb | ++----------------+--------------------------------------------------------------------+ +|ea |Ea, length of the RM output sequence in bits, r < cab | ++----------------+--------------------------------------------------------------------+ +|eb |Eb, length of the RM output sequence in bits, r >= cab | ++----------------+--------------------------------------------------------------------+ The mbuf input ``input`` is mandatory for all BBDEV PMDs and is the incoming code block or transport block data. @@ -865,7 +865,7 @@ calculated by BBDEV before signalling to the driver. The number of CBs in the group should not be confused with ``c``, the total number of CBs in the full TB (``C`` as per 3GPP TS 38.212 section 5.2.2) -Figure 13.1 above showing the Turbo encoding of CBs using BBDEV +Figure :numref:`figure_turbo_tb_encode` above showing the Turbo encoding of CBs using BBDEV interface in TB-mode is also valid for LDPC encode. BBDEV LDPC Decode Operation @@ -1077,7 +1077,7 @@ total number of CBs in the full TB (``C`` as per 3GPP TS 38.212 section 5.2.2) The ``length`` is total size of the CBs inclusive of any CRC24A and CRC24B in case they were appended by the application. -Figure 13.2 above showing the Turbo decoding of CBs using BBDEV +Figure :numref:`figure_turbo_tb_decode` above showing the Turbo decoding of CBs using BBDEV interface in TB-mode is also valid for LDPC decode. -- 1.8.3.1