X-Git-Url: http://git.droids-corp.org/?a=blobdiff_plain;f=doc%2Fguides%2Fnics%2Fdpaa2.rst;h=ca6ba5b5e2910b4a2978e4d9fd4ccccfce15c311;hb=1736219b3c5737c943620c22121b361e35b18d0d;hp=a698e5ab653826f031cc9ebc2339a52aa556a1a2;hpb=d629b7b5fe812f0040b83d27d2ada33b003aa918;p=dpdk.git diff --git a/doc/guides/nics/dpaa2.rst b/doc/guides/nics/dpaa2.rst index a698e5ab65..ca6ba5b5e2 100644 --- a/doc/guides/nics/dpaa2.rst +++ b/doc/guides/nics/dpaa2.rst @@ -1,5 +1,5 @@ .. SPDX-License-Identifier: BSD-3-Clause - Copyright 2016 NXP + Copyright 2016,2020 NXP DPAA2 Poll Mode Driver @@ -300,7 +300,7 @@ The diagram below shows the dpaa2 drivers involved in a networking scenario and the objects bound to each driver. A brief description of each driver follows. -.. code-block: console +.. code-block:: console +------------+ @@ -421,8 +421,8 @@ See :doc:`../platform/dpaa2` for setup information Currently supported by DPDK: -- NXP LSDK **19.03+**. -- MC Firmware version **10.14.0** and higher. +- NXP LSDK **19.08+**. +- MC Firmware version **10.18.0** and higher. - Supported architectures: **arm64 LE**. - Follow the DPDK :ref:`Getting Started Guide for Linux ` to setup the basic DPDK environment. @@ -441,21 +441,19 @@ Config File Options The following options can be modified in the ``config`` file. Please note that enabling debugging options may affect system performance. -- ``CONFIG_RTE_LIBRTE_FSLMC_BUS`` (default ``n``) +- ``CONFIG_RTE_LIBRTE_FSLMC_BUS`` (default ``y``) - By default it is enabled only for defconfig_arm64-dpaa2-* config. Toggle compilation of the ``librte_bus_fslmc`` driver. -- ``CONFIG_RTE_LIBRTE_DPAA2_PMD`` (default ``n``) +- ``CONFIG_RTE_LIBRTE_DPAA2_PMD`` (default ``y``) - By default it is enabled only for defconfig_arm64-dpaa2-* config. Toggle compilation of the ``librte_pmd_dpaa2`` driver. - ``CONFIG_RTE_LIBRTE_DPAA2_DEBUG_DRIVER`` (default ``n``) Toggle display of debugging messages/logic -- ``CONFIG_RTE_LIBRTE_DPAA2_USE_PHYS_IOVA`` (default ``y``) +- ``CONFIG_RTE_LIBRTE_DPAA2_USE_PHYS_IOVA`` (default ``n``) Toggle to use physical address vs virtual address for hardware accelerators. @@ -504,6 +502,10 @@ for details. driver level. Any packet received will be reflected back by the driver on same port. e.g. ``fslmc:dpni.1,drv_loopback=1`` +* Use dev arg option ``drv_no_prefetch=1`` to disable prefetching + of the packet pull command which is issued in the previous cycle. + e.g. ``fslmc:dpni.1,drv_no_prefetch=1`` + Enabling logs ------------- @@ -536,6 +538,19 @@ For blacklisting a DPAA2 device, following commands can be used. Where x is the device object id as configured in resource container. +Running secondary debug app without blacklist +--------------------------------------------- + +dpaa2 hardware imposes limits on some H/W access devices like Management +Control Port and H/W portal. This causes issue in their shared usages in +case of multi-process applications. It can overcome by using +whitelist/blacklist in primary and secondary applications. + +In order to ease usage of standard debugging apps like dpdk-procinfo, dpaa2 +driver reserves extra Management Control Port and H/W portal which can be +used by debug application to debug any existing application without +blacklisting these devices in primary process. + Limitations -----------