doc: update qede PMD guide
Checks
Commit Message
- Add note for Co-existence of DPDK and Linux drivers.
- Update the firmware version in example.
- Add Config note for potential error due to lack of memzone desciptor
count.
Signed-off-by: Rasesh Mody <rmody@marvell.com>
---
doc/guides/nics/qede.rst | 25 ++++++++++++++++++++-----
1 file changed, 20 insertions(+), 5 deletions(-)
Comments
On 11/22/2019 7:51 AM, Rasesh Mody wrote:
> - Add note for Co-existence of DPDK and Linux drivers.
> - Update the firmware version in example.
> - Add Config note for potential error due to lack of memzone desciptor
> count.
>
> Signed-off-by: Rasesh Mody <rmody@marvell.com>
> ---
> doc/guides/nics/qede.rst | 25 ++++++++++++++++++++-----
> 1 file changed, 20 insertions(+), 5 deletions(-)
>
> diff --git a/doc/guides/nics/qede.rst b/doc/guides/nics/qede.rst
> index 2f4045795..9c14dd006 100644
> --- a/doc/guides/nics/qede.rst
> +++ b/doc/guides/nics/qede.rst
> @@ -70,6 +70,10 @@ Co-existence considerations
> to the PFs of a given adapter and either qede PMD or Linux drivers
> (qed and qede) can be bound to the VFs of the adapter.
>
> +- To use DPDK on some PFs and Linux drivers on other PFs of an adapter,
> + create a VF each on the PFs where DPDK will be used, attach DPDK to
> + these VFs and Linux drivers to the other PFs where no VFs are created.
But this won't be using DPDK on some PFs, you are indeed suggesting to create
VFs and use them via DPDK instead. And should the PF not bound to any kernel driver?
Hi Ferruh,
>From: Ferruh Yigit <ferruh.yigit@intel.com>
>Sent: Friday, November 22, 2019 6:33 AM
>
>External Email
>
>----------------------------------------------------------------------
>On 11/22/2019 7:51 AM, Rasesh Mody wrote:
>> - Add note for Co-existence of DPDK and Linux drivers.
>> - Update the firmware version in example.
>> - Add Config note for potential error due to lack of memzone desciptor
>> count.
>>
>> Signed-off-by: Rasesh Mody <rmody@marvell.com>
>> ---
>> doc/guides/nics/qede.rst | 25 ++++++++++++++++++++-----
>> 1 file changed, 20 insertions(+), 5 deletions(-)
>>
>> diff --git a/doc/guides/nics/qede.rst b/doc/guides/nics/qede.rst index
>> 2f4045795..9c14dd006 100644
>> --- a/doc/guides/nics/qede.rst
>> +++ b/doc/guides/nics/qede.rst
>> @@ -70,6 +70,10 @@ Co-existence considerations
>> to the PFs of a given adapter and either qede PMD or Linux drivers
>> (qed and qede) can be bound to the VFs of the adapter.
>>
>> +- To use DPDK on some PFs and Linux drivers on other PFs of an
>> +adapter,
>> + create a VF each on the PFs where DPDK will be used, attach DPDK to
>> + these VFs and Linux drivers to the other PFs where no VFs are created.
>
>But this won't be using DPDK on some PFs, you are indeed suggesting to
>create VFs and use them via DPDK instead. And should the PF not bound to
>any kernel driver?
For sharing an adapter between DPDK and Linux drivers, we are suggesting to use DPDK on a VF created on PFs. All the PFs would be bound to Linux drivers(qed/qede). I'll send out a v2 with modified text for more clarity.
Thanks!
-Rasesh
@@ -70,6 +70,10 @@ Co-existence considerations
to the PFs of a given adapter and either qede PMD or Linux drivers
(qed and qede) can be bound to the VFs of the adapter.
+- To use DPDK on some PFs and Linux drivers on other PFs of an adapter,
+ create a VF each on the PFs where DPDK will be used, attach DPDK to
+ these VFs and Linux drivers to the other PFs where no VFs are created.
+
Supported QLogic Adapters
-------------------------
@@ -82,9 +86,7 @@ Prerequisites
inbox in certain newer Linux distros under the standard directory
``E.g. /lib/firmware/qed/qed_init_values-8.40.33.0.bin``.
If the required firmware files are not available then download it from
- `linux-firmware git repository <http://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qed>`_
- or `QLogic Driver Download Center <http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/DefaultNewSearch.aspx>`_.
- To download firmware file from QLogic website, select adapter category, model and DPDK Poll Mode Driver.
+ `linux-firmware git repository <http://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qed>`_.
- Requires the NIC be updated minimally with **8.30.x.x** Management firmware(MFW) version supported for that NIC.
It is highly recommended that the NIC be updated with the latest available management firmware version to get latest feature set.
@@ -99,7 +101,6 @@ Prerequisites
`QLogic Driver Download Center <http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/DefaultNewSearch.aspx>`_.
For downloading PF driver, select adapter category, model and Linux distro.
-
Performance note
~~~~~~~~~~~~~~~~
@@ -126,12 +127,26 @@ enabling debugging options may affect system performance.
- ``CONFIG_RTE_LIBRTE_QEDE_FW`` (default **""**)
Gives absolute path of firmware file.
- ``Eg: "/lib/firmware/qed/qed_init_values-8.37.7.0.bin"``
+ ``Eg: "/lib/firmware/qed/qed_init_values-8.40.33.0.bin"``
Empty string indicates driver will pick up the firmware file
from the default location /lib/firmware/qed.
CAUTION this option is more for custom firmware, it is not
recommended for use under normal condition.
+Config notes
+~~~~~~~~~~~~
+
+When there are multiple adapters and/or large number of Rx/Tx queues
+configured on the adapters, the default (2560) number of memzone
+descriptors may not be enough. Please increase the number of memzone
+descriptors to a higher number as needed. When sufficient number of
+memzone descriptors are not configured, user can potentially run into
+following error.
+
+ .. code-block:: console
+
+ EAL: memzone_reserve_aligned_thread_unsafe(): No more room in config
+
Driver compilation and testing
------------------------------