net/vhost: fix potential memory leak on close

[dpdk.git] / doc / guides / eventdevs / dpaa.rst

diff --git a/doc/guides/eventdevs/dpaa.rst b/doc/guides/eventdevs/dpaa.rst
index 44ed128..be68c6d 100644 (file)
--- a/doc/guides/eventdevs/dpaa.rst
+++ b/doc/guides/eventdevs/dpaa.rst
@@ -25,57 +25,17 @@ The DPAA EVENTDEV implements many features in the eventdev API;
 Supported DPAA SoCs
 --------------------
 
 Supported DPAA SoCs
 --------------------
 

-- LS1046A
-- LS1043A
+- LS1046A/LS1026A
+- LS1043A/LS1023A

 
 Prerequisites
 -------------
 
 
 Prerequisites
 -------------
 

-There are following pre-requisites for executing EVENTDEV on a DPAA compatible
-platform:
-
-1. **ARM 64 Tool Chain**
-
-  For example, the `*aarch64* Linaro Toolchain <https://releases.linaro.org/components/toolchain/binaries/6.4-2017.08/aarch64-linux-gnu/>`_.
-
-2. **Linux Kernel**
-
-   It can be obtained from `NXP's Github hosting <https://github.com/qoriq-open-source/linux>`_.
-
-3. **Rootfile System**
-
-   Any *aarch64* supporting filesystem can be used. For example,
-   Ubuntu 15.10 (Wily) or 16.04 LTS (Xenial) userland which can be obtained
-   from `here <http://cdimage.ubuntu.com/ubuntu-base/releases/16.04/release/ubuntu-base-16.04.1-base-arm64.tar.gz>`_.
-
-As an alternative method, DPAA EVENTDEV can also be executed using images provided
-as part of SDK from NXP. The SDK includes all the above prerequisites necessary
-to bring up a DPAA board.
-
-The following dependencies are not part of DPDK and must be installed
-separately:
-
-- **NXP Linux SDK**
-
-  NXP Linux software development kit (SDK) includes support for family
-  of QorIQ® ARM-Architecture-based system on chip (SoC) processors
-  and corresponding boards.
-
-  It includes the Linux board support packages (BSPs) for NXP SoCs,
-  a fully operational tool chain, kernel and board specific modules.
-
-  SDK and related information can be obtained from:  `NXP QorIQ SDK  <http://www.nxp.com/products/software-and-tools/run-time-software/linux-sdk/linux-sdk-for-qoriq-processors:SDKLINUX>`_.
-
-- **DPDK Extra Scripts**
-
-  DPAA based resources can be configured easily with the help of ready to use
-  xml files as provided in the DPDK Extra repository.
-
-  `DPDK Extras Scripts <https://github.com/qoriq-open-source/dpdk-extras>`_.
+See :doc:`../platform/dpaa` for setup information

 
 Currently supported by DPDK:
 
 
 Currently supported by DPDK:
 

-- NXP SDK **2.0+** or LSDK **17.09+**
+- NXP SDK **2.0+** or LSDK **18.09+**

 - Supported architectures:  **arm64 LE**.
 
 - Follow the DPDK :ref:`Getting Started Guide for Linux <linux_gsg>` to setup the basic DPDK environment.
 - Supported architectures:  **arm64 LE**.
 
 - Follow the DPDK :ref:`Getting Started Guide for Linux <linux_gsg>` to setup the basic DPDK environment.


@@ -102,7 +62,7 @@ following ``make`` command:
 .. code-block:: console
 
    cd <DPDK-source-directory>
 .. code-block:: console
 
    cd <DPDK-source-directory>

-   make config T=arm64-dpaa-linuxapp-gcc install
+   make config T=arm64-dpaa-linux-gcc install

 
 Initialization
 --------------
 
 Initialization
 --------------


@@ -111,16 +71,18 @@ The dpaa eventdev is exposed as a vdev device which consists of a set of channel
 and queues. On EAL initialization, dpaa components will be
 probed and then vdev device can be created from the application code by
 
 and queues. On EAL initialization, dpaa components will be
 probed and then vdev device can be created from the application code by
 

-* Invoking ``rte_vdev_init("event_dpaa")`` from the application
+* Invoking ``rte_vdev_init("event_dpaa1")`` from the application

 
 

-* Using ``--vdev="event_dpaa"`` in the EAL options, which will call
+* Using ``--vdev="event_dpaa1"`` in the EAL options, which will call

   rte_vdev_init() internally
 
 Example:
 
 .. code-block:: console
 
   rte_vdev_init() internally
 
 Example:
 
 .. code-block:: console
 

-    ./your_eventdev_application --vdev="event_dpaa"
+    ./your_eventdev_application --vdev="event_dpaa1"
+
+* Use dev arg option ``disable_intr=1`` to disable the interrupt mode

 
 Limitations
 -----------
 
 Limitations
 -----------