From: Tom Rix <trix@redhat.com>
To: "Chautru, Nicolas" <nicolas.chautru@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Liu, Tianjiao" <tianjiao.liu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: add reference to companion configuration tool
Date: Tue, 3 Nov 2020 11:07:34 -0800 [thread overview]
Message-ID: <c7c912a5-de57-30f8-ff31-f9842209047b@redhat.com> (raw)
In-Reply-To: <BY5PR11MB4451EABE8BEC45AFE5724691F8110@BY5PR11MB4451.namprd11.prod.outlook.com>
On 11/3/20 7:58 AM, Chautru, Nicolas wrote:
>
>> -----Original Message-----
>> From: Tom Rix <trix@redhat.com>
>> Sent: Tuesday, November 3, 2020 7:07 AM
>> To: Chautru, Nicolas <nicolas.chautru@intel.com>; dev@dpdk.org;
>> akhil.goyal@nxp.com; thomas@monjalon.net
>> Cc: Mcnamara, John <john.mcnamara@intel.com>;
>> david.marchand@redhat.com; Richardson, Bruce
>> <bruce.richardson@intel.com>; Liu, Tianjiao <tianjiao.liu@intel.com>
>> Subject: Re: [PATCH v2] doc: add reference to companion configuration tool
>>
>>
>> On 11/2/20 12:53 PM, Nicolas Chautru wrote:
>>> Adding reference to pf_bb_config in github to do device configuration
>>> of the fpga_5gnr, fpga_lte and
>>> acc100 devices and pmds.
>>>
>>> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
>>> ---
>>> doc/guides/bbdevs/acc100.rst | 19 +++++++++++++++++++
>>> doc/guides/bbdevs/fpga_5gnr_fec.rst | 19 +++++++++++++++++++
>>> doc/guides/bbdevs/fpga_lte_fec.rst | 19 +++++++++++++++++++
>>> 3 files changed, 57 insertions(+)
>>>
>>> diff --git a/doc/guides/bbdevs/acc100.rst
>>> b/doc/guides/bbdevs/acc100.rst index 7a23c16..b772854 100644
>>> --- a/doc/guides/bbdevs/acc100.rst
>>> +++ b/doc/guides/bbdevs/acc100.rst
>>> @@ -223,3 +223,22 @@ In addition to the simple LDPC decoder and LDPC
>>> encoder tests, bbdev also provid a range of additional tests under
>>> the test_vectors folder, which may be useful. The results of these
>>> tests will depend on the ACC100 5G/4G FEC capabilities which may cause
>> some testcases to be skipped, but no failure should be reported.
>>> +
>>> +
>>> +Alternate Baseband Device configuration tool
>>> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> +
>>> +On top of the embedded configuration feature supported in test-bbdev
>> using "- -init-device"
>>> +option mentioned above, there is also a tool available to perform
>>> +that device configuration using a companion application.
>>> +The ``pf_bb_config`` application notably enables then to run
>>> +bbdev-test from the VF and not only limited to the PF as captured above.
>>> +
>>> +See for more details: https://github.com/intel/pf-bb-config
>>> +
>>> +Specifically for the BBDEV ACC100 PMD, the command below can be
>> used:
>>> +
>>> +.. code-block:: console
>>> +
>>> + ./pf_bb_config ACC100 -c acc100/acc100_config_vf_5g.cfg
>>> + ./test-bbdev.py -e="-c 0xff0 -w${VF_PCI_ADDR}" -c validation -n 64
>>> + -b 32 -l 1 -v ./ldpc_dec_default.data
>>> diff --git a/doc/guides/bbdevs/fpga_5gnr_fec.rst
>>> b/doc/guides/bbdevs/fpga_5gnr_fec.rst
>>> index 61c19c3..78c1ce7 100644
>>> --- a/doc/guides/bbdevs/fpga_5gnr_fec.rst
>>> +++ b/doc/guides/bbdevs/fpga_5gnr_fec.rst
>>> @@ -286,3 +286,22 @@ Test Vectors
>>> In addition to the simple LDPC decoder and LDPC encoder tests, bbdev
>>> also provides a range of additional tests under the test_vectors
>>> folder, which may be useful. The results of these tests will depend on the
>> FPGA 5GNR FEC capabilities.
>>> +
>>> +
>>> +Alternate Baseband Device configuration tool
>>> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> +
>>> +On top of the embedded configuration feature supported in test-bbdev
>> using "- -init-device"
>>> +option, there is also a tool available to perform that device
>>> +configuration using a companion application.
>>> +The ``pf_bb_config`` application notably enables then to run
>>> +bbdev-test from the VF and not only limited to the PF as captured above.
>>> +
>>> +See for more details: https://github.com/intel/pf-bb-config
>>> +
>>> +Specifically for the BBDEV FPGA 5GNR FEC PMD, the command below can
>> be used:
>>> +
>>> +.. code-block:: console
>>> +
>>> +
>>> + ./test-bbdev.py -e="-c 0xff0 -w${VF_PCI_ADDR}" -c validation -n 64
>>> + -b 32 -l 1 -v ./ldpc_dec_default.data
>>> diff --git a/doc/guides/bbdevs/fpga_lte_fec.rst
>>> b/doc/guides/bbdevs/fpga_lte_fec.rst
>>> index 9d64e15..a1b3e33 100644
>>> --- a/doc/guides/bbdevs/fpga_lte_fec.rst
>>> +++ b/doc/guides/bbdevs/fpga_lte_fec.rst
>>> @@ -305,3 +305,22 @@ of these tests will depend on the FPGA LTE FEC
>> capabilities:
>>> - ``turbo_enc_c2_k5952_r0_e17868_crc24b.data``
>>> - ``turbo_enc_c3_k4800_r2_e14412_crc24b.data``
>>> - ``turbo_enc_c4_k4800_r2_e14412_crc24b.data``
>>> +
>>> +
>>> +Alternate Baseband Device configuration tool
>>> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> +
>>> +On top of the embedded configuration feature supported in test-bbdev
>> using "- -init-device"
>>> +option, there is also a tool available to perform that device
>>> +configuration using a companion application.
>>> +The ``pf_bb_config`` application notably enables then to run
>>> +bbdev-test from the VF and not only limited to the PF as captured above.
>>> +
>>> +See for more details: https://github.com/intel/pf-bb-config
>>> +
>>> +Specifically for the BBDEV FPGA LTE FEC PMD, the command below can
>> be used:
>>> +
>>> +.. code-block:: console
>>> +
>>> + ./pf_bb_config FPGA_lte -c fpga_lte/fpga_lte_config_vf.cfg
>> From inspection, pf_bb_config does not care about the case of FPGA_lte
> What do you mean?
comparing the call examples in the doc
./pf_bb_config ACC100 -c acc100/acc100_config_vf_5g.cfg
./pf_bb_config FPGA_5GNR -c fpga_5gnr/fpga_5gnr_config_vf.cfg
./pf_bb_config FPGA_lte -c fpga_lte/fpga_lte_config_vf.cfg
For consistency, the last should use FPGA_LTE
Tom
>
>> However for documentation, it is best if these examples are consistent.
>>
>> So this should be
>>
>> ./pf_bb_config FPGA_LTE ...
>>
>> Tom
>>
>>
>>> + ./test-bbdev.py -e="-c 0xff0 -w${VF_PCI_ADDR}" -c validation -n 64
>>> + -b 32 -l 1 -v ./turbo_dec_default.data
next prev parent reply other threads:[~2020-11-03 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 20:53 [dpdk-dev] [PATCH v2] doc: add reference to bbdev " Nicolas Chautru
2020-11-02 20:53 ` [dpdk-dev] [PATCH v2] doc: add reference to " Nicolas Chautru
2020-11-03 15:06 ` Tom Rix
2020-11-03 15:58 ` Chautru, Nicolas
2020-11-03 19:07 ` Tom Rix [this message]
2020-11-03 19:34 ` 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=c7c912a5-de57-30f8-ff31-f9842209047b@redhat.com \
--to=trix@redhat.com \
--cc=akhil.goyal@nxp.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=nicolas.chautru@intel.com \
--cc=thomas@monjalon.net \
--cc=tianjiao.liu@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).