remove make support in DPDK
Subsystems (12)
PATCH v3 29/37 doc: remove references to make in NIC guides
In reply to Ciara PowerMake is no longer supported for compiling DPDK, references are now removed in the documentation.
--- doc/guides/nics/ark.rst | 26 ------------- doc/guides/nics/atlantic.rst | 4 -- doc/guides/nics/axgbe.rst | 15 -------- doc/guides/nics/bnx2x.rst | 27 ------------- doc/guides/nics/bnxt.rst | 5 +-- doc/guides/nics/build_and_test.rst | 8 +++- doc/guides/nics/cxgbe.rst | 36 +++++------------ doc/guides/nics/dpaa.rst | 27 +------------ doc/guides/nics/dpaa2.rst | 26 +------------ doc/guides/nics/ena.rst | 16 -------- doc/guides/nics/enetc.rst | 2 - doc/guides/nics/enic.rst | 9 ----- doc/guides/nics/fail_safe.rst | 20 ++-------- doc/guides/nics/features.rst | 9 ----- doc/guides/nics/fm10k.rst | 4 -- doc/guides/nics/hinic.rst | 9 ----- doc/guides/nics/hns3.rst | 10 ----- doc/guides/nics/i40e.rst | 44 ++++++--------------- doc/guides/nics/ice.rst | 25 ++---------- doc/guides/nics/igc.rst | 18 +-------- doc/guides/nics/intel_vf.rst | 13 +------ doc/guides/nics/ionic.rst | 8 ---- doc/guides/nics/ipn3ke.rst | 12 +----- doc/guides/nics/kni.rst | 4 +- doc/guides/nics/liquidio.rst | 27 ------------- doc/guides/nics/memif.rst | 10 ++--- doc/guides/nics/mlx4.rst | 55 ++------------------------ doc/guides/nics/mlx5.rst | 62 ++---------------------------- doc/guides/nics/mvneta.rst | 36 ++++------------- doc/guides/nics/mvpp2.rst | 43 ++++----------------- doc/guides/nics/nfb.rst | 19 +-------- doc/guides/nics/nfp.rst | 4 -- doc/guides/nics/null.rst | 6 +-- doc/guides/nics/octeontx.rst | 19 +-------- doc/guides/nics/octeontx2.rst | 13 +------ doc/guides/nics/pcap_ring.rst | 24 ++++++------ doc/guides/nics/qede.rst | 17 +------- doc/guides/nics/sfc_efx.rst | 15 -------- doc/guides/nics/softnic.rst | 13 +------ doc/guides/nics/szedata2.rst | 18 +-------- doc/guides/nics/thunderx.rst | 25 +----------- doc/guides/nics/vdev_netvsc.rst | 6 --- doc/guides/nics/vhost.rst | 2 +- doc/guides/nics/virtio.rst | 4 +- 44 files changed, 102 insertions(+), 693 deletions(-)
doc/guides/nics/ark.rst +0 -26
@@ -119,32 +119,6 @@ Data Path Interface Ingress RX and Egress TX operation is by the nominal DPDK API . The driver supports single-port, multi-queue for both RX and TX. -Configuration Information -------------------------- - -**DPDK Configuration Parameters** - - The following configuration options are available for the ARK PMD: - - * **CONFIG_RTE_LIBRTE_ARK_PMD** (default y): Enables or disables inclusion - of the ARK PMD driver in the DPDK compilation. - - * **CONFIG_RTE_LIBRTE_ARK_PAD_TX** (default y): When enabled TX - packets are padded to 60 bytes to support downstream MACS. - - * **CONFIG_RTE_LIBRTE_ARK_DEBUG_RX** (default n): Enables or disables debug - logging and internal checking of RX ingress logic within the ARK PMD driver. - - * **CONFIG_RTE_LIBRTE_ARK_DEBUG_TX** (default n): Enables or disables debug - logging and internal checking of TX egress logic within the ARK PMD driver. - - * **CONFIG_RTE_LIBRTE_ARK_DEBUG_STATS** (default n): Enables or disables debug - logging of detailed packet and performance statistics gathered in - the PMD and FPGA. - - * **CONFIG_RTE_LIBRTE_ARK_DEBUG_TRACE** (default n): Enables or disables debug - logging of detailed PMD events and status. - Building DPDK -------------
doc/guides/nics/atlantic.rst +0 -4
@@ -26,10 +26,6 @@ Experimental API features - MACSEC PMD API is considered as experimental and is subject to change/removal in next DPDK releases. -Configuration Information -^^^^^^^^^^^^^^^^^^^^^^^^^ - -- ``CONFIG_RTE_LIBRTE_ATLANTIC_PMD`` (default ``y``) Application Programming Interface ---------------------------------
doc/guides/nics/axgbe.rst +0 -15
@@ -27,21 +27,6 @@ AXGBE PMD has support for: - Jumbo Frame up to 9K -Configuration Information -------------------------- - -The following options can be modified in the ``.config`` file. Please note that -enabling debugging options may affect system performance. - -- ``CONFIG_RTE_LIBRTE_AXGBE_PMD`` (default **y**) - - Toggle compilation of axgbe PMD. - -- ``CONFIG_RTE_LIBRTE_AXGBE_PMD_DEBUG`` (default **n**) - - Toggle display for PMD debug related messages. - - Building DPDK -------------
doc/guides/nics/bnx2x.rst +0 -27
@@ -72,33 +72,6 @@ Prerequisites `linux-firmware git repository <https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/bnx2x/bnx2x-e2-7.13.11.0.fw>`_ to get the required firmware. -Pre-Installation Configuration ------------------------------- - -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_BNX2X_PMD`` (default **n**) - - Toggle compilation of bnx2x driver. To use bnx2x PMD set this config parameter - to 'y'. Also, in order for firmware binary to load user will need zlib devel - package installed. - -- ``CONFIG_RTE_LIBRTE_BNX2X_DEBUG_TX`` (default **n**) - - Toggle display of transmit fast path run-time messages. - -- ``CONFIG_RTE_LIBRTE_BNX2X_DEBUG_RX`` (default **n**) - - Toggle display of receive fast path run-time messages. - -- ``CONFIG_RTE_LIBRTE_BNX2X_DEBUG_PERIODIC`` (default **n**) - - Toggle display of register reads and writes. - .. _bnx2x_driver-compilation:
doc/guides/nics/bnxt.rst +1 -4
@@ -565,9 +565,6 @@ The BNXT PMD supports a PTP client application to communicate with a PTP master clock using DPDK IEEE1588 APIs. Note that the PTP client application needs to run on PF and vector mode needs to be disabled. -For the PTP time synchronization support, the BNXT PMD must be compiled with -``CONFIG_RTE_LIBRTE_IEEE1588=y`` (this compilation flag is currently pending). - .. code-block:: console testpmd> set fwd ieee1588 // enable IEEE 1588 mode
@@ -612,7 +609,7 @@ Basic stats include: * oerrors By default, per-queue stats for 16 queues are supported. For more than 16 -queues, BNXT PMD should be compiled with ``CONFIG_RTE_ETHDEV_QUEUE_STAT_CNTRS`` +queues, BNXT PMD should be compiled with ``RTE_ETHDEV_QUEUE_STAT_CNTRS`` set to the desired number of queues. Extended Stats
doc/guides/nics/build_and_test.rst +6 -2
@@ -66,10 +66,14 @@ This section demonstrates how to setup and run ``testpmd`` in Linux. #. Load ``igb_uio`` or ``vfio-pci`` driver: + Before compiling, make sure to enable kmods for the meson build:: + + meson configure -Denable_kmods=true + .. code-block:: console modprobe uio - insmod ./x86_64-native-linux-gcc/kmod/igb_uio.ko + insmod ./<build_dir>/kernel/linux/igb_uio/igb_uio.ko or
@@ -106,7 +110,7 @@ This section demonstrates how to setup and run ``testpmd`` in Linux. .. code-block:: console - ./x86_64-native-linux-gcc/app/testpmd -l 0-3 -n 4 -- -i + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 -- -i Successful execution will show initialization messages from EAL, PMD and testpmd application. A prompt will be displayed at the end for user commands
doc/guides/nics/cxgbe.rst +10 -26
@@ -87,35 +87,19 @@ Prerequisites :ref:`linux-installation` for Linux and section :ref:`freebsd-installation` for FreeBSD. -Pre-Installation Configuration ------------------------------- - -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_CXGBE_PMD`` (default **y**) - - Toggle compilation of librte_pmd_cxgbe driver. - - .. note:: - - This controls compilation of both CXGBE and CXGBEVF PMD. Runtime Options -~~~~~~~~~~~~~~~ +--------------- The following ``devargs`` options can be enabled at runtime. They must be passed as part of EAL arguments. For example, .. code-block:: console - testpmd -w 02:00.4,keep_ovlan=1 -- -i + dpdk-testpmd -w 02:00.4,keep_ovlan=1 -- -i Common Runtime Options -^^^^^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~~~~~ - ``keep_ovlan`` (default **0**)
@@ -133,7 +117,7 @@ Common Runtime Options coalesce limit has been reached. CXGBE VF Only Runtime Options -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - ``force_link_up`` (default **0**)
@@ -142,7 +126,7 @@ CXGBE VF Only Runtime Options to send traffic to each other even when the physical link is down. CXGBE PF Only Runtime Options -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - ``filtermode`` (default **0**)
@@ -317,7 +301,7 @@ CXGBE PF Only Runtime Options .. code-block:: console - testpmd -w 02:00.4,filtermode=0x88 -- -i + dpdk-testpmd -w 02:00.4,filtermode=0x88 -- -i - ``filtermask`` (default **0**)
@@ -344,7 +328,7 @@ CXGBE PF Only Runtime Options .. code-block:: console - testpmd -w 02:00.4,filtermode=0x88,filtermask=0x80 -- -i + dpdk-testpmd -w 02:00.4,filtermode=0x88,filtermask=0x80 -- -i .. _driver-compilation:
@@ -689,7 +673,7 @@ devices managed by librte_pmd_cxgbe in FreeBSD operating system. .. code-block:: console - cp x86_64-native-freebsd-clang/kmod/contigmem.ko /boot/kernel/ + cp <build_dir>/kernel/freebsd/contigmem.ko /boot/kernel/ #. Add the following lines to /boot/loader.conf:
@@ -770,13 +754,13 @@ devices managed by librte_pmd_cxgbe in FreeBSD operating system. .. code-block:: console - kldload ./x86_64-native-freebsd-clang/kmod/nic_uio.ko + kldload <build_dir>/kernel/freebsd/nic_uio.ko #. Start testpmd with basic parameters: .. code-block:: console - ./x86_64-native-freebsd-clang/app/testpmd -l 0-3 -n 4 -w 0000:02:00.4 -- -i + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 -w 0000:02:00.4 -- -i Example output:
doc/guides/nics/dpaa.rst +1 -26
@@ -195,31 +195,6 @@ See :doc:`../platform/dpaa` for setup information Pre-Installation Configuration ------------------------------ -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_DPAA_BUS`` (default ``y``) - - Toggle compilation of the ``librte_bus_dpaa`` driver. - -- ``CONFIG_RTE_LIBRTE_DPAA_PMD`` (default ``y``) - - Toggle compilation of the ``librte_pmd_dpaa`` driver. - -- ``CONFIG_RTE_LIBRTE_DPAA_DEBUG_DRIVER`` (default ``n``) - - Toggles display of bus configurations and enables a debugging queue - to fetch error (Rx/Tx) packets to driver. By default, packets with errors - (like wrong checksum) are dropped by the hardware. - -- ``CONFIG_RTE_LIBRTE_DPAA_HWDEBUG`` (default ``n``) - - Enables debugging of the Queue and Buffer Manager layer which interacts - with the DPAA hardware. - Environment Variables ~~~~~~~~~~~~~~~~~~~~~
@@ -264,7 +239,7 @@ for details. .. code-block:: console - ./arm64-dpaa-linux-gcc/testpmd -c 0xff -n 1 \ + ./<build_dir>/app/dpdk-testpmd -c 0xff -n 1 \ -- -i --portmask=0x3 --nb-cores=1 --no-flush-rx .....
doc/guides/nics/dpaa2.rst +1 -25
@@ -432,30 +432,6 @@ Currently supported by DPDK: Some part of fslmc bus code (mc flib - object library) routines are dual licensed (BSD & GPLv2), however they are used as BSD in DPDK in userspace. -Pre-Installation Configuration ------------------------------- - -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 ``y``) - - Toggle compilation of the ``librte_bus_fslmc`` driver. - -- ``CONFIG_RTE_LIBRTE_DPAA2_PMD`` (default ``y``) - - 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 ``n``) - - Toggle to use physical address vs virtual address for hardware accelerators. Driver compilation and testing ------------------------------
@@ -473,7 +449,7 @@ for details. .. code-block:: console - ./testpmd -c 0xff -n 1 -- -i --portmask=0x3 --nb-cores=1 --no-flush-rx + ./dpdk-testpmd -c 0xff -n 1 -- -i --portmask=0x3 --nb-cores=1 --no-flush-rx ..... EAL: Registered [pci] bus.
doc/guides/nics/ena.rst +0 -16
@@ -79,22 +79,6 @@ The driver supports multi-queue for both Tx and Rx. Configuration information ------------------------- -**DPDK Configuration Parameters** - - The following configuration options are available for the ENA PMD: - - * **CONFIG_RTE_LIBRTE_ENA_PMD** (default y): Enables or disables inclusion - of the ENA PMD driver in the DPDK compilation. - - * **CONFIG_RTE_LIBRTE_ENA_DEBUG_RX** (default n): Enables or disables debug - logging of RX logic within the ENA PMD driver. - - * **CONFIG_RTE_LIBRTE_ENA_DEBUG_TX** (default n): Enables or disables debug - logging of TX logic within the ENA PMD driver. - - * **CONFIG_RTE_LIBRTE_ENA_COM_DEBUG** (default n): Enables or disables debug - logging of low level tx/rx logic in ena_com(base) within the ENA PMD driver. - **Runtime Configuration Parameters** * **large_llq_hdr** (default 0)
doc/guides/nics/enetc.rst +0 -2
@@ -113,5 +113,3 @@ Driver compilation and testing Follow instructions available in the document :ref:`compiling and testing a PMD for a NIC <pmd_build_and_test>` to launch **testpmd** - -To compile in performance mode, please set ``CONFIG_RTE_CACHE_LINE_SIZE=64``
doc/guides/nics/enic.rst +0 -9
@@ -20,13 +20,6 @@ should be downloaded from https://core.dpdk.org/download/ Configuration information ------------------------- -- **DPDK Configuration Parameters** - - The following configuration options are available for the ENIC PMD: - - - **CONFIG_RTE_LIBRTE_ENIC_PMD** (default y): Enables or disables inclusion - of the ENIC PMD driver in the DPDK compilation. - - **vNIC Configuration Parameters** - **Number of Queues**
@@ -583,8 +576,6 @@ The value depends on the memory configuration of the application, DPDK and PMD. Typically, the limit has to be raised to higher than 2GB. e.g., 2621440 -The compilation of any unused drivers can be disabled using the -configuration file in config/ directory (e.g., config/common_linux). This would help in bringing down the time taken for building the libraries and the initialization time of the application.
doc/guides/nics/fail_safe.rst +4 -16
@@ -14,10 +14,6 @@ Additionally to the Seamless Hotplug feature, the Fail-safe PMD offers the ability to redirect operations to a secondary device when the primary has been removed from the system. -.. note:: - - The library is enabled by default. You can enable it or disable it manually - by setting the ``CONFIG_RTE_LIBRTE_PMD_FAILSAFE`` configuration option. Features --------
@@ -33,14 +29,6 @@ automatically by detecting capable devices and registering the relevant handler. Check the feature matrix for the complete set of supported features. -Compilation option ------------------- - -Available options within the ``$RTE_TARGET/build/.config`` file: - -- ``CONFIG_RTE_LIBRTE_PMD_FAILSAFE`` (default **y**) - - This option enables or disables compiling librte_pmd_failsafe. Using the Fail-safe PMD from the EAL command line -------------------------------------------------
@@ -128,7 +116,7 @@ This section shows some example of using **testpmd** with a fail-safe PMD. .. code-block:: console - $RTE_TARGET/build/app/testpmd -c 0xff -n 4 \ + ./<build_dir>/app/dpdk-testpmd -c 0xff -n 4 \ --vdev 'net_failsafe0,mac=de:ad:be:ef:01:02,dev(84:00.0),dev(net_ring0)' \ -b 84:00.0 -b 00:04.0 -- -i
@@ -142,7 +130,7 @@ This section shows some example of using **testpmd** with a fail-safe PMD. .. code-block:: console - $RTE_TARGET/build/app/testpmd -c 0xff -n 4 \ + ./<build_dir>/app/dpdk-testpmd -c 0xff -n 4 \ --vdev 'net_failsafe0,mac=de:ad:be:ef:01:02,dev(84:00.0),dev(net_ring0)' \ -w 81:00.0 -- -i
@@ -150,7 +138,7 @@ This section shows some example of using **testpmd** with a fail-safe PMD. .. code-block:: console - $RTE_TARGET/build/app/testpmd -c 0xff -n 4 -w ff:ff.f \ + ./<build_dir>/app/dpdk-testpmd -c 0xff -n 4 -w ff:ff.f \ --vdev='net_failsafe0,exec(echo 84:00.0)' -- -i #. Start testpmd, automatically probing the device 84:00.0 and using it with
@@ -158,7 +146,7 @@ This section shows some example of using **testpmd** with a fail-safe PMD. .. code-block:: console - $RTE_TARGET/build/app/testpmd -c 0xff -n 4 \ + ./<build_dir>/app/dpdk-testpmd -c 0xff -n 4 \ --vdev 'net_failsafe0,dev(0000:84:00.0),dev(net_ring0)' -- -i
doc/guides/nics/features.rst +0 -9
@@ -812,8 +812,6 @@ ARMv7 Support armv7 architecture. -Use ``defconfig_arm-armv7a-*-*``. - .. _nic_features_armv8:
@@ -822,8 +820,6 @@ ARMv8 Support armv8a (64bit) architecture. -Use ``defconfig_arm64-armv8a-*-*`` - .. _nic_features_power8:
@@ -832,7 +828,6 @@ Power8 Support PowerPC architecture. -Use ``defconfig_ppc_64-power8-*-*`` .. _nic_features_x86-32:
@@ -841,8 +836,6 @@ x86-32 Support 32bits x86 architecture. -Use ``defconfig_x86_x32-native-*-*`` and ``defconfig_i686-native-*-*``. - .. _nic_features_x86-64:
@@ -851,8 +844,6 @@ x86-64 Support 64bits x86 architecture. -Use ``defconfig_x86_64-native-*-*``. - .. _nic_features_usage_doc:
doc/guides/nics/fm10k.rst +0 -4
@@ -35,10 +35,6 @@ There is no change to the PMD API. The RX/TX handlers are the only two entries f vPMD packet I/O. They are transparently registered at runtime RX/TX execution if all required conditions are met. -1. To date, only an SSE version of FM10K vPMD is available. - To ensure that vPMD is in the binary code, set - ``CONFIG_RTE_LIBRTE_FM10K_INC_VECTOR=y`` in the configure file. - Some constraints apply as pre-conditions for specific optimizations on bulk packet transfers. The following sections explain RX and TX constraints in the vPMD.
doc/guides/nics/hinic.rst +0 -9
@@ -46,15 +46,6 @@ Prerequisites - Follow the DPDK :ref:`Getting Started Guide for Linux <linux_gsg>` to setup the basic DPDK environment. -Pre-Installation Configuration ------------------------------- - -Config File Options -~~~~~~~~~~~~~~~~~~~ - -The following options can be modified in the ``config`` file. - -- ``CONFIG_RTE_LIBRTE_HINIC_PMD`` (default ``y``) Driver compilation and testing ------------------------------
doc/guides/nics/hns3.rst +0 -10
@@ -44,16 +44,6 @@ Prerequisites - Follow the DPDK :ref:`Getting Started Guide for Linux <linux_gsg>` to setup the basic DPDK environment. -Pre-Installation Configuration ------------------------------- - -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_HNS3_PMD`` (default ``y``) Driver compilation and testing ------------------------------
doc/guides/nics/i40e.rst +12 -32
84 lines not on this page · raw message
doc/guides/nics/ice.rst +4 -21
@@ -23,23 +23,6 @@ Prerequisites Pre-Installation Configuration ------------------------------ -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_ICE_PMD`` (default ``y``) - - Toggle compilation of the ``librte_pmd_ice`` driver. - -- ``CONFIG_RTE_LIBRTE_ICE_DEBUG_*`` (default ``n``) - - Toggle display of generic debugging messages. - -- ``CONFIG_RTE_LIBRTE_ICE_16BYTE_RX_DESC`` (default ``n``) - - Toggle to use a 16-byte RX descriptor, by default the RX descriptor is 32 byte. Runtime Config Options ~~~~~~~~~~~~~~~~~~~~~~
@@ -106,14 +89,14 @@ Runtime Config Options .. code-block:: console - testpmd -w 18:00.0,proto_xtr='[(1,2-3,8-9):tcp,10-13:vlan]' + dpdk-testpmd -w 18:00.0,proto_xtr='[(1,2-3,8-9):tcp,10-13:vlan]' This setting means queues 1, 2-3, 8-9 are TCP extraction, queues 10-13 are VLAN extraction, other queues run with no protocol extraction. .. code-block:: console - testpmd -w 18:00.0,proto_xtr=vlan,proto_xtr='[(1,2-3,8-9):tcp,10-23:ipv6]' + dpdk-testpmd -w 18:00.0,proto_xtr=vlan,proto_xtr='[(1,2-3,8-9):tcp,10-23:ipv6]' This setting means queues 1, 2-3, 8-9 are TCP extraction, queues 10-23 are IPv6 extraction, other queues use the default VLAN extraction.
@@ -253,7 +236,7 @@ responses for the same from PF. #. Bind the VF0, and run testpmd with 'cap=dcf' devarg:: - testpmd -l 22-25 -n 4 -w 18:01.0,cap=dcf -- -i + dpdk-testpmd -l 22-25 -n 4 -w 18:01.0,cap=dcf -- -i #. Monitor the VF2 interface network traffic::
@@ -282,7 +265,7 @@ To start ``testpmd``, and add vlan 10 to port 0: .. code-block:: console - ./app/testpmd -l 0-15 -n 4 -- -i + ./app/dpdk-testpmd -l 0-15 -n 4 -- -i ... testpmd> rx_vlan add 10 0
doc/guides/nics/igc.rst +2 -16
@@ -11,20 +11,6 @@ I225 Series Network Adapters. `https://ark.intel.com/content/www/us/en/ark/products/series/184686/ intel-ethernet-controller-i225-series.html` -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_IGC_PMD`` (default ``y``) - - Toggle compilation of the ``librte_pmd_igc`` driver. - -- ``CONFIG_RTE_LIBRTE_IGC_DEBUG_*`` (default ``n``) - - Toggle display of generic debugging messages. - Driver compilation and testing ------------------------------
@@ -67,7 +53,7 @@ outer VLAN to 0x9100: .. code-block:: console - ./app/testpmd -l 4-8 -- -i + ./app/dpdk-testpmd -l 4-8 -- -i ... testpmd> vlan set filter on 0
@@ -94,7 +80,7 @@ Start ``testpmd``: .. code-block:: console - ./testpmd -l 4-8 -- i --rxq=4 --txq=4 --pkt-filter-mode=perfect --disable-rss + ./dpdk-testpmd -l 4-8 -- i --rxq=4 --txq=4 --pkt-filter-mode=perfect --disable-rss Add a rule to direct packet whose ``ether-type=0x801`` to queue 1:
doc/guides/nics/intel_vf.rst +2 -11
@@ -124,7 +124,6 @@ Intel® X710/XL710 Gigabit Ethernet Controller VF Infrastructure In a virtualized environment, the programmer can enable a maximum of *128 Virtual Functions (VF)* globally per Intel® X710/XL710 Gigabit Ethernet Controller NIC device. -The number of queue pairs of each VF can be configured by ``CONFIG_RTE_LIBRTE_I40E_QUEUE_NUM_PER_VF`` in ``config`` file. The Physical Function in host could be either configured by the Linux* i40e driver (in the case of the Linux Kernel-based Virtual Machine [KVM]) or by DPDK PMD PF driver. When using both DPDK PMD PF/VF drivers, the whole NIC will be taken over by DPDK based application.
@@ -521,20 +520,12 @@ The setup procedure is as follows: .. code-block:: console - make install T=x86_64-native-linux-gcc - ./x86_64-native-linux-gcc/app/testpmd -l 0-3 -n 4 -- -i + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 -- -i #. Finally, access the Guest OS using vncviewer with the localhost:5900 port and check the lspci command output in the Guest OS. The virtual functions will be listed as available for use. -#. Configure and install the DPDK with an x86_64-native-linux-gcc configuration on the Guest OS as normal, - that is, there is no change to the normal installation procedure. - - .. code-block:: console - - make config T=x86_64-native-linux-gcc O=x86_64-native-linux-gcc - cd x86_64-native-linux-gcc - make +#. Configure and install the DPDK on the Guest OS as normal, that is, there is no change to the normal installation procedure. .. note::
doc/guides/nics/ionic.rst +0 -8
@@ -24,14 +24,6 @@ on the host, check for the PCI devices: b5:00.0 Ethernet controller: Device 1dd8:1002 b6:00.0 Ethernet controller: Device 1dd8:1002 -Pre-Installation Configuration ------------------------------- - -The following options can be modified in the ``config`` file. - -- ``CONFIG_RTE_LIBRTE_IONIC_PMD`` (default ``y``) - - Toggle compilation of ionic PMD. Building DPDK -------------
doc/guides/nics/ipn3ke.rst +2 -10
@@ -31,14 +31,6 @@ Prerequisites Pre-Installation Configuration ------------------------------ -Config File Options -~~~~~~~~~~~~~~~~~~~ - -The following options can be modified in the ``config`` file. - -- ``CONFIG_RTE_LIBRTE_IPN3KE_PMD`` (default ``y``) - - Toggle compilation of the ``librte_pmd_ipn3ke`` driver. Runtime Config Options ~~~~~~~~~~~~~~~~~~~~~~
@@ -85,7 +77,7 @@ To start ``testpmd``, and add I40e PF to FPGA network port: .. code-block:: console - ./app/testpmd -l 0-15 -n 4 --vdev 'ifpga_rawdev_cfg0,ifpga=b3:00.0,port=0' --vdev 'ipn3ke_cfg0,afu=0|b3:00.0,i40e_pf={0000:b1:00.0|0000:b1:00.1|0000:b1:00.2|0000:b1:00.3|0000:b5:00.0|0000:b5:00.1|0000:b5:00.2|0000:b5:00.3}' -- -i --no-numa --port-topology=loop + ./<build_dir>/app/dpdk-testpmd -l 0-15 -n 4 --vdev 'ifpga_rawdev_cfg0,ifpga=b3:00.0,port=0' --vdev 'ipn3ke_cfg0,afu=0|b3:00.0,i40e_pf={0000:b1:00.0|0000:b1:00.1|0000:b1:00.2|0000:b1:00.3|0000:b5:00.0|0000:b5:00.1|0000:b5:00.2|0000:b5:00.3}' -- -i --no-numa --port-topology=loop HQoS and flow acceleration ~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -96,7 +88,7 @@ To start ``testpmd``, and add I40e PF to FPGA network port, enable FPGA HQoS and .. code-block:: console - ./app/testpmd -l 0-15 -n 4 --vdev 'ifpga_rawdev_cfg0,ifpga=b3:00.0,port=0' --vdev 'ipn3ke_cfg0,afu=0|b3:00.0,fpga_acc={tm|flow},i40e_pf={0000:b1:00.0|0000:b1:00.1|0000:b1:00.2|0000:b1:00.3|0000:b5:00.0|0000:b5:00.1|0000:b5:00.2|0000:b5:00.3}' -- -i --no-numa --forward-mode=macswap + ./<build_dir>/app/dpdk-testpmd -l 0-15 -n 4 --vdev 'ifpga_rawdev_cfg0,ifpga=b3:00.0,port=0' --vdev 'ipn3ke_cfg0,afu=0|b3:00.0,fpga_acc={tm|flow},i40e_pf={0000:b1:00.0|0000:b1:00.1|0000:b1:00.2|0000:b1:00.3|0000:b5:00.0|0000:b5:00.1|0000:b5:00.2|0000:b5:00.3}' -- -i --no-numa --forward-mode=macswap Limitations or Known issues ---------------------------
doc/guides/nics/kni.rst +2 -2
@@ -97,13 +97,13 @@ It is possible to test PMD quickly using KNI kernel module loopback feature: .. code-block:: console - insmod build/kmod/rte_kni.ko lo_mode=lo_mode_fifo_skb + insmod <build_dir>/kernel/linux/kni/rte_kni.ko lo_mode=lo_mode_fifo_skb * Start testpmd with no physical device but two KNI virtual devices: .. code-block:: console - ./testpmd --vdev net_kni0 --vdev net_kni1 -- -i + ./dpdk-testpmd --vdev net_kni0 --vdev net_kni1 -- -i .. code-block:: console
doc/guides/nics/liquidio.rst +0 -27
@@ -20,33 +20,6 @@ Supported LiquidIO Adapters - LiquidIO II CN2360 210SVPT -Pre-Installation Configuration ------------------------------- - -The following options can be modified in the ``config`` file. -Please note that enabling debugging options may affect system performance. - -- ``CONFIG_RTE_LIBRTE_LIO_PMD`` (default ``y``) - - Toggle compilation of LiquidIO PMD. - -- ``CONFIG_RTE_LIBRTE_LIO_DEBUG_RX`` (default ``n``) - - Toggle display of receive fast path run-time messages. - -- ``CONFIG_RTE_LIBRTE_LIO_DEBUG_TX`` (default ``n``) - - Toggle display of transmit fast path run-time messages. - -- ``CONFIG_RTE_LIBRTE_LIO_DEBUG_MBOX`` (default ``n``) - - Toggle display of mailbox messages. - -- ``CONFIG_RTE_LIBRTE_LIO_DEBUG_REGS`` (default ``n``) - - Toggle display of register reads and writes. - - SR-IOV: Prerequisites and Sample Application Notes --------------------------------------------------
doc/guides/nics/memif.rst +5 -5
@@ -213,15 +213,15 @@ In this example we run two instances of testpmd application and transmit packets First create ``master`` interface:: - #./build/app/testpmd -l 0-1 --proc-type=primary --file-prefix=pmd1 --vdev=net_memif,role=master -- -i + #./<build_dir>/app/dpdk-testpmd -l 0-1 --proc-type=primary --file-prefix=pmd1 --vdev=net_memif,role=master -- -i Now create ``slave`` interface (master must be already running so the slave will connect):: - #./build/app/testpmd -l 2-3 --proc-type=primary --file-prefix=pmd2 --vdev=net_memif -- -i + #./<build_dir>/app/dpdk-testpmd -l 2-3 --proc-type=primary --file-prefix=pmd2 --vdev=net_memif -- -i You can also enable ``zero-copy`` on ``slave`` interface:: - #./build/app/testpmd -l 2-3 --proc-type=primary --file-prefix=pmd2 --vdev=net_memif,zero-copy=yes --single-file-segments -- -i + #./<build_dir>/app/dpdk-testpmd -l 2-3 --proc-type=primary --file-prefix=pmd2 --vdev=net_memif,zero-copy=yes --single-file-segments -- -i Start forwarding packets::
@@ -257,7 +257,7 @@ To see socket filename use show memif command:: Now create memif interface by running testpmd with these command line options:: - #./testpmd --vdev=net_memif,socket=/run/vpp/memif.sock -- -i + #./dpdk-testpmd --vdev=net_memif,socket=/run/vpp/memif.sock -- -i Testpmd should now create memif slave interface and try to connect to master. In testpmd set forward option to icmpecho and start forwarding::
@@ -280,7 +280,7 @@ The situation is analogous to cross connecting 2 ports of the NIC by cable. To set the loopback, just use the same socket and id with different roles:: - #./testpmd --vdev=net_memif0,role=master,id=0 --vdev=net_memif1,role=slave,id=0 -- -i + #./dpdk-testpmd --vdev=net_memif0,role=master,id=0 --vdev=net_memif1,role=slave,id=0 -- -i Then start the communication::
doc/guides/nics/mlx4.rst +3 -52
79 lines not on this page · raw message
doc/guides/nics/mlx5.rst +3 -59
86 lines not on this page · raw message
doc/guides/nics/mvneta.rst +8 -28
@@ -13,12 +13,6 @@ Detailed information about SoCs that use PPv2 can be obtained here: * https://www.marvell.com/embedded-processors/armada-3700/ -.. Note:: - - Due to external dependencies, this driver is disabled by default. It must - be enabled manually by setting relevant configuration option manually. - Please refer to `Config File Options`_ section for further details. - Features --------
@@ -81,20 +75,9 @@ Prerequisites Follow the DPDK :ref:`Getting Started Guide for Linux <linux_gsg>` to setup DPDK environment. -Pre-Installation Configuration ------------------------------- - -Config File Options -~~~~~~~~~~~~~~~~~~~ - -The following options can be modified in the ``config`` file. - -- ``CONFIG_RTE_LIBRTE_MVNETA_PMD`` (default ``n``) - - Toggle compilation of the librte_pmd_mvneta driver. Runtime options -~~~~~~~~~~~~~~~ +--------------- The following ``devargs`` options can be enabled at runtime. They must be passed as part of EAL arguments.
@@ -107,7 +90,7 @@ be passed as part of EAL arguments. .. code-block:: console - ./testpmd --vdev=net_mvneta,iface=eth0,iface=eth1 \ + ./dpdk-testpmd --vdev=net_mvneta,iface=eth0,iface=eth1 \ -c 3 -- -i --p 3 -a
@@ -126,16 +109,13 @@ Driver needs precompiled MUSDK library during compilation. MUSDK will be installed to `usr/local` under current directory. For the detailed build instructions please consult ``doc/musdk_get_started.txt``. -Before the DPDK build process the environmental variable ``LIBMUSDK_PATH`` with -the path to the MUSDK installation directory needs to be exported. +The path to the MUSDK installation directory needs to set in meson, shown in the +following command: .. code-block:: console - export LIBMUSDK_PATH=<musdk>/usr/local - export CROSS=aarch64-linux-gnu- - make config T=arm64-armv8a-linux-gcc - sed -ri 's,(MVNETA_PMD=)n,\1y,' build/.config - make + meson -Dlib_musdk_dir=/path/to/musdk build ninja -C build + Usage Example -------------
@@ -160,7 +140,7 @@ In order to run testpmd example application following command can be used: .. code-block:: console - ./testpmd --vdev=net_mvneta,iface=eth0,iface=eth1 -c 3 -- \ + ./dpdk-testpmd --vdev=net_mvneta,iface=eth0,iface=eth1 -c 3 -- \ -i --p 3 -a --txd 256 --rxd 128 --rxq=1 --txq=1 --nb-cores=1
@@ -168,4 +148,4 @@ In order to run l2fwd example application following command can be used: .. code-block:: console - ./l2fwd --vdev=net_mvneta,iface=eth0,iface=eth1 -c 3 -- -T 1 -p 3 + ./dpdk-l2fwd --vdev=net_mvneta,iface=eth0,iface=eth1 -c 3 -- -T 1 -p 3
doc/guides/nics/mvpp2.rst +8 -35
97 lines not on this page · raw message
doc/guides/nics/nfb.rst +2 -17
@@ -16,13 +16,6 @@ and used technology (`Netcope Development Kit <http://www.netcope.com/en/products/fpga-development-kit>`_) can be found on the `Netcope Technologies website <http://www.netcope.com/>`_. -.. note:: - - This driver has external dependencies. - Therefore it is disabled in default configuration files. - It can be enabled by setting ``CONFIG_RTE_LIBRTE_NFB_PMD=y`` - and recompiling. - .. note:: Currently the driver is supported only on x86_64 architectures.
@@ -62,14 +55,6 @@ The minimum version of the provided packages: Configuration ------------- -These configuration options can be modified before compilation in the -``.config`` file: - -* ``CONFIG_RTE_LIBRTE_NFB_PMD`` default value: **n** - - Value **y** enables compilation of nfb PMD. - - Timestamps The PMD supports hardware timestamps of frame receipt on physical network interface. In order to use
@@ -78,7 +63,7 @@ products) and the device argument `timestamp=1` must be used. .. code-block:: console - $RTE_TARGET/app/testpmd -w b3:00.0,timestamp=1 <other EAL params> -- <testpmd params> + ./<build_dir>/app/dpdk-testpmd -w b3:00.0,timestamp=1 <other EAL params> -- <testpmd params> When the timestamps are enabled with the *devarg*, a timestamp validity flag is set in the MBUFs containing received frames and timestamp is inserted into the `rte_mbuf` struct.
@@ -133,7 +118,7 @@ transmit queue: .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 2 \ + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 2 \ -- --port-topology=chained --rxq=2 --txq=2 --nb-cores=2 -i -a Example output:
doc/guides/nics/nfp.rst +0 -4
@@ -49,10 +49,6 @@ compile it along with other DPDK PMDs even if no BSP was installed previously. Of course, a DPDK app will require such a BSP installed for using the NFP PMD, along with a specific NFP firmware application. -Default PMD configuration is at the **common_linux configuration** file: - -- **CONFIG_RTE_LIBRTE_NFP_PMD=y** - Once the DPDK is built all the DPDK apps and examples include support for the NFP PMD.
doc/guides/nics/null.rst +3 -3
@@ -14,7 +14,7 @@ Usage .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 4 --vdev net_null0 --vdev net_null1 -- -i + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 --vdev net_null0 --vdev net_null1 -- -i Runtime Config Options
@@ -26,7 +26,7 @@ Runtime Config Options .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 4 --vdev "net_null0,copy=1" -- -i + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 --vdev "net_null0,copy=1" -- -i - ``size`` [optional, default=64 bytes]
@@ -35,7 +35,7 @@ Runtime Config Options .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 4 --vdev "net_null0,size=256" -- -i + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 --vdev "net_null0,size=256" -- -i - ``no-rx`` [optional, default disabled]
doc/guides/nics/octeontx.rst +1 -18
@@ -52,15 +52,6 @@ See :doc:`../platform/octeontx` for setup information. Pre-Installation Configuration ------------------------------ -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_OCTEONTX_PMD`` (default ``y``) - - Toggle compilation of the ``librte_pmd_octeontx`` driver. Driver compilation and testing ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -68,14 +59,6 @@ Driver compilation and testing Refer to the document :ref:`compiling and testing a PMD for a NIC <pmd_build_and_test>` for details. -To compile the OCTEON TX PMD for Linux arm64 gcc target, run the -following ``make`` command: - -.. code-block:: console - - cd <DPDK-source-directory> - make config T=arm64-thunderx-linux-gcc install - #. Running testpmd: Follow instructions available in the document
@@ -86,7 +69,7 @@ following ``make`` command: .. code-block:: console - ./arm64-thunderx-linux-gcc/app/testpmd -c 700 \ + ./<build_dir>/app/dpdk-testpmd -c 700 \ --base-virtaddr=0x100000000000 \ --mbuf-pool-ops-name="octeontx_fpavf" \ --vdev='event_octeontx' \
doc/guides/nics/octeontx2.rst +1 -12
@@ -46,14 +46,6 @@ Prerequisites See :doc:`../platform/octeontx2` for setup information. -Compile time Config Options ---------------------------- - -The following options may be modified in the ``config`` file. - -- ``CONFIG_RTE_LIBRTE_OCTEONTX2_PMD`` (default ``y``) - - Toggle compilation of the ``librte_pmd_octeontx2`` driver. Driver compilation and testing ------------------------------
@@ -61,9 +53,6 @@ Driver compilation and testing Refer to the document :ref:`compiling and testing a PMD for a NIC <pmd_build_and_test>` for details. -To compile the OCTEON TX2 PMD for Linux arm64 gcc, -use arm64-octeontx2-linux-gcc as target. - #. Running testpmd: Follow instructions available in the document
@@ -74,7 +63,7 @@ use arm64-octeontx2-linux-gcc as target. .. code-block:: console - ./build/app/testpmd -c 0x300 -w 0002:02:00.0 -- --portmask=0x1 --nb-cores=1 --port-topology=loop --rxq=1 --txq=1 + ./<build_dir>/app/dpdk-testpmd -c 0x300 -w 0002:02:00.0 -- --portmask=0x1 --nb-cores=1 --port-topology=loop --rxq=1 --txq=1 EAL: Detected 24 lcore(s) EAL: Detected 1 NUMA nodes EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
doc/guides/nics/pcap_ring.rst +11 -13
@@ -15,10 +15,8 @@ the DPDK also includes pure-software PMDs, two of these drivers are: .. note:: - The libpcap -based PMD is disabled by default in the build configuration files, - owing to an external dependency on the libpcap development files which must be installed on the board. - Once the libpcap development files are installed, - the library can be enabled by setting CONFIG_RTE_LIBRTE_PMD_PCAP=y and recompiling the DPDK. + The libpcap -based PMD has an external dependency on the libpcap development files which must + be installed on the board. Using the Drivers from the EAL Command Line -------------------------------------------
@@ -42,7 +40,7 @@ Device name and stream options must be separated by commas as shown below: .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 4 \ + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 \ --vdev 'net_pcap0,stream_opt0=..,stream_opt1=..' \ --vdev='net_pcap1,stream_opt0=..'
@@ -141,7 +139,7 @@ Read packets from one pcap file and write them to another: .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 4 \ + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 \ --vdev 'net_pcap0,rx_pcap=file_rx.pcap,tx_pcap=file_tx.pcap' \ -- --port-topology=chained
@@ -149,7 +147,7 @@ Read packets from a network interface and write them to a pcap file: .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 4 \ + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 \ --vdev 'net_pcap0,rx_iface=eth0,tx_pcap=file_tx.pcap' \ -- --port-topology=chained
@@ -157,7 +155,7 @@ Read packets from a pcap file and write them to a network interface: .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 4 \ + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 \ --vdev 'net_pcap0,rx_pcap=file_rx.pcap,tx_iface=eth1' \ -- --port-topology=chained
@@ -165,14 +163,14 @@ Forward packets through two network interfaces: .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 4 \ + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 \ --vdev 'net_pcap0,iface=eth0' --vdev='net_pcap1;iface=eth1' Enable 2 tx queues on a network interface: .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 4 \ + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 \ --vdev 'net_pcap0,rx_iface=eth1,tx_iface=eth1,tx_iface=eth1' \ -- --txq 2
@@ -180,7 +178,7 @@ Read only incoming packets from a network interface and write them back to the s .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 4 \ + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 \ --vdev 'net_pcap0,rx_iface_in=eth1,tx_iface=eth1' Using libpcap-based PMD with the testpmd Application
@@ -205,7 +203,7 @@ Otherwise, the first 512 packets from the input pcap file will be discarded by t .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 4 \ + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 \ --vdev 'net_pcap0,rx_pcap=file_rx.pcap,tx_pcap=file_tx.pcap' \ -- --port-topology=chained --no-flush-rx
@@ -225,7 +223,7 @@ Multiple devices may be specified, separated by commas. .. code-block:: console - ./testpmd -l 1-3 -n 4 --vdev=net_ring0 --vdev=net_ring1 -- -i + ./dpdk-testpmd -l 1-3 -n 4 --vdev=net_ring0 --vdev=net_ring1 -- -i EAL: Detected lcore 1 as core 1 on socket 0 ...
doc/guides/nics/qede.rst +2 -15
@@ -111,22 +111,9 @@ Performance note Config File Options ~~~~~~~~~~~~~~~~~~~ -The following options can be modified in the ``.config`` file. Please note that -enabling debugging options may affect system performance. +The following option can be modified in the ``config/rte_config.h`` file. -- ``CONFIG_RTE_LIBRTE_QEDE_PMD`` (default **y**) - - Toggle compilation of QEDE PMD driver. - -- ``CONFIG_RTE_LIBRTE_QEDE_DEBUG_TX`` (default **n**) - - Toggle display of transmit fast path run-time messages. - -- ``CONFIG_RTE_LIBRTE_QEDE_DEBUG_RX`` (default **n**) - - Toggle display of receive fast path run-time messages. - -- ``CONFIG_RTE_LIBRTE_QEDE_FW`` (default **""**) +- ``RTE_LIBRTE_QEDE_FW`` (default **""**) Gives absolute path of firmware file. ``Eg: "/lib/firmware/qed/qed_init_values-8.40.33.0.bin"``
doc/guides/nics/sfc_efx.rst +0 -15
@@ -271,21 +271,6 @@ Pre-Installation Configuration ------------------------------ -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_SFC_EFX_PMD`` (default **y**) - - Enable compilation of Solarflare libefx-based poll-mode driver. - -- ``CONFIG_RTE_LIBRTE_SFC_EFX_DEBUG`` (default **n**) - - Enable compilation of the extra run-time consistency checks. - - Per-Device Parameters ~~~~~~~~~~~~~~~~~~~~~
doc/guides/nics/softnic.rst +2 -11
@@ -51,15 +51,6 @@ Any Linux distribution fulfilling the conditions described in ``System Requireme section of :ref:`the DPDK documentation <linux_gsg>` or refer to *DPDK Release Notes*. -Build options -------------- - -The default PMD configuration available in the common_linux configuration file: - -CONFIG_RTE_LIBRTE_PMD_SOFTNIC=y - -Once the DPDK is built, all the DPDK applications include support for the -Soft NIC PMD. Soft NIC PMD arguments ----------------------
@@ -130,7 +121,7 @@ Soft NIC testing .. code-block:: console - ./testpmd -c 0x7 -s 0x4 --vdev 'net_softnic0,firmware=<script path>/firmware.cli,cpu_id=0,conn_port=8086' -- -i + ./dpdk-testpmd -c 0x7 -s 0x4 --vdev 'net_softnic0,firmware=<script path>/firmware.cli,cpu_id=0,conn_port=8086' -- -i --portmask=0x2 .. code-block:: console
@@ -375,7 +366,7 @@ commands. .. code-block:: console - ./x86_64-native-linux-gcc/app/testpmd -c 0x7 -s 0x4 -n 4 \ + ./<build_dir>/app/dpdk-testpmd -c 0x7 -s 0x4 -n 4 \ --vdev 'net_softnic0, \ firmware=./drivers/net/softnic/ \ firmware.cli, \
doc/guides/nics/szedata2.rst +1 -17
@@ -15,13 +15,6 @@ and used technology (`Netcope Development Kit <http://www.netcope.com/en/products/fpga-development-kit>`_) can be found on the `Netcope Technologies website <http://www.netcope.com/>`_. -.. note:: - - This driver has external dependencies. - Therefore it is disabled in default configuration files. - It can be enabled by setting ``CONFIG_RTE_LIBRTE_PMD_SZEDATA2=y`` - and recompiling. - .. note:: Currently the driver is supported only on x86_64 architectures.
@@ -63,15 +56,6 @@ The minimum version of the provided packages: * for DPDK up to 18.02 (including): **3.0.5** -Configuration -------------- - -These configuration options can be modified before compilation in the -``.config`` file: - -* ``CONFIG_RTE_LIBRTE_PMD_SZEDATA2`` default value: **n** - - Value **y** enables compilation of szedata2 PMD. Using the SZEDATA2 PMD ----------------------
@@ -129,7 +113,7 @@ transmit channel: .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 2 \ + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 2 \ -- --port-topology=chained --rxq=2 --txq=2 --nb-cores=2 -i -a Example output:
doc/guides/nics/thunderx.rst +2 -23
@@ -43,26 +43,6 @@ Prerequisites ------------- - Follow the DPDK :ref:`Getting Started Guide for Linux <linux_gsg>` to setup the basic DPDK environment. -Pre-Installation Configuration ------------------------------- - -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_THUNDERX_NICVF_PMD`` (default ``y``) - - Toggle compilation of the ``librte_pmd_thunderx_nicvf`` driver. - -- ``CONFIG_RTE_LIBRTE_THUNDERX_NICVF_DEBUG_RX`` (default ``n``) - - Toggle asserts of receive fast path. - -- ``CONFIG_RTE_LIBRTE_THUNDERX_NICVF_DEBUG_TX`` (default ``n``) - - Toggle asserts of transmit fast path. Driver compilation and testing ------------------------------
@@ -70,8 +50,7 @@ Driver compilation and testing Refer to the document :ref:`compiling and testing a PMD for a NIC <pmd_build_and_test>` for details. -To compile the ThunderX NICVF PMD for Linux arm64 gcc, -use arm64-thunderx-linux-gcc as target. +Use config/arm/arm64-thunderx-linux-gcc as a meson cross-file when cross-compiling. Linux -----
@@ -178,7 +157,7 @@ This section provides instructions to configure SR-IOV with Linux OS. .. code-block:: console - ./arm64-thunderx-linux-gcc/app/testpmd -l 0-3 -n 4 -w 0002:01:00.2 \ + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 -w 0002:01:00.2 \ -- -i --no-flush-rx \ --port-topology=loop
doc/guides/nics/vdev_netvsc.rst +0 -6
@@ -61,12 +61,6 @@ This driver implementation may be temporary and should be improved or removed either when hot-plug will be fully supported in EAL and bus drivers or when a new NetVSC driver will be integrated. -Build options -------------- - -- ``CONFIG_RTE_LIBRTE_VDEV_NETVSC_PMD`` (default ``y``) - - Toggle compilation of this driver. Run-time parameters -------------------
doc/guides/nics/vhost.rst +1 -1
@@ -90,7 +90,7 @@ This section demonstrates vhost PMD with testpmd DPDK sample application. .. code-block:: console - ./testpmd -l 0-3 -n 4 --vdev 'net_vhost0,iface=/tmp/sock0,queues=1' -- -i + ./dpdk-testpmd -l 0-3 -n 4 --vdev 'net_vhost0,iface=/tmp/sock0,queues=1' -- -i Other basic DPDK preparations like hugepage enabling here. Please refer to the *DPDK Getting Started Guide* for detailed instructions.
doc/guides/nics/virtio.rst +2 -2
@@ -110,7 +110,7 @@ Host2VM communication example .. code-block:: console - examples/kni/build/app/kni -l 0-3 -n 4 -- -p 0x1 -P --config="(0,1,3)" + <build_dir>/examples/dpdk-kni -l 0-3 -n 4 -- -p 0x1 -P --config="(0,1,3)" This command generates one network device vEth0 for physical port. If specify more physical ports, the generated network device will be vEth1, vEth2, and so on.
@@ -340,7 +340,7 @@ Here we use l3fwd-power as an example to show how to get started. .. code-block:: console - $ l3fwd-power -l 0-1 -- -p 1 -P --config="(0,0,1)" \ + $ dpdk-l3fwd-power -l 0-1 -- -p 1 -P --config="(0,0,1)" \ --no-numa --parse-ptype
Signature · 1 line
2.17.1
PATCH v3 30/37 doc: remove references to make in platform guides
In reply to Ciara PowerMake is no longer supported for compiling DPDK, references are now removed in the documentation.
--- doc/guides/platform/bluefield.rst | 22 --------------------- doc/guides/platform/octeontx.rst | 33 +------------------------------ doc/guides/platform/octeontx2.rst | 32 ------------------------------ 3 files changed, 1 insertion(+), 86 deletions(-)
doc/guides/platform/bluefield.rst +0 -22
@@ -60,17 +60,6 @@ Native Compilation Refer to :doc:`../nics/mlx5` for prerequisites. Either Mellanox OFED/EN or rdma-core library with corresponding kernel drivers is required. -make build -^^^^^^^^^^ - -.. code-block:: console - - make config T=arm64-bluefield-linux-gcc - make -j - -meson build -^^^^^^^^^^^ - .. code-block:: console meson build
@@ -126,17 +115,6 @@ Then, untar the tarball at the cross toolchain directory on the x86 host. cd $(dirname $(which aarch64-linux-gnu-gcc))/.. tar xf aarch64-linux-gnu-mlx.tar -make build -^^^^^^^^^^ - -.. code-block:: console - - make config T=arm64-bluefield-linux-gcc - make -j CROSS=aarch64-linux-gnu- CONFIG_RTE_KNI_KMOD=n CONFIG_RTE_EAL_IGB_UIO=n - -meson build -^^^^^^^^^^^ - .. code-block:: console meson build --cross-file config/arm/arm64_bluefield_linux_gcc
doc/guides/platform/octeontx.rst +1 -32
@@ -90,23 +90,8 @@ native architecture, the linux sources need to be compiled once natively. The above steps would rebuild the modules and the required intermediate binaries. Once the target is ready for native compilation, the OCTEON TX platform -drivers can be compiled with the following steps, +drivers can be compiled, see :doc:`../linux_gsg/build_dpdk` for details. -.. code-block:: console - - cd <dpdk directory> - make config T=arm64-thunderx-linux-gcc - make - -The example applications can be compiled using the following: - -.. code-block:: console - - cd <dpdk directory> - export RTE_SDK=$PWD - export RTE_TARGET=build - cd examples/<application> - make Cross Compilation ~~~~~~~~~~~~~~~~~
@@ -139,23 +124,7 @@ SDK 6.2.0 patch 3: The above steps will prepare build system with numa additions. Now this build system can be used to build applications for **OCTEON TX** :sup:`®` platforms. -.. code-block:: console - - cd <dpdk directory> - export RTE_SDK=$PWD - export RTE_KERNELDIR=$THUNDER_ROOT/linux/kernel/linux - make config T=arm64-thunderx-linux-gcc - make -j CROSS=aarch64-thunderx-linux-gnu- CONFIG_RTE_KNI_KMOD=n CONFIG_RTE_EAL_IGB_UIO=n EXTRA_CFLAGS="-isystem <numa_install_dir>/include" EXTRA_LDFLAGS="-L<numa_install_dir>/lib -lnuma" - If NUMA support is not required, it can be disabled as explained in :doc:`../linux_gsg/cross_build_dpdk_for_arm64`. -Following steps could be used in that case. - -.. code-block:: console - - make config T=arm64-thunderx-linux-gcc - make CROSS=aarch64-thunderx-linux-gnu- - - SDK and related information can be obtained from: `Cavium support site <https://support.cavium.com/>`_.
doc/guides/platform/octeontx2.rst +0 -32
@@ -498,27 +498,6 @@ an x86 based platform. Native Compilation ~~~~~~~~~~~~~~~~~~ -make build -^^^^^^^^^^ - -.. code-block:: console - - make config T=arm64-octeontx2-linux-gcc - make -j - -The example applications can be compiled using the following: - -.. code-block:: console - - cd <dpdk directory> - export RTE_SDK=$PWD - export RTE_TARGET=build - cd examples/<application> - make -j - -meson build -^^^^^^^^^^^ - .. code-block:: console meson build
@@ -529,17 +508,6 @@ Cross Compilation Refer to :doc:`../linux_gsg/cross_build_dpdk_for_arm64` for generic arm64 details. -make build -^^^^^^^^^^ - -.. code-block:: console - - make config T=arm64-octeontx2-linux-gcc - make -j CROSS=aarch64-marvell-linux-gnu- CONFIG_RTE_KNI_KMOD=n - -meson build -^^^^^^^^^^^ - .. code-block:: console meson build --cross-file config/arm/arm64_octeontx2_linux_gcc
Signature · 1 line
2.17.1
PATCH v3 31/37 doc: remove references to make in prog guides
In reply to Ciara PowerMake is no longer supported for compiling DPDK, references are now removed in the documentation.
---
MAINTAINERS | 3 +-
doc/guides/prog_guide/build_app.rst | 48 +--
.../prog_guide/dev_kit_build_system.rst | 331 ------------------
.../prog_guide/dev_kit_root_make_help.rst | 188 ----------
.../prog_guide/env_abstraction_layer.rst | 17 +-
...ib_make_help.rst => ext_app_make_help.rst} | 25 +-
doc/guides/prog_guide/graph_lib.rst | 6 +-
doc/guides/prog_guide/index.rst | 4 +-
doc/guides/prog_guide/intro.rst | 2 +-
.../prog_guide/ip_fragment_reassembly_lib.rst | 5 -
.../prog_guide/kernel_nic_interface.rst | 14 +-
.../link_bonding_poll_mode_drv_lib.rst | 15 +-
doc/guides/prog_guide/lto.rst | 12 +-
doc/guides/prog_guide/mbuf_lib.rst | 4 +-
doc/guides/prog_guide/mempool_lib.rst | 7 +-
doc/guides/prog_guide/overview.rst | 12 +-
doc/guides/prog_guide/profile_app.rst | 17 +-
doc/guides/prog_guide/qos_framework.rst | 10 +-
doc/guides/prog_guide/rcu_lib.rst | 7 +-
doc/guides/prog_guide/source_org.rst | 23 +-
doc/guides/prog_guide/trace_lib.rst | 3 +-
.../prog_guide/writing_efficient_code.rst | 3 +-
22 files changed, 52 insertions(+), 704 deletions(-)
delete mode 100644 doc/guides/prog_guide/dev_kit_build_system.rst
delete mode 100644 doc/guides/prog_guide/dev_kit_root_make_help.rst
rename doc/guides/prog_guide/{ext_app_lib_make_help.rst => ext_app_make_help.rst} (69%)MAINTAINERS +1 -2
@@ -103,8 +103,7 @@ F: Makefile F: config/ F: doc/build-sdk-quick.txt F: doc/guides/prog_guide/build_app.rst -F: doc/guides/prog_guide/dev_kit_* -F: doc/guides/prog_guide/ext_app_lib_make_help.rst +F: doc/guides/prog_guide/ext_app_make_help.rst Meson build M: Bruce Richardson <[email protected]>
doc/guides/prog_guide/build_app.rst +4 -44
79 lines not on this page · raw message
doc/guides/prog_guide/dev_kit_build_system.rst deleted +0 -331
331 lines not on this page · raw message
doc/guides/prog_guide/dev_kit_root_make_help.rst deleted +0 -188
188 lines not on this page · raw message
doc/guides/prog_guide/env_abstraction_layer.rst +6 -11
@@ -201,16 +201,16 @@ each segment is strictly one physical page. It is possible to change the amount of virtual memory being preallocated at startup by editing the following config variables: -* ``CONFIG_RTE_MAX_MEMSEG_LISTS`` controls how many segment lists can DPDK have -* ``CONFIG_RTE_MAX_MEM_MB_PER_LIST`` controls how much megabytes of memory each +* ``RTE_MAX_MEMSEG_LISTS`` controls how many segment lists can DPDK have +* ``RTE_MAX_MEM_MB_PER_LIST`` controls how much megabytes of memory each segment list can address -* ``CONFIG_RTE_MAX_MEMSEG_PER_LIST`` controls how many segments each segment can +* ``RTE_MAX_MEMSEG_PER_LIST`` controls how many segments each segment can have -* ``CONFIG_RTE_MAX_MEMSEG_PER_TYPE`` controls how many segments each memory type +* ``RTE_MAX_MEMSEG_PER_TYPE`` controls how many segments each memory type can have (where "type" is defined as "page size + NUMA node" combination) -* ``CONFIG_RTE_MAX_MEM_MB_PER_TYPE`` controls how much megabytes of memory each +* ``RTE_MAX_MEM_MB_PER_TYPE`` controls how much megabytes of memory each memory type can address -* ``CONFIG_RTE_MAX_MEM_MB`` places a global maximum on the amount of memory +* ``RTE_MAX_MEM_MB`` places a global maximum on the amount of memory DPDK can reserve Normally, these options do not need to be changed.
@@ -715,11 +715,6 @@ However, they can be used in configuration code. Refer to the rte_malloc() function description in the *DPDK API Reference* manual for more information. -Cookies -~~~~~~~ - -When CONFIG_RTE_MALLOC_DEBUG is enabled, the allocated memory contains -overwrite protection fields to help identify buffer overflows. Alignment and NUMA Constraints ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
doc/guides/prog_guide/ext_app_make_help.rst renamed from doc/guides/prog_guide/ext_app_lib_make_help.rst +3 -22
@@ -1,28 +1,11 @@ .. SPDX-License-Identifier: BSD-3-Clause Copyright(c) 2010-2014 Intel Corporation. -.. _External_Application/Library_Makefile_help: +.. _External_Application_Makefile_help: -External Application/Library Makefile help +External Application Makefile help ========================================== -External applications or libraries should include specific Makefiles from RTE_SDK, located in mk directory. -These Makefiles are: - -* ${RTE_SDK}/mk/rte.extapp.mk: Build an application - -* ${RTE_SDK}/mk/rte.extlib.mk: Build a static library - -* ${RTE_SDK}/mk/rte.extobj.mk: Build objects (.o) - -Prerequisites -------------- - -The following variables must be defined: - -* ${RTE_SDK}: Points to the root directory of the DPDK. - -* ${RTE_TARGET}: Reference the target to be used for compilation (for example, x86_64-native-linux-gcc). Build Targets -------------
@@ -32,7 +15,7 @@ This is optional; the default output directory is build. * all, "nothing" (meaning just make) - Build the application or the library in the specified output directory. + Build the application in the specified output directory. Example:
@@ -93,6 +76,4 @@ It is possible to run the Makefile from another directory, by specifying the out .. code-block:: console - export RTE_SDK=/path/to/DPDK - export RTE_TARGET=x86_64-native-linux-icc make -f /path/to/my_app/Makefile S=/path/to/my_app O=/path/to/build_dir
doc/guides/prog_guide/graph_lib.rst +2 -4
@@ -45,13 +45,11 @@ Performance tuning parameters ----------------------------- - Test with various burst size values (256, 128, 64, 32) using - CONFIG_RTE_GRAPH_BURST_SIZE config option. + RTE_GRAPH_BURST_SIZE config option. The testing shows, on x86 and arm64 servers, The sweet spot is 256 burst size. While on arm64 embedded SoCs, it is either 64 or 128. -- Disable node statistics (using ``CONFIG_RTE_LIBRTE_GRAPH_STATS`` config option) +- Disable node statistics (using ``RTE_LIBRTE_GRAPH_STATS`` config option) if not needed. -- Use arm64 optimized memory copy for arm64 architecture by - selecting ``CONFIG_RTE_ARCH_ARM64_MEMCPY``. Programming model -----------------
doc/guides/prog_guide/index.rst +1 -3
@@ -62,12 +62,10 @@ Programmer's Guide ipsec_lib graph_lib source_org - dev_kit_build_system - dev_kit_root_make_help build-sdk-meson meson_ut build_app - ext_app_lib_make_help + ext_app_make_help perf_opt_guidelines writing_efficient_code lto
doc/guides/prog_guide/intro.rst +1 -1
@@ -34,7 +34,7 @@ The following is a list of DPDK documents in the suggested reading order: specifically in a Linux* application (linux) environment * The content of the DPDK, the build system - (including the commands that can be used in the root DPDK Makefile to build the development kit and an application) + (including the commands that can be used in the root DPDK to build the development kit and an application) and guidelines for porting an application * Optimizations used in the software and those that should be considered for new development
doc/guides/prog_guide/ip_fragment_reassembly_lib.rst +0 -5
@@ -103,8 +103,3 @@ Debug logging and Statistics Collection The RTE_LIBRTE_IP_FRAG_TBL_STAT config macro controls statistics collection for the Fragment Table. This macro is not enabled by default. - -The RTE_LIBRTE_IP_FRAG_DEBUG controls debug logging of IP fragments processing and reassembling. -This macro is disabled by default. -Note that while logging contains a lot of detailed information, -it slows down packet processing and might cause the loss of a lot of packets.
doc/guides/prog_guide/kernel_nic_interface.rst +7 -7
@@ -65,7 +65,7 @@ disabled, and the default carrier state of KNI interfaces is set to *off*. .. code-block:: console - # insmod kmod/rte_kni.ko + # insmod <build_dir>/kernel/linux/kni/rte_kni.ko .. _kni_loopback_mode:
@@ -77,14 +77,14 @@ by specifying the ``lo_mode`` parameter: .. code-block:: console - # insmod kmod/rte_kni.ko lo_mode=lo_mode_fifo + # insmod <build_dir>/kernel/linux/kni/rte_kni.ko lo_mode=lo_mode_fifo The ``lo_mode_fifo`` loopback option will loop back ring enqueue/dequeue operations in kernel space. .. code-block:: console - # insmod kmod/rte_kni.ko lo_mode=lo_mode_fifo_skb + # insmod <build_dir>/kernel/linux/kni/rte_kni.ko lo_mode=lo_mode_fifo_skb The ``lo_mode_fifo_skb`` loopback option will loop back ring enqueue/dequeue operations and sk buffer copies in kernel space.
@@ -105,7 +105,7 @@ Single kernel thread mode is enabled as follows: .. code-block:: console - # insmod kmod/rte_kni.ko kthread_mode=single + # insmod <build_dir>/kernel/linux/kni/rte_kni.ko kthread_mode=single This mode will create only one kernel thread for all KNI interfaces to receive data on the kernel side. By default, this kernel thread is not
@@ -122,7 +122,7 @@ kernel thread mode is enabled as follows: .. code-block:: console - # insmod kmod/rte_kni.ko kthread_mode=multiple + # insmod <build_dir>/kernel/linux/kni/rte_kni.ko kthread_mode=multiple This mode will create a separate kernel thread for each KNI interface to receive data on the kernel side. The core affinity of each ``kni_thread``
@@ -163,13 +163,13 @@ To set the default carrier state to *on*: .. code-block:: console - # insmod kmod/rte_kni.ko carrier=on + # insmod <build_dir>/kernel/linux/kni/rte_kni.ko carrier=on To set the default carrier state to *off*: .. code-block:: console - # insmod kmod/rte_kni.ko carrier=off + # insmod <build_dir>/kernel/linux/kni/rte_kni.ko carrier=off If the ``carrier`` parameter is not specified, the default carrier state of KNI interfaces will be set to *off*.
doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst +8 -7
@@ -28,8 +28,9 @@ bonded device and its slave devices. .. note:: The Link Bonding PMD Library is enabled by default in the build - configuration files, the library can be disabled by setting - ``CONFIG_RTE_LIBRTE_PMD_BOND=n`` and recompiling the DPDK. + configuration, the library can be disabled using the meson option + "-Ddisable_drivers=net/bond". + Link Bonding Modes Overview ---------------------------
@@ -377,7 +378,7 @@ Device names and bonding options must be separated by commas as shown below: .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 4 --vdev 'net_bonding0,bond_opt0=..,bond opt1=..'--vdev 'net_bonding1,bond _opt0=..,bond_opt1=..' + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 --vdev 'net_bonding0,bond_opt0=..,bond opt1=..'--vdev 'net_bonding1,bond _opt0=..,bond_opt1=..' Link Bonding EAL Options ^^^^^^^^^^^^^^^^^^^^^^^^
@@ -477,22 +478,22 @@ Create a bonded device in round robin mode with two slaves specified by their PC .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 4 --vdev 'net_bonding0,mode=0,slave=0000:0a:00.01,slave=0000:04:00.00' -- --port-topology=chained + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 --vdev 'net_bonding0,mode=0,slave=0000:0a:00.01,slave=0000:04:00.00' -- --port-topology=chained Create a bonded device in round robin mode with two slaves specified by their PCI address and an overriding MAC address: .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 4 --vdev 'net_bonding0,mode=0,slave=0000:0a:00.01,slave=0000:04:00.00,mac=00:1e:67:1d:fd:1d' -- --port-topology=chained + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 --vdev 'net_bonding0,mode=0,slave=0000:0a:00.01,slave=0000:04:00.00,mac=00:1e:67:1d:fd:1d' -- --port-topology=chained Create a bonded device in active backup mode with two slaves specified, and a primary slave specified by their PCI addresses: .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 4 --vdev 'net_bonding0,mode=1,slave=0000:0a:00.01,slave=0000:04:00.00,primary=0000:0a:00.01' -- --port-topology=chained + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 --vdev 'net_bonding0,mode=1,slave=0000:0a:00.01,slave=0000:04:00.00,primary=0000:0a:00.01' -- --port-topology=chained Create a bonded device in balance mode with two slaves specified by their PCI addresses, and a transmission policy of layer 3 + 4 forwarding: .. code-block:: console - $RTE_TARGET/app/testpmd -l 0-3 -n 4 --vdev 'net_bonding0,mode=2,slave=0000:0a:00.01,slave=0000:04:00.00,xmit_policy=l34' -- --port-topology=chained + ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 --vdev 'net_bonding0,mode=2,slave=0000:0a:00.01,slave=0000:04:00.00,xmit_policy=l34' -- --port-topology=chained
doc/guides/prog_guide/lto.rst +1 -11
@@ -26,17 +26,7 @@ need to explicitly initialize variable in order to silence the compiler. Please note that turning LTO on causes considerable extension of build time. -When using make based build, link time optimization can be enabled for -the whole DPDK by setting: - -.. code-block:: console - - CONFIG_RTE_ENABLE_LTO=y - -in config file. - -For the meson based build it can be enabled by setting meson built-in -'b_lto' option: +Link time optimization can be enabled by setting meson built-in 'b_lto' option: .. code-block:: console
doc/guides/prog_guide/mbuf_lib.rst +2 -2
@@ -266,8 +266,8 @@ can be found in several of the sample applications, for example, the IPv4 Multic Debug ----- -In debug mode (CONFIG_RTE_MBUF_DEBUG is enabled), -the functions of the mbuf library perform sanity checks before any operation (such as, buffer corruption, bad type, and so on). +In debug mode, the functions of the mbuf library perform sanity checks before any operation (such as, buffer corruption, +bad type, and so on). Use Cases ---------
doc/guides/prog_guide/mempool_lib.rst +3 -4
@@ -17,14 +17,13 @@ This library is used by the :ref:`Mbuf Library <Mbuf_Library>`. Cookies ------- -In debug mode (CONFIG_RTE_LIBRTE_MEMPOOL_DEBUG is enabled), cookies are added at the beginning and end of allocated blocks. +In debug mode, cookies are added at the beginning and end of allocated blocks. The allocated objects then contain overwrite protection fields to help debugging buffer overflows. Stats ----- -In debug mode (CONFIG_RTE_LIBRTE_MEMPOOL_DEBUG is enabled), -statistics about get from/put in the pool are stored in the mempool structure. +In debug mode, statistics about get from/put in the pool are stored in the mempool structure. Statistics are per-lcore to avoid concurrent access to statistics counters. Memory Alignment Constraints on x86 architecture
@@ -90,7 +89,7 @@ the speed at which a core can access its own cache for a specific memory pool wi The cache is composed of a small, per-core table of pointers and its length (used as a stack). This internal cache can be enabled or disabled at creation of the pool. -The maximum size of the cache is static and is defined at compilation time (CONFIG_RTE_MEMPOOL_CACHE_MAX_SIZE). +The maximum size of the cache is static and is defined at compilation time (RTE_MEMPOOL_CACHE_MAX_SIZE). :numref:`figure_mempool` shows a cache in operation.
doc/guides/prog_guide/overview.rst +2 -10
@@ -18,7 +18,7 @@ The framework creates a set of libraries for specific environments through the creation of an Environment Abstraction Layer (EAL), which may be specific to a mode of the Intel® architecture (32-bit or 64-bit), Linux* user space compilers or a specific platform. -These environments are created through the use of make files and configuration files. +These environments are created through the use of meson files and configuration files. Once the EAL library is created, the user may link with the library to create their own applications. Other libraries, outside of EAL, including the Hash, Longest Prefix Match (LPM) and rings libraries are also provided.
@@ -38,21 +38,13 @@ Development Environment ----------------------- The DPDK project installation requires Linux and the associated toolchain, -such as one or more compilers, assembler, make utility, +such as one or more compilers, assembler, meson utility, editor and various libraries to create the DPDK components and libraries. Once these libraries are created for the specific environment and architecture, they may then be used to create the user's data plane application. When creating applications for the Linux user space, the glibc library is used. -For DPDK applications, two environmental variables (RTE_SDK and RTE_TARGET) -must be configured before compiling the applications. -The following are examples of how the variables can be set: - -.. code-block:: console - - export RTE_SDK=/home/user/DPDK - export RTE_TARGET=x86_64-native-linux-gcc See the *DPDK Getting Started Guide* for information on setting up the development environment.
doc/guides/prog_guide/profile_app.rst +3 -14
@@ -33,14 +33,6 @@ Refer to the for details about application profiling. -Profiling with VTune -~~~~~~~~~~~~~~~~~~~~ - -To allow VTune attaching to the DPDK application, reconfigure and recompile -the DPDK with ``CONFIG_RTE_ETHDEV_RXTX_CALLBACKS`` and -``CONFIG_RTE_ETHDEV_PROFILE_WITH_VTUNE`` enabled. - - Profiling on ARM64 ------------------
@@ -76,8 +68,7 @@ cycle counter for user space access by configuring the PMU from the privileged mode (kernel space). By default the ``rte_rdtsc()`` implementation uses a portable ``cntvct_el0`` -scheme. Application can choose the PMU based implementation with -``CONFIG_RTE_ARM_EAL_RDTSC_USE_PMU``. +scheme. The example below shows the steps to configure the PMU based cycle counter on an ARMv8 machine.
@@ -88,10 +79,8 @@ an ARMv8 machine. cd armv8_pmu_cycle_counter_el0 make sudo insmod pmu_el0_cycle_counter.ko - cd $DPDK_DIR - make config T=arm64-armv8a-linux-gcc - echo "CONFIG_RTE_ARM_EAL_RDTSC_USE_PMU=y" >> build/.config - make + +Please refer to :doc:`../linux_gsg/build_dpdk` for details on compiling DPDK with meson. .. warning::
doc/guides/prog_guide/qos_framework.rst +1 -9
@@ -1525,15 +1525,7 @@ Integration with the DPDK QoS Scheduler ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ RED functionality in the DPDK QoS scheduler is disabled by default. -To enable it, use the DPDK configuration parameter: - -:: - - CONFIG_RTE_SCHED_RED=y - -This parameter must be set to y. -The parameter is found in the build configuration files in the DPDK/config directory, -for example, DPDK/config/common_linux. +The parameter is found in the build configuration files in the DPDK/config directory. RED configuration parameters are specified in the rte_red_params structure within the rte_sched_port_params structure that is passed to the scheduler on initialization. RED parameters are specified separately for four traffic classes and three packet colors (green, yellow and red)
doc/guides/prog_guide/rcu_lib.rst +3 -4
@@ -186,10 +186,9 @@ they entered a quiescent state. This API checks if a writer has triggered a quiescent state query and update the state accordingly. The ``rte_rcu_qsbr_lock()`` and ``rte_rcu_qsbr_unlock()`` are empty functions. -However, when ``CONFIG_RTE_LIBRTE_RCU_DEBUG`` is enabled, these APIs aid -in debugging issues. One can mark the access to shared data structures on the -reader side using these APIs. The ``rte_rcu_qsbr_quiescent()`` will check if -all the locks are unlocked. +However, these APIs can aid in debugging issues. One can mark the access to +shared data structures on the reader side using these APIs. The +``rte_rcu_qsbr_quiescent()`` will check if all the locks are unlocked. Resource reclamation framework for DPDK ---------------------------------------
doc/guides/prog_guide/source_org.rst +2 -21
@@ -8,29 +8,10 @@ Source Organization This section describes the organization of sources in the DPDK framework. -Makefiles and Config --------------------- - -.. note:: - - In the following descriptions, - ``RTE_SDK`` is the environment variable that points to the base directory into which the tarball was extracted. - See - :ref:`Useful_Variables_Provided_by_the_Build_System` - for descriptions of other variables. - -Makefiles that are provided by the DPDK libraries and applications are located in ``$(RTE_SDK)/mk``. - -Config templates are located in ``$(RTE_SDK)/config``. The templates describe the options that are enabled for each target. -The config file also contains items that can be enabled and disabled for many of the DPDK libraries, -including debug options. -The user should look at the config file and become familiar with these options. -The config file is also used to create a header file, which will be located in the new build directory. - Libraries --------- -Libraries are located in subdirectories of ``$(RTE_SDK)/lib``. +Libraries are located in subdirectories of ``dpdk/lib``. By convention a library refers to any code that provides an API to an application. Typically, it generates an archive file (``.a``), but a kernel module would also go in the same directory.
@@ -55,7 +36,7 @@ Applications ------------ Applications are source files that contain a ``main()`` function. -They are located in the ``$(RTE_SDK)/app`` and ``$(RTE_SDK)/examples`` directories. +They are located in the ``dpdk/app`` and ``dpdk/examples`` directories. The app directory contains sample applications that are used to test DPDK (such as autotests) or the Poll Mode Drivers (test-pmd).
doc/guides/prog_guide/trace_lib.rst +1 -2
@@ -135,8 +135,7 @@ In order to avoid performance impact in fast path code, the library introduced the user must use ``RTE_TRACE_POINT_FP`` instead of ``RTE_TRACE_POINT``. ``RTE_TRACE_POINT_FP`` is compiled out by default and it can be enabled using -``CONFIG_RTE_ENABLE_TRACE_FP`` configuration parameter. -The ``enable_trace_fp`` option shall be used for the same for meson build. +the ``enable_trace_fp`` option for meson build. Event record mode -----------------
doc/guides/prog_guide/writing_efficient_code.rst +1 -2
@@ -258,8 +258,7 @@ For instance: Setting the Target CPU Type --------------------------- -The DPDK supports CPU microarchitecture-specific optimizations by means of CONFIG_RTE_MACHINE option -in the DPDK configuration file. +The DPDK supports CPU microarchitecture-specific optimizations by means of RTE_MACHINE option. The degree of optimization depends on the compiler's ability to optimize for a specific microarchitecture, therefore it is preferable to use the latest compiler versions whenever possible.
Signature · 1 line
2.17.1
PATCH v3 32/37 doc: remove references to make in rawdev guides
In reply to Ciara PowerMake is no longer supported for compiling DPDK, references are now removed in the documentation.
--- doc/guides/rawdevs/dpaa2_cmdif.rst | 21 --------------------- doc/guides/rawdevs/dpaa2_qdma.rst | 21 --------------------- doc/guides/rawdevs/ifpga.rst | 10 ---------- doc/guides/rawdevs/ioat.rst | 8 +------- doc/guides/rawdevs/ntb.rst | 6 ------ doc/guides/rawdevs/octeontx2_dma.rst | 12 ------------ doc/guides/rawdevs/octeontx2_ep.rst | 8 -------- 7 files changed, 1 insertion(+), 85 deletions(-)
doc/guides/rawdevs/dpaa2_cmdif.rst +0 -21
@@ -44,17 +44,6 @@ Currently supported by DPDK: Some part of fslmc bus code (mc flib - object library) routines are dual licensed (BSD & GPLv2). -Pre-Installation Configuration ------------------------------- - -Config File Options -~~~~~~~~~~~~~~~~~~~ - -The following options can be modified in the ``config`` file. - -- ``CONFIG_RTE_LIBRTE_PMD_DPAA2_CMDIF_RAWDEV`` (default ``y``) - - Toggle compilation of the ``lrte_pmd_dpaa2_cmdif`` driver. Enabling logs -------------
@@ -68,16 +57,6 @@ For enabling logs, use the following EAL parameter: Using ``pmd.raw.dpaa2.cmdif`` as log matching criteria, all Event PMD logs can be enabled which are lower than logging ``level``. -Driver Compilation -~~~~~~~~~~~~~~~~~~ - -To compile the DPAA2 CMDIF PMD for Linux arm64 gcc target, run the -following ``make`` command: - -.. code-block:: console - - cd <DPDK-source-directory> - make config T=arm64-dpaa-linux-gcc install Initialization --------------
doc/guides/rawdevs/dpaa2_qdma.rst +0 -21
@@ -48,17 +48,6 @@ Currently supported by DPDK: Some part of fslmc bus code (mc flib - object library) routines are dual licensed (BSD & GPLv2). -Pre-Installation Configuration ------------------------------- - -Config File Options -~~~~~~~~~~~~~~~~~~~ - -The following options can be modified in the ``config`` file. - -- ``CONFIG_RTE_LIBRTE_PMD_DPAA2_QDMA_RAWDEV`` (default ``y``) - - Toggle compilation of the ``lrte_pmd_dpaa2_qdma`` driver. Enabling logs -------------
@@ -72,16 +61,6 @@ For enabling logs, use the following EAL parameter: Using ``pmd.raw.dpaa2.qdma`` as log matching criteria, all Event PMD logs can be enabled which are lower than logging ``level``. -Driver Compilation -~~~~~~~~~~~~~~~~~~ - -To compile the DPAA2 QDMA PMD for Linux arm64 gcc target, run the -following ``make`` command: - -.. code-block:: console - - cd <DPDK-source-directory> - make config T=arm64-dpaa-linux-gcc install Initialization --------------
doc/guides/rawdevs/ifpga.rst +0 -10
@@ -76,16 +76,6 @@ summarized by the following block diagram:: | vdev_ifpga_cfg driver | | Intel FpgaDev | +------------------------------------+ +-----------------+ -Build options -------------- - -- ``CONFIG_RTE_LIBRTE_IFPGA_BUS`` (default ``y``) - - Toggle compilation of IFPGA Bus library. - -- ``CONFIG_RTE_LIBRTE_IFPGA_RAWDEV`` (default ``y``) - - Toggle compilation of the ``ifpga_rawdev`` driver. Run-time parameters -------------------
doc/guides/rawdevs/ioat.rst +1 -7
@@ -54,13 +54,7 @@ shows: Compilation ------------ -For builds done with ``make``, the driver compilation is enabled by the -``CONFIG_RTE_LIBRTE_PMD_IOAT_RAWDEV`` build configuration option. This is -enabled by default in builds for x86 platforms, and disabled in other -configurations. - -For builds using ``meson`` and ``ninja``, the driver will be built when the -target platform is x86-based. +The driver will be built when the target platform is x86-based. Device Setup -------------
doc/guides/rawdevs/ntb.rst +0 -6
@@ -30,12 +30,6 @@ is https://www.intel.com/content/dam/support/us/en/documents/server-products/Int - Disable PCIe PII SSC (Spread Spectrum Clocking) for both hosts. This is a hardware requirement. -Build Options -------------- - -- ``CONFIG_RTE_LIBRTE_PMD_NTB_RAWDEV`` (default ``y``) - - Toggle compilation of the ``ntb`` driver. Device Setup ------------
doc/guides/rawdevs/octeontx2_dma.rst +0 -12
@@ -26,18 +26,6 @@ Prerequisites and Compilation procedure See :doc:`../platform/octeontx2` for setup information. -Pre-Installation Configuration ------------------------------- - -Config File Options -~~~~~~~~~~~~~~~~~~~ - -The following options can be modified in the ``config`` file. - -- ``CONFIG_RTE_LIBRTE_PMD_OCTEONTX2_DMA_RAWDEV`` (default ``y``) - - Toggle compilation of the ``lrte_pmd_octeontx2_dma`` driver. - Enabling logs -------------
doc/guides/rawdevs/octeontx2_ep.rst +0 -8
@@ -18,14 +18,6 @@ This OCTEON TX2 End Point mode PMD supports #. Packet Output - OCTEON TX2 to Host with info pointer mode. -Config File Options -~~~~~~~~~~~~~~~~~~~ - -The following options can be modified in the ``config`` file. - -- ``CONFIG_RTE_LIBRTE_PMD_OCTEONTX2_EP_RAWDEV`` (default ``y``) - - Toggle compilation of the ``lrte_pmd_octeontx2_ep`` driver. Initialization --------------
Signature · 1 line
2.17.1
PATCH v3 33/37 doc: remove references to make in sample app guides
In reply to Ciara PowerMake is no longer supported for compiling DPDK, references are now removed in the documentation.
--- doc/guides/sample_app_ug/bbdev_app.rst | 34 ++------ doc/guides/sample_app_ug/cmd_line.rst | 2 +- doc/guides/sample_app_ug/compiling.rst | 83 +++++++------------ doc/guides/sample_app_ug/dist_app.rst | 4 +- doc/guides/sample_app_ug/ethtool.rst | 2 +- .../sample_app_ug/eventdev_pipeline.rst | 3 +- doc/guides/sample_app_ug/fips_validation.rst | 10 +-- doc/guides/sample_app_ug/flow_classify.rst | 4 +- doc/guides/sample_app_ug/flow_filtering.rst | 25 +----- doc/guides/sample_app_ug/hello_world.rst | 2 +- doc/guides/sample_app_ug/ioat.rst | 6 +- doc/guides/sample_app_ug/ip_frag.rst | 6 +- doc/guides/sample_app_ug/ip_pipeline.rst | 4 +- doc/guides/sample_app_ug/ip_reassembly.rst | 9 +- doc/guides/sample_app_ug/ipsec_secgw.rst | 14 +--- doc/guides/sample_app_ug/ipv4_multicast.rst | 4 +- doc/guides/sample_app_ug/keep_alive.rst | 4 +- .../sample_app_ug/kernel_nic_interface.rst | 14 ++-- doc/guides/sample_app_ug/l2_forward_cat.rst | 4 +- .../sample_app_ug/l2_forward_crypto.rst | 4 +- doc/guides/sample_app_ug/l2_forward_event.rst | 10 +-- .../sample_app_ug/l2_forward_job_stats.rst | 4 +- .../sample_app_ug/l2_forward_real_virtual.rst | 6 +- doc/guides/sample_app_ug/l3_forward.rst | 10 +-- .../sample_app_ug/l3_forward_access_ctrl.rst | 6 +- doc/guides/sample_app_ug/l3_forward_graph.rst | 4 +- .../sample_app_ug/l3_forward_power_man.rst | 14 ++-- doc/guides/sample_app_ug/link_status_intr.rst | 4 +- doc/guides/sample_app_ug/multi_process.rst | 20 ++--- doc/guides/sample_app_ug/ntb.rst | 2 +- doc/guides/sample_app_ug/packet_ordering.rst | 3 +- .../sample_app_ug/performance_thread.rst | 44 +++------- doc/guides/sample_app_ug/ptpclient.rst | 9 +- doc/guides/sample_app_ug/qos_metering.rst | 2 +- doc/guides/sample_app_ug/qos_scheduler.rst | 10 +-- doc/guides/sample_app_ug/rxtx_callbacks.rst | 9 +- doc/guides/sample_app_ug/server_node_efd.rst | 2 +- doc/guides/sample_app_ug/service_cores.rst | 23 +---- doc/guides/sample_app_ug/skeleton.rst | 2 +- doc/guides/sample_app_ug/tep_termination.rst | 43 +++------- doc/guides/sample_app_ug/test_pipeline.rst | 4 +- doc/guides/sample_app_ug/timer.rst | 2 +- doc/guides/sample_app_ug/vdpa.rst | 4 +- doc/guides/sample_app_ug/vhost.rst | 11 +-- doc/guides/sample_app_ug/vhost_blk.rst | 2 +- doc/guides/sample_app_ug/vhost_crypto.rst | 2 +- .../sample_app_ug/vm_power_management.rst | 34 ++++---- .../sample_app_ug/vmdq_dcb_forwarding.rst | 8 +- doc/guides/sample_app_ug/vmdq_forwarding.rst | 8 +- 49 files changed, 194 insertions(+), 346 deletions(-)
doc/guides/sample_app_ug/bbdev_app.rst +8 -26
@@ -31,30 +31,12 @@ Limitations Compiling the Application ------------------------- -#. DPDK needs to be built with ``baseband_turbo_sw`` PMD driver enabled along - with ``FLEXRAN SDK`` Libraries. Refer to *SW Turbo Poll Mode Driver* - documentation for more details on this. +DPDK needs to be built with ``baseband_turbo_sw`` PMD driver enabled along +with ``FLEXRAN SDK`` Libraries. Refer to *SW Turbo Poll Mode Driver* +documentation for more details on this. -#. Go to the example directory: +To compile the sample application see :doc:`compiling`. - .. code-block:: console - - export RTE_SDK=/path/to/rte_sdk - cd ${RTE_SDK}/examples/bbdev_app - -#. Set the target (a default target is used if not specified). For example: - - .. code-block:: console - - export RTE_TARGET=x86_64-native-linux-gcc - - See the *DPDK Getting Started Guide* for possible RTE_TARGET values. - -#. Build the application: - - .. code-block:: console - - make Running the Application -----------------------
@@ -63,8 +45,8 @@ The application accepts a number of command line options: .. code-block:: console - $ ./build/bbdev [EAL options] -- [-e ENCODING_CORES] [-d DECODING_CORES] / - [-p ETH_PORT_ID] [-b BBDEV_ID] + $ ./<build_dir>/examples/dpdk-bbdev [EAL options] -- [-e ENCODING_CORES] / + [-d DECODING_CORES] [-p ETH_PORT_ID] [-b BBDEV_ID] where:
@@ -84,8 +66,8 @@ issue the command: .. code-block:: console - $ ./build/bbdev --vdev='baseband_turbo_sw' -w <NIC0PCIADDR> -c 0x38 --socket-mem=2,2 \ - --file-prefix=bbdev -- -e 0x10 -d 0x20 + $ ./<build_dir>/examples/dpdk-bbdev --vdev='baseband_turbo_sw' -w <NIC0PCIADDR> \ + -c 0x38 --socket-mem=2,2 --file-prefix=bbdev -- -e 0x10 -d 0x20 where, NIC0PCIADDR is the PCI address of the Rx port
doc/guides/sample_app_ug/cmd_line.rst +1 -1
@@ -52,7 +52,7 @@ To run the application in linux environment, issue the following command: .. code-block:: console - $ ./build/cmdline -l 0-3 -n 4 + $ ./<build_dir>/examples/dpdk-cmdline -l 0-3 -n 4 Refer to the *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL) options.
doc/guides/sample_app_ug/compiling.rst +29 -54
129 lines not on this page · raw message
doc/guides/sample_app_ug/dist_app.rst +2 -2
@@ -42,7 +42,7 @@ Running the Application .. code-block:: console - ./build/distributor_app [EAL options] -- -p PORTMASK + ./<build-dir>/examples/dpdk-distributor [EAL options] -- -p PORTMASK where,
@@ -53,7 +53,7 @@ Running the Application .. code-block:: console - $ ./build/distributor_app -l 1-9,22 -n 4 -- -p f + $ ./<build-dir>/examples/dpdk-distributor -l 1-9,22 -n 4 -- -p f #. Refer to the DPDK Getting Started Guide for general information on running applications and the Environment Abstraction Layer (EAL) options.
doc/guides/sample_app_ug/ethtool.rst +1 -1
@@ -24,7 +24,7 @@ The only available options are the standard ones for the EAL: .. code-block:: console - ./ethtool-app/${RTE_TARGET}/ethtool [EAL options] + ./<build_dir>/examples/dpdk-ethtool [EAL options] Refer to the *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL)
doc/guides/sample_app_ug/eventdev_pipeline.rst +2 -1
@@ -46,7 +46,8 @@ these settings is shown below: .. code-block:: console - ./build/eventdev_pipeline --vdev event_sw0 -- -r1 -t1 -e4 -w FF00 -s4 -n0 -c32 -W1000 -D + ./<build_dir>/examples/dpdk-eventdev_pipeline --vdev event_sw0 -- -r1 -t1 / + -e4 -w FF00 -s4 -n0 -c32 -W1000 -D The application has some sanity checking built-in, so if there is a function (e.g.; the RX core) which doesn't have a cpu core mask assigned, the application
doc/guides/sample_app_ug/fips_validation.rst +4 -6
@@ -70,9 +70,7 @@ Compiling the Application * Compile Application - .. code-block:: console - - make -C examples/fips_validation + To compile the sample application see :doc:`compiling`. * Run ``dos2unix`` on the request files
@@ -92,7 +90,7 @@ The application requires a number of command line options: .. code-block:: console - ./fips_validation [EAL options] + ./dpdk-fips_validation [EAL options] -- --req-file FILE_PATH/FOLDER_PATH --rsp-file FILE_PATH/FOLDER_PATH [--cryptodev DEVICE_NAME] [--cryptodev-id ID] [--path-is-folder]
@@ -117,7 +115,7 @@ file for crypto_aesni_mb PMD, issue the command: .. code-block:: console - $ ./fips_validation --vdev crypto_aesni_mb -- + $ ./dpdk-fips_validation --vdev crypto_aesni_mb -- --req-file /PATH/TO/REQUEST/FILE.req --rsp-file ./PATH/TO/RESPONSE/FILE.rsp --cryptodev crypto_aesni_mb
@@ -126,7 +124,7 @@ data files in one folder for crypto_aesni_gcm PMD, issue the command: .. code-block:: console - $ ./fips_validation --vdev crypto_aesni_gcm0 -- + $ ./dpdk-fips_validation --vdev crypto_aesni_gcm0 -- --req-file /PATH/TO/REQUEST/FILE/FOLDER/ --rsp-file ./PATH/TO/RESPONSE/FILE/FOLDER/ --cryptodev-id 0 --path-is-folder
doc/guides/sample_app_ug/flow_classify.rst +2 -2
@@ -28,8 +28,8 @@ To run the example in a ``linux`` environment: .. code-block:: console - cd ~/dpdk/examples/flow_classify - ./build/flow_classify -c 4 -n 4 -- --rule_ipv4="../ipv4_rules_file.txt" + ./<build_dir>/examples/dpdk-flow_classify -c 4 -n 4 -- / + --rule_ipv4="../ipv4_rules_file.txt" Please refer to the *DPDK Getting Started Guide*, section :doc:`../linux_gsg/build_sample_apps`
doc/guides/sample_app_ug/flow_filtering.rst +2 -23
@@ -13,28 +13,7 @@ It is intended as a demonstration of the basic components RTE flow rules. Compiling the Application ------------------------- -To compile the application export the path to the DPDK source tree and go to -the example directory: - -.. code-block:: console - - export RTE_SDK=/path/to/rte_sdk - - cd ${RTE_SDK}/examples/flow_filtering - -Set the target, for example: - -.. code-block:: console - - export RTE_TARGET=x86_64-native-linux-gcc - -See the *DPDK Getting Started* Guide for possible ``RTE_TARGET`` values. - -Build the application as follows: - -.. code-block:: console - - make +To compile the sample application see :doc:`compiling`. Running the Application
@@ -44,7 +23,7 @@ To run the example in a ``linux`` environment: .. code-block:: console - ./build/flow -l 1 -n 1 + ./<build_dir>/examples/dpdk-flow_filtering -l 1 -n 1 Refer to *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL) options.
doc/guides/sample_app_ug/hello_world.rst +1 -1
@@ -21,7 +21,7 @@ To run the example in a linux environment: .. code-block:: console - $ ./build/helloworld -l 0-3 -n 4 + $ ./<build_dir>/examples/dpdk-helloworld -l 0-3 -n 4 Refer to *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL) options.
doc/guides/sample_app_ug/ioat.rst +3 -3
@@ -45,7 +45,7 @@ The application requires a number of command line options: .. code-block:: console - ./build/ioatfwd [EAL options] -- [-p MASK] [-q NQ] [-s RS] [-c <sw|hw>] + ./<build_dir>/examples/dpdk-ioat [EAL options] -- [-p MASK] [-q NQ] [-s RS] [-c <sw|hw>] [--[no-]mac-updating] where,
@@ -81,7 +81,7 @@ updating issue the command: .. code-block:: console - $ ./build/ioatfwd -l 0-2 -n 2 -- -p 0x1 --mac-updating -c sw + $ ./<build_dir>/examples/dpdk-ioat -l 0-2 -n 2 -- -p 0x1 --mac-updating -c sw To run the application in a Linux environment with 2 lcores (the master lcore, plus one forwarding core), 2 ports (ports 0 and 1), hardware copying and no MAC
@@ -89,7 +89,7 @@ updating issue the command: .. code-block:: console - $ ./build/ioatfwd -l 0-1 -n 1 -- -p 0x3 --no-mac-updating -c hw + $ ./<build_dir>/examples/dpdk-ioat -l 0-1 -n 1 -- -p 0x3 --no-mac-updating -c hw Refer to the *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL) options.
doc/guides/sample_app_ug/ip_frag.rst +3 -3
@@ -53,7 +53,7 @@ Application usage: .. code-block:: console - ./build/ip_fragmentation [EAL options] -- -p PORTMASK [-q NQ] + ./<build_dir>/examples/dpdk-ip_fragmentation [EAL options] -- -p PORTMASK [-q NQ] where:
@@ -65,7 +65,7 @@ To run the example in linux environment with 2 lcores (2,4) over 2 ports(0,2) wi .. code-block:: console - ./build/ip_fragmentation -l 2,4 -n 3 -- -p 5 + ./<build_dir>/examples/dpdk-ip_fragmentation -l 2,4 -n 3 -- -p 5 EAL: coremask set to 14 EAL: Detected lcore 0 on socket 0 EAL: Detected lcore 1 on socket 1
@@ -94,7 +94,7 @@ To run the example in linux environment with 1 lcore (4) over 2 ports(0,2) with .. code-block:: console - ./build/ip_fragmentation -l 4 -n 3 -- -p 5 -q 2 + ./<build_dir>/examples/dpdk-ip_fragmentation -l 4 -n 3 -- -p 5 -q 2 To test the application, flows should be set up in the flow generator that match the values in the l3fwd_ipv4_route_array and/or l3fwd_ipv6_route_array table.
doc/guides/sample_app_ug/ip_pipeline.rst +2 -2
@@ -34,7 +34,7 @@ Running the application The application startup command line is:: - ip_pipeline [EAL_ARGS] -- [-s SCRIPT_FILE] [-h HOST] [-p PORT] + dpdk-ip_pipeline [EAL_ARGS] -- [-s SCRIPT_FILE] [-h HOST] [-p PORT] The application startup arguments are:
@@ -71,7 +71,7 @@ The following is an example command to run ip pipeline application configured fo .. code-block:: console - $ ./build/ip_pipeline -c 0x3 -- -s examples/route_ecmp.cli + $ ./<build_dir>/examples/dpdk-ip_pipeline -c 0x3 -- -s examples/route_ecmp.cli The application should start successfully and display as follows:
doc/guides/sample_app_ug/ip_reassembly.rst +5 -4
@@ -42,7 +42,7 @@ The application has a number of command line options: .. code-block:: console - ./build/ip_reassembly [EAL options] -- -p PORTMASK [-q NQ] [--maxflows=FLOWS>] [--flowttl=TTL[(s|ms)]] + ./<build_dir>/examples/dpdk-ip_reassembly [EAL options] -- -p PORTMASK [-q NQ] [--maxflows=FLOWS>] [--flowttl=TTL[(s|ms)]] where:
@@ -61,7 +61,7 @@ To run the example in linux environment with 2 lcores (2,4) over 2 ports(0,2) wi .. code-block:: console - ./build/ip_reassembly -l 2,4 -n 3 -- -p 5 + ./<build_dir>/examples/dpdk-ip_reassembly -l 2,4 -n 3 -- -p 5 EAL: coremask set to 14 EAL: Detected lcore 0 on socket 0 EAL: Detected lcore 1 on socket 1
@@ -92,7 +92,7 @@ To run the example in linux environment with 1 lcore (4) over 2 ports(0,2) with .. code-block:: console - ./build/ip_reassembly -l 4 -n 3 -- -p 5 -q 2 + ./<build_dir>/examples/dpdk-ip_reassembly -l 4 -n 3 -- -p 5 -q 2 To test the application, flows should be set up in the flow generator that match the values in the l3fwd_ipv4_route_array and/or l3fwd_ipv6_route_array table.
@@ -231,7 +231,8 @@ Debug logging and Statistics Collection ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The RTE_LIBRTE_IP_FRAG_TBL_STAT controls statistics collection for the IP Fragment Table. -This macro is disabled by default. +This macro is disabled by default, but it can be enabled by modifying the appropriate line +in ``config/rte_config.h``. To make ip_reassembly print the statistics to the standard output, the user must send either an USR1, INT or TERM signal to the process. For all of these signals, the ip_reassembly process prints Fragment table statistics for each RX queue,
doc/guides/sample_app_ug/ipsec_secgw.rst +4 -10
@@ -116,12 +116,6 @@ To compile the sample application see :doc:`compiling`. The application is located in the ``ipsec-secgw`` sub-directory. -#. [Optional] Build the application for debugging: - This option adds some extra flags, disables compiler optimizations and - is verbose:: - - make DEBUG=1 - Running the Application -----------------------
@@ -129,7 +123,7 @@ Running the Application The application has a number of command line options:: - ./build/ipsec-secgw [EAL options] -- + ./<build_dir>/examples/dpdk-ipsec-secgw [EAL options] -- -p PORTMASK -P -u PORTMASK -j FRAMESIZE -l -w REPLAY_WINOW_SIZE -e -a -c SAD_CACHE_SIZE
@@ -245,7 +239,7 @@ The mapping of lcores to port/queues is similar to other l3fwd applications. For example, given the following command line to run application in poll mode:: - ./build/ipsec-secgw -l 20,21 -n 4 --socket-mem 0,2048 \ + ./<build_dir>/examples/dpdk-ipsec-secgw -l 20,21 -n 4 --socket-mem 0,2048 \ --vdev "crypto_null" -- -p 0xf -P -u 0x3 \ --config="(0,0,20),(1,0,20),(2,0,21),(3,0,21)" \ -f /path/to/config_file --transfer-mode poll \
@@ -297,7 +291,7 @@ where each option means: Similarly for example, given the following command line to run application in event app mode:: - ./build/ipsec-secgw -c 0x3 -- -P -p 0x3 -u 0x1 \ + ./<build_dir>/examples/dpdk-ipsec-secgw -c 0x3 -- -P -p 0x3 -u 0x1 \ -f /path/to/config_file --transfer-mode event \ --event-schedule-type parallel \
@@ -336,7 +330,7 @@ For example, something like the following command line: .. code-block:: console - ./build/ipsec-secgw -l 20,21 -n 4 --socket-mem 0,2048 \ + ./<build_dir>/examples/dpdk-ipsec-secgw -l 20,21 -n 4 --socket-mem 0,2048 \ -w 81:00.0 -w 81:00.1 -w 81:00.2 -w 81:00.3 \ --vdev "crypto_aesni_mb" --vdev "crypto_null" \ -- \
doc/guides/sample_app_ug/ipv4_multicast.rst +2 -2
@@ -50,7 +50,7 @@ The application has a number of command line options: .. code-block:: console - ./build/ipv4_multicast [EAL options] -- -p PORTMASK [-q NQ] + ./<build_dir>/examples/dpdk-ipv4_multicast [EAL options] -- -p PORTMASK [-q NQ] where,
@@ -67,7 +67,7 @@ Typically, to run the IPv4 Multicast sample application, issue the following com .. code-block:: console - ./build/ipv4_multicast -l 0-3 -n 3 -- -p 0x3 -q 1 + ./<build_dir>/examples/dpdk-ipv4_multicast -l 0-3 -n 3 -- -p 0x3 -q 1 In this command:
doc/guides/sample_app_ug/keep_alive.rst +2 -2
@@ -49,7 +49,7 @@ The application has a number of command line options: .. code-block:: console - ./build/l2fwd-keepalive [EAL options] \ + ./<build_dir>/examples/dpdk-l2fwd-keepalive [EAL options] \ -- -p PORTMASK [-q NQ] [-K PERIOD] [-T PERIOD] where,
@@ -68,7 +68,7 @@ To run the application in linux environment with 4 lcores, 16 ports .. code-block:: console - ./build/l2fwd-keepalive -l 0-3 -n 4 -- -q 8 -p ffff -K 10 + ./<build_dir>/examples/dpdk-l2fwd-keepalive -l 0-3 -n 4 -- -q 8 -p ffff -K 10 Refer to the *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL)
doc/guides/sample_app_ug/kernel_nic_interface.rst +7 -7
@@ -96,7 +96,7 @@ The ``kni`` example application requires a number of command line options: .. code-block:: console - kni [EAL options] -- -p PORTMASK --config="(port,lcore_rx,lcore_tx[,lcore_kthread,...])[,(port,lcore_rx,lcore_tx[,lcore_kthread,...])]" [-P] [-m] + dpdk-kni [EAL options] -- -p PORTMASK --config="(port,lcore_rx,lcore_tx[,lcore_kthread,...])[,(port,lcore_rx,lcore_tx[,lcore_kthread,...])]" [-P] [-m] Where:
@@ -168,8 +168,8 @@ interface ``vEth1_0`` with the kernel thread bound to lcore 9. .. code-block:: console # rmmod rte_kni - # insmod kmod/rte_kni.ko kthread_mode=multiple - # ./build/kni -l 4-7 -n 4 -- -P -p 0x3 -m --config="(0,4,6,8),(1,5,7,9)" + # insmod <build_dir>/kernel/linux/kni/rte_kni.ko kthread_mode=multiple + # ./<build-dir>/examples/dpdk-kni -l 4-7 -n 4 -- -P -p 0x3 -m --config="(0,4,6,8),(1,5,7,9)" The following example is identical, except an additional ``lcore_kthread`` core is specified per physical port. In this case, ``kni`` will create
@@ -186,8 +186,8 @@ The kernel thread for each interface will be bound as follows: .. code-block:: console # rmmod rte_kni - # insmod kmod/rte_kni.ko kthread_mode=multiple - # ./build/kni -l 4-7 -n 4 -- -P -p 0x3 -m --config="(0,4,6,8,10),(1,5,7,9,11)" + # insmod <build_dir>/kernel/linux/kni/rte_kni.ko kthread_mode=multiple + # ./<build-dir>/examples/dpdk-kni -l 4-7 -n 4 -- -P -p 0x3 -m --config="(0,4,6,8,10),(1,5,7,9,11)" The following example can be used to test the interface between the ``kni`` test application and the ``rte_kni`` kernel module. In this example,
@@ -206,8 +206,8 @@ disabled by **not** specifying the ``-m`` flag to ``kni``: .. code-block:: console # rmmod rte_kni - # insmod kmod/rte_kni.ko lo_mode=lo_mode_fifo carrier=on - # ./build/kni -l 4-7 -n 4 -- -P -p 0x3 --config="(0,4,6,8),(1,5,7,9)" + # insmod <build_dir>/kernel/linux/kni/rte_kni.ko lo_mode=lo_mode_fifo carrier=on + # ./<build-dir>/examples/dpdk-kni -l 4-7 -n 4 -- -P -p 0x3 --config="(0,4,6,8),(1,5,7,9)" KNI Operations --------------
doc/guides/sample_app_ug/l2_forward_cat.rst +2 -2
@@ -70,13 +70,13 @@ To run the example in a ``linux`` environment and enable CAT on cpus 0-2: .. code-block:: console - ./build/l2fwd-cat -l 1 -n 4 -- --l3ca="0x3@(0-2)" + ./<build_dir>/examples/dpdk-l2fwd-cat -l 1 -n 4 -- --l3ca="0x3@(0-2)" or to enable CAT and CDP on cpus 1,3: .. code-block:: console - ./build/l2fwd-cat -l 1 -n 4 -- --l3ca="(0x00C00,0x00300)@(1,3)" + ./<build_dir>/examples/dpdk-l2fwd-cat -l 1 -n 4 -- --l3ca="(0x00C00,0x00300)@(1,3)" If CDP is not supported it will fail with following error message:
doc/guides/sample_app_ug/l2_forward_crypto.rst +2 -2
@@ -39,7 +39,7 @@ The application requires a number of command line options: .. code-block:: console - ./build/l2fwd-crypto [EAL options] -- [-p PORTMASK] [-q NQ] [-s] [-T PERIOD] / + ./<build_dir>/examples/dpdk-l2fwd-crypto [EAL options] -- [-p PORTMASK] [-q NQ] [-s] [-T PERIOD] / [--cdev_type HW/SW/ANY] [--chain HASH_CIPHER/CIPHER_HASH/CIPHER_ONLY/HASH_ONLY/AEAD] / [--cipher_algo ALGO] [--cipher_op ENCRYPT/DECRYPT] [--cipher_key KEY] / [--cipher_key_random_size SIZE] [--cipher_iv IV] [--cipher_iv_random_size SIZE] /
@@ -162,7 +162,7 @@ To run the application in linux environment with 2 lcores, 2 ports and 2 crypto .. code-block:: console - $ ./build/l2fwd-crypto -l 0-1 -n 4 --vdev "crypto_aesni_mb0" \ + $ ./<build_dir>/examples/dpdk-l2fwd-crypto -l 0-1 -n 4 --vdev "crypto_aesni_mb0" \ --vdev "crypto_aesni_mb1" -- -p 0x3 --chain CIPHER_HASH \ --cipher_op ENCRYPT --cipher_algo aes-cbc \ --cipher_key 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f \
doc/guides/sample_app_ug/l2_forward_event.rst +5 -5
@@ -52,7 +52,7 @@ The application requires a number of command line options: .. code-block:: console - ./build/l2fwd-event [EAL options] -- -p PORTMASK [-q NQ] --[no-]mac-updating --mode=MODE --eventq-sched=SCHED_MODE + ./<build_dir>/examples/dpdk-l2fwd-event [EAL options] -- -p PORTMASK [-q NQ] --[no-]mac-updating --mode=MODE --eventq-sched=SCHED_MODE where,
@@ -75,20 +75,20 @@ issue the command: .. code-block:: console - ./build/l2fwd-event -l 0-3 -n 4 -- -q 8 -p ffff --mode=poll + ./<build_dir>/examples/dpdk-l2fwd-event -l 0-3 -n 4 -- -q 8 -p ffff --mode=poll Eventdev mode with 4 lcores, 16 ports , sched method ordered and MAC address updating enabled, issue the command: .. code-block:: console - ./build/l2fwd-event -l 0-3 -n 4 -- -p ffff --eventq-sched=ordered + ./<build_dir>/examples/dpdk-l2fwd-event -l 0-3 -n 4 -- -p ffff --eventq-sched=ordered or .. code-block:: console - ./build/l2fwd-event -l 0-3 -n 4 -- -q 8 -p ffff --mode=eventdev --eventq-sched=ordered + ./<build_dir>/examples/dpdk-l2fwd-event -l 0-3 -n 4 -- -q 8 -p ffff --mode=eventdev --eventq-sched=ordered Refer to the *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL) options.
@@ -105,7 +105,7 @@ scheduler. Following is the sample command: .. code-block:: console - ./build/l2fwd-event -l 0-7 -s 0-3 -n 4 --vdev event_sw0 -- -q 8 -p ffff --mode=eventdev --eventq-sched=ordered + ./<build_dir>/examples/dpdk-l2fwd-event -l 0-7 -s 0-3 -n 4 --vdev event_sw0 -- -q 8 -p ffff --mode=eventdev --eventq-sched=ordered Explanation -----------
doc/guides/sample_app_ug/l2_forward_job_stats.rst +2 -2
@@ -81,7 +81,7 @@ The application requires a number of command line options: .. code-block:: console - ./build/l2fwd-jobstats [EAL options] -- -p PORTMASK [-q NQ] [-l] + ./<build_dir>/examples/dpdk-l2fwd-jobstats [EAL options] -- -p PORTMASK [-q NQ] [-l] where,
@@ -96,7 +96,7 @@ thousands separator printing, issue the command: .. code-block:: console - $ ./build/l2fwd-jobstats -l 0-3 -n 4 -- -q 8 -p ffff -l + $ ./<build_dir>/examples/dpdk-l2fwd-jobstats -l 0-3 -n 4 -- -q 8 -p ffff -l Refer to the *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL) options.
doc/guides/sample_app_ug/l2_forward_real_virtual.rst +3 -3
@@ -91,7 +91,7 @@ The application requires a number of command line options: .. code-block:: console - ./build/l2fwd [EAL options] -- -p PORTMASK + ./<build_dir>/examples/dpdk-l2fwd [EAL options] -- -p PORTMASK [-q NQ] --[no-]mac-updating [--portmap="(port, port)[,(port, port)]"]
@@ -111,7 +111,7 @@ updating enabled, issue the command: .. code-block:: console - $ ./build/l2fwd -l 0-3 -n 4 -- -q 8 -p ffff + $ ./<build_dir>/examples/dpdk-l2fwd -l 0-3 -n 4 -- -q 8 -p ffff To run the application in linux environment with 4 lcores, 4 ports, 8 RX queues per lcore, to forward RX traffic of ports 0 & 1 on ports 2 & 3 respectively and
@@ -119,7 +119,7 @@ vice versa, issue the command: .. code-block:: console - $ ./build/l2fwd -l 0-3 -n 4 -- -q 8 -p f --portmap="(0,2)(1,3)" + $ ./<build_dir>/examples/dpdk-l2fwd -l 0-3 -n 4 -- -q 8 -p f --portmap="(0,2)(1,3)" Refer to the *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL) options.
doc/guides/sample_app_ug/l3_forward.rst +5 -5
@@ -51,7 +51,7 @@ Running the Application The application has a number of command line options:: - ./l3fwd [EAL options] -- -p PORTMASK + ./dpdk-l3fwd [EAL options] -- -p PORTMASK [-P] [-E] [-L]
@@ -111,7 +111,7 @@ To enable L3 forwarding between two ports, assuming that both ports are in the s .. code-block:: console - ./build/l3fwd -l 1,2 -n 4 -- -p 0x3 --config="(0,0,1),(1,0,2)" + ./<build_dir>/examples/dpdk-l3fwd -l 1,2 -n 4 -- -p 0x3 --config="(0,0,1),(1,0,2)" In this command:
@@ -138,13 +138,13 @@ Following is the sample command: .. code-block:: console - ./build/l3fwd -l 0-3 -n 4 -w <event device> -- -p 0x3 --eventq-sched=ordered + ./<build_dir>/examples/dpdk-l3fwd -l 0-3 -n 4 -w <event device> -- -p 0x3 --eventq-sched=ordered or .. code-block:: console - ./build/l3fwd -l 0-3 -n 4 -w <event device> -- -p 0x03 --mode=eventdev --eventq-sched=ordered + ./<build_dir>/examples/dpdk-l3fwd -l 0-3 -n 4 -w <event device> -- -p 0x03 --mode=eventdev --eventq-sched=ordered In this command:
@@ -166,7 +166,7 @@ scheduler. Following is the sample command: .. code-block:: console - ./build/l3fwd -l 0-7 -s 0xf0000 -n 4 --vdev event_sw0 -- -p 0x3 --mode=eventdev --eventq-sched=ordered + ./<build_dir>/examples/dpdk-l3fwd -l 0-7 -s 0xf0000 -n 4 --vdev event_sw0 -- -p 0x3 --mode=eventdev --eventq-sched=ordered In case of eventdev mode, *--config* option is not used for ethernet port configuration. Instead each ethernet port will be configured with mentioned
doc/guides/sample_app_ug/l3_forward_access_ctrl.rst +3 -3
@@ -184,7 +184,7 @@ Packet 2 matches Rule 2 and is forwarded to port 1. Packet 3 matches Rule 3 and is forwarded to port 0. For more details on the rule file format, -please refer to rule_ipv4.db and rule_ipv6.db files (inside <RTE_SDK>/examples/l3fwd-acl/). +please refer to rule_ipv4.db and rule_ipv6.db files (inside dpdk/examples/l3fwd-acl/). Application Phases ~~~~~~~~~~~~~~~~~~
@@ -236,7 +236,7 @@ The application has a number of command line options: .. code-block:: console - ./build/l3fwd-acl [EAL options] -- -p PORTMASK [-P] --config(port,queue,lcore)[,(port,queue,lcore)] --rule_ipv4 FILENAME rule_ipv6 FILENAME [--scalar] [--enable-jumbo [--max-pkt-len PKTLEN]] [--no-numa] + ./<build_dir>/examples/dpdk-l3fwd-acl [EAL options] -- -p PORTMASK [-P] --config(port,queue,lcore)[,(port,queue,lcore)] --rule_ipv4 FILENAME rule_ipv6 FILENAME [--scalar] [--enable-jumbo [--max-pkt-len PKTLEN]] [--no-numa] where,
@@ -268,7 +268,7 @@ To enable L3 forwarding between two ports, assuming that both ports are in the s .. code-block:: console - ./build/l3fwd-acl -l 1,2 -n 4 -- -p 0x3 --config="(0,0,1),(1,0,2)" --rule_ipv4="./rule_ipv4.db" -- rule_ipv6="./rule_ipv6.db" --scalar + ./<build_dir>/examples/dpdk-l3fwd-acl -l 1,2 -n 4 -- -p 0x3 --config="(0,0,1),(1,0,2)" --rule_ipv4="./rule_ipv4.db" -- rule_ipv6="./rule_ipv6.db" --scalar In this command:
doc/guides/sample_app_ug/l3_forward_graph.rst +2 -2
@@ -44,7 +44,7 @@ Running the Application The application has a number of command line options similar to l3fwd:: - ./l3fwd-graph [EAL options] -- -p PORTMASK + ./dpdk-l3fwd-graph [EAL options] -- -p PORTMASK [-P] --config(port,queue,lcore)[,(port,queue,lcore)] [--eth-dest=X,MM:MM:MM:MM:MM:MM]
@@ -79,7 +79,7 @@ To enable L3 forwarding between two ports, assuming that both ports are in the s .. code-block:: console - ./build/l3fwd-graph -l 1,2 -n 4 -- -p 0x3 --config="(0,0,1),(1,0,2)" + ./<build_dir>/examples/dpdk-l3fwd-graph -l 1,2 -n 4 -- -p 0x3 --config="(0,0,1),(1,0,2)" In this command:
doc/guides/sample_app_ug/l3_forward_power_man.rst +5 -9
@@ -88,7 +88,7 @@ The application has a number of command line options: .. code-block:: console - ./build/l3fwd_power [EAL options] -- -p PORTMASK [-P] --config(port,queue,lcore)[,(port,queue,lcore)] [--enable-jumbo [--max-pkt-len PKTLEN]] [--no-numa] + ./<build_dir>/examples/dpdk-l3fwd_power [EAL options] -- -p PORTMASK [-P] --config(port,queue,lcore)[,(port,queue,lcore)] [--enable-jumbo [--max-pkt-len PKTLEN]] [--no-numa] where,
@@ -378,7 +378,7 @@ See :doc:`Power Management<../prog_guide/power_man>` chapter in the DPDK Program .. code-block:: console - ./l3fwd-power -l xxx -n 4 -w 0000:xx:00.0 -w 0000:xx:00.1 -- -p 0x3 -P --config="(0,0,xx),(1,0,xx)" --empty-poll="0,0,0" -l 14 -m 9 -h 1 + ./<build_dir>/examples/dpdk-l3fwd-power -l xxx -n 4 -w 0000:xx:00.0 -w 0000:xx:00.1 -- -p 0x3 -P --config="(0,0,xx),(1,0,xx)" --empty-poll="0,0,0" -l 14 -m 9 -h 1 Where,
@@ -407,7 +407,7 @@ app with the training flag set to “1”, and the other parameters set to .. code-block:: console - ./examples/l3fwd-power/build/l3fwd-power -l 1-3 -- -p 0x0f --config="(0,0,2),(0,1,3)" --empty-poll "1,0,0" –P + ./<build_dir>/examples/dpdk-l3fwd-power -l 1-3 -- -p 0x0f --config="(0,0,2),(0,1,3)" --empty-poll "1,0,0" –P This will run the training algorithm for x seconds on each core (cores 2 and 3), and then print out the recommended threshold values for those
@@ -432,7 +432,7 @@ then be started without the training mode so traffic can start immediately. .. code-block:: console - ./examples/l3fwd-power/build/l3fwd-power -l 1-3 -- -p 0x0f --config="(0,0,2),(0,1,3)" --empty-poll "0,340000,540000" –P + ./<build_dir>/examples/dpdk-l3fwd-power -l 1-3 -- -p 0x0f --config="(0,0,2),(0,1,3)" --empty-poll "0,340000,540000" –P Telemetry Mode --------------
@@ -449,13 +449,9 @@ cycles it took is measured and compared with minimum and maximum reference cycles and accordingly busy rate is set to either 0% or 50% or 100%. - .. Note:: - - * The CONFIG_RTE_LIBRTE_TELEMETRY should be set in order to get the stats in DPDK telemetry. - .. code-block:: console - ./examples/l3fwd-power/build/l3fwd-power --telemetry -l 1-3 -- -p 0x0f --config="(0,0,2),(0,1,3)" --telemetry + ./<build_dir>/examples/dpdk-l3fwd-power --telemetry -l 1-3 -- -p 0x0f --config="(0,0,2),(0,1,3)" --telemetry The new stats ``empty_poll`` , ``full_poll`` and ``busy_percent`` can be viewed by running the script ``/usertools/dpdk-telemetry-client.py`` and selecting the menu option ``Send for global Metrics``.
doc/guides/sample_app_ug/link_status_intr.rst +2 -2
@@ -39,7 +39,7 @@ The application requires a number of command line options: .. code-block:: console - ./build/link_status_interrupt [EAL options] -- -p PORTMASK [-q NQ][-T PERIOD] + ./<build_dir>/examples/dpdk-link_status_interrupt [EAL options] -- -p PORTMASK [-q NQ][-T PERIOD] where,
@@ -54,7 +54,7 @@ issue the command: .. code-block:: console - $ ./build/link_status_interrupt -l 0-3 -n 4-- -q 8 -p ffff + $ ./<build_dir>/examples/dpdk-link_status_interrupt -l 0-3 -n 4-- -q 8 -p ffff Refer to the *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL) options.
doc/guides/sample_app_ug/multi_process.rst +10 -10
@@ -41,7 +41,7 @@ passing at least two cores in the coremask/corelist, as follows: .. code-block:: console - ./build/simple_mp -l 0-1 -n 4 --proc-type=primary + ./<build_dir>/examples/dpdk-simple_mp -l 0-1 -n 4 --proc-type=primary For the first DPDK process run, the proc-type flag can be omitted or set to auto, since all DPDK processes will default to being a primary instance,
@@ -50,7 +50,7 @@ The process should start successfully and display a command prompt as follows: .. code-block:: console - $ ./build/simple_mp -l 0-1 -n 4 --proc-type=primary + $ ./<build_dir>/examples/dpdk-simple_mp -l 0-1 -n 4 --proc-type=primary EAL: coremask set to 3 EAL: Detected lcore 0 on socket 0 EAL: Detected lcore 1 on socket 0
@@ -78,7 +78,7 @@ again run the same binary setting at least two cores in the coremask/corelist: .. code-block:: console - ./build/simple_mp -l 2-3 -n 4 --proc-type=secondary + ./<build_dir>/examples/dpdk-simple_mp -l 2-3 -n 4 --proc-type=secondary When running a secondary process such as that shown above, the proc-type parameter can again be specified as auto. However, omitting the parameter altogether will cause the process to try and start as a primary rather than secondary process.
@@ -184,10 +184,10 @@ the following commands can be used (assuming run as root): .. code-block:: console - # ./build/symmetric_mp -l 1 -n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=0 - # ./build/symmetric_mp -l 2 -n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=1 - # ./build/symmetric_mp -l 3 -n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=2 - # ./build/symmetric_mp -l 4 -n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=3 + # ./<build_dir>/examples/dpdk-symmetric_mp -l 1 -n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=0 + # ./<build_dir>/examples/dpdk-symmetric_mp -l 2 -n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=1 + # ./<build_dir>/examples/dpdk-symmetric_mp -l 3 -n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=2 + # ./<build_dir>/examples/dpdk-symmetric_mp -l 4 -n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=3 .. note::
@@ -284,9 +284,9 @@ the following commands could be used: .. code-block:: console - # ./mp_server/build/mp_server -l 1-2 -n 4 -- -p 3 -n 2 - # ./mp_client/build/mp_client -l 3 -n 4 --proc-type=auto -- -n 0 - # ./mp_client/build/mp_client -l 4 -n 4 --proc-type=auto -- -n 1 + # ./<build_dir>/examples/dpdk-mp_server -l 1-2 -n 4 -- -p 3 -n 2 + # ./<build_dir>/examples/dpdk-mp_client -l 3 -n 4 --proc-type=auto -- -n 0 + # ./<build_dir>/examples/dpdk-mp_client -l 4 -n 4 --proc-type=auto -- -n 1 .. note::
doc/guides/sample_app_ug/ntb.rst +1 -1
@@ -32,7 +32,7 @@ The only available options are the standard ones for the EAL: .. code-block:: console - ./build/ntb_fwd -c 0xf -n 6 -- -i + ./<build_dir>/examples/dpdk-ntb -c 0xf -n 6 -- -i Refer to the *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL)
doc/guides/sample_app_ug/packet_ordering.rst +2 -1
@@ -43,7 +43,8 @@ The application execution command line is: .. code-block:: console - ./packet_ordering [EAL options] -- -p PORTMASK [--disable-reorder] [--insight-worker] + ./<build_dir>/examples/dpdk-packet_ordering [EAL options] -- -p PORTMASK / + [--disable-reorder] [--insight-worker] The -c EAL CPU_COREMASK option has to contain at least 3 CPU cores. The first CPU core in the core mask is the master core and would be assigned to
doc/guides/sample_app_ug/performance_thread.rst +13 -31
121 lines not on this page · raw message
doc/guides/sample_app_ug/ptpclient.rst +1 -8
@@ -57,13 +57,6 @@ To compile the sample application see :doc:`compiling`. The application is located in the ``ptpclient`` sub-directory. -.. note:: - To compile the application edit the ``config/common_linux`` configuration file to enable IEEE1588 - and then recompile DPDK: - - .. code-block:: console - - CONFIG_RTE_LIBRTE_IEEE1588=y Running the Application -----------------------
@@ -72,7 +65,7 @@ To run the example in a ``linux`` environment: .. code-block:: console - ./build/ptpclient -l 1 -n 4 -- -p 0x1 -T 0 + ./<build_dir>/examples/dpdk-ptpclient -l 1 -n 4 -- -p 0x1 -T 0 Refer to *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL) options.
doc/guides/sample_app_ug/qos_metering.rst +1 -1
@@ -48,7 +48,7 @@ The application execution command line is as below: .. code-block:: console - ./qos_meter [EAL options] -- -p PORTMASK + ./dpdk-qos_meter [EAL options] -- -p PORTMASK The application is constrained to use a single core in the EAL core mask and 2 ports only in the application port mask (first port from the port mask is used for RX and the other port in the core mask is used for TX).
doc/guides/sample_app_ug/qos_scheduler.rst +5 -5
@@ -42,8 +42,8 @@ The application is located in the ``qos_sched`` sub-directory. .. note:: To get statistics on the sample app using the command line interface as described in the next section, - DPDK must be compiled defining *CONFIG_RTE_SCHED_COLLECT_STATS*, - which can be done by changing the configuration file for the specific target to be compiled. + DPDK must be compiled defining *RTE_SCHED_COLLECT_STATS*, which can be done by changing the relevant + entry in the ``config/rte_config.h`` file. Running the Application -----------------------
@@ -57,7 +57,7 @@ The application has a number of command line options: .. code-block:: console - ./qos_sched [EAL options] -- <APP PARAMS> + ./<build_dir>/examples/dpdk-qos_sched [EAL options] -- <APP PARAMS> Mandatory application parameters include:
@@ -315,7 +315,7 @@ The following is an example command with a single packet flow configuration: .. code-block:: console - ./qos_sched -l 1,5,7 -n 4 -- --pfc "3,2,5,7" --cfg ./profile.cfg + ./<build_dir>/examples/dpdk-qos_sched -l 1,5,7 -n 4 -- --pfc "3,2,5,7" --cfg ./profile.cfg This example uses a single packet flow configuration which creates one RX thread on lcore 5 reading from port 3 and a worker thread on lcore 7 writing to port 2.
@@ -324,7 +324,7 @@ Another example with 2 packet flow configurations using different ports but shar .. code-block:: console - ./qos_sched -l 1,2,6,7 -n 4 -- --pfc "3,2,2,6,7" --pfc "1,0,2,6,7" --cfg ./profile.cfg + ./<build_dir>/examples/dpdk-qos_sched -l 1,2,6,7 -n 4 -- --pfc "3,2,2,6,7" --pfc "1,0,2,6,7" --cfg ./profile.cfg Note that independent cores for the packet flow configurations for each of the RX, WT and TX thread are also supported, providing flexibility to balance the work.
doc/guides/sample_app_ug/rxtx_callbacks.rst +1 -8
@@ -25,13 +25,6 @@ To compile the sample application see :doc:`compiling`. The application is located in the ``rxtx_callbacks`` sub-directory. -The callbacks feature requires that the ``CONFIG_RTE_ETHDEV_RXTX_CALLBACKS`` -setting is on in the ``config/common_`` config file that applies to the -target. This is generally on by default: - -.. code-block:: console - - CONFIG_RTE_ETHDEV_RXTX_CALLBACKS=y Running the Application -----------------------
@@ -40,7 +33,7 @@ To run the example in a ``linux`` environment: .. code-block:: console - ./build/rxtx_callbacks -l 1 -n 4 -- [-t] + ./<build_dir>/examples/dpdk-rxtx_callbacks -l 1 -n 4 -- [-t] Use -t to enable hardware timestamping. If not supported by the NIC, an error will be displayed.
doc/guides/sample_app_ug/server_node_efd.rst +1 -1
@@ -93,7 +93,7 @@ and the back-end node. The frontend server (server) has the following command line options:: - ./server [EAL options] -- -p PORTMASK -n NUM_NODES -f NUM_FLOWS + ./<build_dir>/examples/dpdk-server [EAL options] -- -p PORTMASK -n NUM_NODES -f NUM_FLOWS Where,
doc/guides/sample_app_ug/service_cores.rst +3 -20
@@ -20,26 +20,9 @@ is application specific, and not a part of the service cores API. Compiling the Application ------------------------- -#. Go to the example directory: +To compile the sample application see :doc:`compiling`. - .. code-block:: console - - export RTE_SDK=/path/to/rte_sdk - cd ${RTE_SDK}/examples/service_cores - -#. Set the target (a default target is used if not specified). For example: - - .. code-block:: console - - export RTE_TARGET=x86_64-native-linux-gcc - - See the *DPDK Getting Started* Guide for possible RTE_TARGET values. - -#. Build the application: - - .. code-block:: console - - make +The application is located in the ``service_cores`` sub-directory. Running the Application -----------------------
@@ -50,7 +33,7 @@ pass a service core-mask as an EAL argument at startup time. .. code-block:: console - $ ./build/service_cores + $ ./<build_dir>/examples/dpdk-service_cores Explanation
doc/guides/sample_app_ug/skeleton.rst +1 -1
@@ -25,7 +25,7 @@ To run the example in a ``linux`` environment: .. code-block:: console - ./build/basicfwd -l 1 -n 4 + ./<build_dir>/examples/dpdk-skeleton -l 1 -n 4 Refer to *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL) options.
doc/guides/sample_app_ug/tep_termination.rst +12 -31
97 lines not on this page · raw message
doc/guides/sample_app_ug/test_pipeline.rst +2 -2
@@ -32,7 +32,7 @@ Compiling the Application ------------------------- To compile the sample application see :doc:`compiling` -The application is located in the ``$RTE_SDK/app/test-pipeline`` directory. +The application is located in the ``dpdk/<build_dir>/app`` directory. Running the Application
@@ -45,7 +45,7 @@ The application execution command line is: .. code-block:: console - ./test-pipeline [EAL options] -- -p PORTMASK --TABLE_TYPE + ./dpdk-test-pipeline [EAL options] -- -p PORTMASK --TABLE_TYPE The -c or -l EAL CPU coremask/corelist option has to contain exactly 3 CPU cores. The first CPU core in the core mask is assigned for core A, the second for core B and the third for core C.
doc/guides/sample_app_ug/timer.rst +1 -1
@@ -21,7 +21,7 @@ To run the example in linux environment: .. code-block:: console - $ ./build/timer -l 0-3 -n 4 + $ ./<build_dir>/examples/dpdk-timer -l 0-3 -n 4 Refer to the *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL) options.
doc/guides/sample_app_ug/vdpa.rst +2 -2
@@ -29,7 +29,7 @@ Start the vdpa example .. code-block:: console - ./vdpa [EAL options] -- [--client] [--interactive|-i] or [--iface SOCKET_PATH] + ./dpdk-vdpa [EAL options] -- [--client] [--interactive|-i] or [--iface SOCKET_PATH] where
@@ -51,7 +51,7 @@ Take IFCVF driver for example: .. code-block:: console - ./vdpa -c 0x2 -n 4 --socket-mem 1024,1024 \ + ./dpdk-vdpa -c 0x2 -n 4 --socket-mem 1024,1024 \ -w 0000:06:00.3,vdpa=1 -w 0000:06:00.4,vdpa=1 \ -- --interactive
doc/guides/sample_app_ug/vhost.rst +3 -8
@@ -38,7 +38,7 @@ Start the vswitch example .. code-block:: console - ./vhost-switch -l 0-3 -n 4 --socket-mem 1024 \ + ./dpdk-vhost-switch -l 0-3 -n 4 --socket-mem 1024 \ -- --socket-file /tmp/sock0 --client \ ...
@@ -78,13 +78,13 @@ could be done by: .. code-block:: console modprobe uio_pci_generic - $RTE_SDK/usertools/dpdk-devbind.py -b uio_pci_generic 0000:00:04.0 + dpdk/usertools/dpdk-devbind.py -b uio_pci_generic 0000:00:04.0 Then start testpmd for packet forwarding testing. .. code-block:: console - ./x86_64-native-gcc/app/testpmd -l 0-1 -- -i + ./<build_dir>/app/dpdk-testpmd -l 0-1 -- -i > start tx_first Inject packets
@@ -192,11 +192,6 @@ Common Issues max queue number is larger than 128, device start will fail due to insufficient mbuf. - Change the default number to make it work as below, just set the number - according to the NIC's property. :: - - make EXTRA_CFLAGS="-DMAX_QUEUES=320" - * Option "builtin-net-driver" is incompatible with QEMU QEMU vhost net device start will fail if protocol feature is not negotiated.
doc/guides/sample_app_ug/vhost_blk.rst +1 -1
@@ -36,7 +36,7 @@ Start the vhost_blk example .. code-block:: console - ./vhost_blk -m 1024 + ./dpdk-vhost_blk -m 1024 .. _vhost_blk_app_run_vm:
doc/guides/sample_app_ug/vhost_crypto.rst +1 -1
@@ -28,7 +28,7 @@ Start the vhost_crypto example .. code-block:: console - ./vhost_crypto [EAL options] -- + ./dpdk-vhost_crypto [EAL options] -- --config (lcore,cdev-id,queue-id)[,(lcore,cdev-id,queue-id)] --socket-file lcore,PATH [--zero-copy]
doc/guides/sample_app_ug/vm_power_management.rst +14 -20
@@ -245,26 +245,23 @@ To build just the ``vm_power_manager`` application using ``make``: .. code-block:: console - export RTE_SDK=/path/to/rte_sdk - export RTE_TARGET=build - cd ${RTE_SDK}/examples/vm_power_manager/ + cd dpdk/examples/vm_power_manager/ make -The resulting binary is ``${RTE_SDK}/build/examples/vm_power_manager``. +The resulting binary is ``dpdk/build/examples/vm_power_manager``. To build just the ``vm_power_manager`` application using ``meson``/``ninja``: .. code-block:: console - export RTE_SDK=/path/to/rte_sdk - cd ${RTE_SDK} + cd dpdk meson build cd build ninja meson configure -Dexamples=vm_power_manager ninja -The resulting binary is ``${RTE_SDK}/build/examples/dpdk-vm_power_manager``. +The resulting binary is ``dpdk/build/examples/dpdk-vm_power_manager``. Running the Host Application ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -274,7 +271,7 @@ than the EAL options: .. code-block:: console - ./build/vm_power_mgr [EAL options] + ./<build_dir>/examples/dpdk-vm_power_mgr [EAL options] The application requires exactly two cores to run. One core for the CLI and the other for the channel endpoint monitor. For example, to run on
@@ -282,7 +279,7 @@ cores 0 and 1 on a system with four memory channels, issue the command: .. code-block:: console - ./build/vm_power_mgr -l 0-1 -n 4 + ./<build_dir>/examples/dpdk-vm_power_mgr -l 0-1 -n 4 After successful initialization, the VM Power Manager CLI prompt appears:
@@ -462,12 +459,10 @@ the following commands: .. code-block:: console - export RTE_SDK=/path/to/rte_sdk - export RTE_TARGET=build - cd ${RTE_SDK}/examples/vm_power_manager/guest_cli/ + cd dpdk/examples/vm_power_manager/guest_cli/ make -The resulting binary is ``${RTE_SDK}/build/examples/guest_cli``. +The resulting binary is ``dpdk/build/examples/guest_cli``. **Note**: This sample application conditionally links in the Jansson JSON library. Consequently, if you are using a multilib or cross-compile
@@ -498,15 +493,14 @@ To build just the ``vm_power_manager`` application using ``meson``/``ninja``: .. code-block:: console - export RTE_SDK=/path/to/rte_sdk - cd ${RTE_SDK} + cd dpdk meson build cd build ninja meson configure -Dexamples=vm_power_manager/guest_cli ninja -The resulting binary is ``${RTE_SDK}/build/examples/guest_cli``. +The resulting binary is ``dpdk/build/examples/guest_cli``. Running the Guest Application ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -515,14 +509,14 @@ The standard EAL command line parameters are necessary: .. code-block:: console - ./build/vm_power_mgr [EAL options] -- [guest options] + ./<build_dir>/examples/dpdk-vm_power_mgr [EAL options] -- [guest options] The guest example uses a channel for each lcore enabled. For example, to run on cores 0, 1, 2 and 3: .. code-block:: console - ./build/guest_vm_power_mgr -l 0-3 + ./<build_dir>/examples/dpdk-guest_vm_power_mgr -l 0-3 .. _sending_policy:
@@ -593,7 +587,7 @@ host, use a command like the following: .. code-block:: console - ./build/guest_vm_power_mgr -l 0-3 -n 4 -- --vm-name=ubuntu --policy=BRANCH_RATIO --vcpu-list=2-4 + ./<build_dir>/examples/dpdk-guest_vm_power_mgr -l 0-3 -n 4 -- --vm-name=ubuntu --policy=BRANCH_RATIO --vcpu-list=2-4 Once the VM Power Manager Guest CLI appears, issuing the 'send_policy now' command will send the policy to the host:
@@ -707,7 +701,7 @@ To start the application and configure the power policy, and send it to the host .. code-block:: console - ./build/guest_vm_power_mgr -l 0-3 -n 4 -- --vm-name=ubuntu --policy=BRANCH_RATIO --vcpu-list=2-4 + ./<build_dir>/examples/dpdk-guest_vm_power_mgr -l 0-3 -n 4 -- --vm-name=ubuntu --policy=BRANCH_RATIO --vcpu-list=2-4 Once the VM Power Manager Guest CLI appears, issuing the 'send_policy now' command will send the policy to the host:
doc/guides/sample_app_ug/vmdq_dcb_forwarding.rst +4 -4
@@ -26,13 +26,13 @@ multiple queues. When run with 8 threads, that is, with the -c FF option, each t As supplied, the sample application configures the VMDQ feature to have 32 pools with 4 queues each as indicated in :numref:`figure_vmdq_dcb_example`. The Intel® 82599 10 Gigabit Ethernet Controller NIC also supports the splitting of traffic into 16 pools of 8 queues. While the Intel® X710 or XL710 Ethernet Controller NICs support many configurations of VMDQ pools of 4 or 8 queues each. For simplicity, only 16 -or 32 pools is supported in this sample. And queues numbers for each VMDQ pool can be changed by setting CONFIG_RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM -in config/common_* file. +or 32 pools is supported in this sample. And queues numbers for each VMDQ pool can be changed by setting RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM +in config/rte_config.h file. The nb-pools, nb-tcs and enable-rss parameters can be passed on the command line, after the EAL parameters: .. code-block:: console - ./build/vmdq_dcb [EAL options] -- -p PORTMASK --nb-pools NP --nb-tcs TC --enable-rss + ./<build_dir>/examples/dpdk-vmdq_dcb [EAL options] -- -p PORTMASK --nb-pools NP --nb-tcs TC --enable-rss where, NP can be 16 or 32, TC can be 4 or 8, rss is disabled by default.
@@ -72,7 +72,7 @@ To run the example in a linux environment: .. code-block:: console - user@target:~$ ./build/vmdq_dcb -l 0-3 -n 4 -- -p 0x3 --nb-pools 32 --nb-tcs 4 + user@target:~$ ./<build_dir>/examples/dpdk-vmdq_dcb -l 0-3 -n 4 -- -p 0x3 --nb-pools 32 --nb-tcs 4 Refer to the *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL) options.
doc/guides/sample_app_ug/vmdq_forwarding.rst +4 -4
@@ -24,13 +24,13 @@ multiple queues. When run with 8 threads, that is, with the -c FF option, each t As supplied, the sample application configures the VMDq feature to have 32 pools with 4 queues each. The Intel® 82599 10 Gigabit Ethernet Controller NIC also supports the splitting of traffic into 16 pools of 2 queues. While the Intel® X710 or XL710 Ethernet Controller NICs support many configurations of VMDq pools of 4 or 8 queues each. -And queues numbers for each VMDq pool can be changed by setting CONFIG_RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM -in config/common_* file. +And queues numbers for each VMDq pool can be changed by setting RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM +in config/rte_config.h file. The nb-pools and enable-rss parameters can be passed on the command line, after the EAL parameters: .. code-block:: console - ./build/vmdq_app [EAL options] -- -p PORTMASK --nb-pools NP --enable-rss + ./<build_dir>/examples/dpdk-vmdq [EAL options] -- -p PORTMASK --nb-pools NP --enable-rss where, NP can be 8, 16 or 32, rss is disabled by default.
@@ -56,7 +56,7 @@ To run the example in a Linux environment: .. code-block:: console - user@target:~$ ./build/vmdq_app -l 0-3 -n 4 -- -p 0x3 --nb-pools 16 + user@target:~$ ./<build_dir>/examples/dpdk-vmdq -l 0-3 -n 4 -- -p 0x3 --nb-pools 16 Refer to the *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL) options.
Signature · 1 line
2.17.1
Re: [dpdk-dev] [PATCH v3 33/37] doc: remove references to make in sample app guides
PATCH v3 34/37 doc: remove references to make in vdpadevs guides
In reply to Ciara PowerMake is no longer supported for compiling DPDK, references are now removed in the documentation.
--- doc/guides/vdpadevs/ifc.rst | 13 ------------ doc/guides/vdpadevs/mlx5.rst | 40 +++--------------------------------- 2 files changed, 3 insertions(+), 50 deletions(-)
doc/guides/vdpadevs/ifc.rst +0 -13
@@ -11,19 +11,6 @@ directly by DMA. Besides, it supports dirty page logging and device state report/restore, this driver enables its vDPA functionality. -Pre-Installation Configuration ------------------------------- - -Config File Options -~~~~~~~~~~~~~~~~~~~ - -The following option can be modified in the ``config`` file. - -- ``CONFIG_RTE_LIBRTE_IFC_PMD`` (default ``y`` for linux) - - Toggle compilation of the ``librte_pmd_ifc`` driver. - - IFCVF vDPA Implementation -------------------------
doc/guides/vdpadevs/mlx5.rst +3 -37
@@ -14,9 +14,7 @@ SR-IOV context. .. note:: - Due to external dependencies, this driver is disabled in default - configuration of the "make" build. It can be enabled with - ``CONFIG_RTE_LIBRTE_MLX5_VDPA_PMD=y`` or by using "meson" build system which + This driver is enabled automatically when using "meson" build system which will detect dependencies.
@@ -65,42 +63,10 @@ Prerequisites Compilation options ~~~~~~~~~~~~~~~~~~~ -These options can be modified in the ``.config`` file. - -- ``CONFIG_RTE_LIBRTE_MLX5_VDPA_PMD`` (default **n**) - - Toggle compilation of librte_pmd_mlx5 itself. - -- ``CONFIG_RTE_IBVERBS_LINK_DLOPEN`` (default **n**) - - Build PMD with additional code to make it loadable without hard - dependencies on **libibverbs** nor **libmlx5**, which may not be installed - on the target system. - - In this mode, their presence is still required for it to run properly, - however their absence won't prevent a DPDK application from starting (with - ``CONFIG_RTE_BUILD_SHARED_LIB`` disabled) and they won't show up as - missing with ``ldd(1)``. - - It works by moving these dependencies to a purpose-built rdma-core "glue" - plug-in which must either be installed in a directory whose name is based - on ``CONFIG_RTE_EAL_PMD_PATH`` suffixed with ``-glue`` if set, or in a - standard location for the dynamic linker (e.g. ``/lib``) if left to the - default empty string (``""``). - - This option has no performance impact. - -- ``CONFIG_RTE_IBVERBS_LINK_STATIC`` (default **n**) - - Embed static flavor of the dependencies **libibverbs** and **libmlx5** - in the PMD shared library or the executable static binary. - .. note:: - For BlueField, target should be set to ``arm64-bluefield-linux-gcc``. This - will enable ``CONFIG_RTE_LIBRTE_MLX5_VDPA_PMD`` and set - ``RTE_CACHE_LINE_SIZE`` to 64. Default armv8a configuration of make build and - meson build set it to 128 then brings performance degradation. + Default armv8a configuration of meson build sets ``RTE_CACHE_LINE_SIZE`` + to 128 then brings performance degradation. Run-time configuration ~~~~~~~~~~~~~~~~~~~~~~
Signature · 1 line
2.17.1
PATCH v3 35/37 doc: remove reference to make in tools guides
In reply to Ciara PowerMake is no longer supported for compiling DPDK, references are now removed in the documentation.
--- doc/guides/tools/comp_perf.rst | 10 ++------- doc/guides/tools/cryptoperf.rst | 20 +++-------------- doc/guides/tools/pdump.rst | 15 ++++++------- doc/guides/tools/proc_info.rst | 2 +- doc/guides/tools/testbbdev.rst | 36 +++++++++---------------------- doc/guides/tools/testeventdev.rst | 21 ++++++++---------- 6 files changed, 31 insertions(+), 73 deletions(-)
doc/guides/tools/comp_perf.rst +2 -8
@@ -100,13 +100,7 @@ Application Options Compiling the Tool ------------------ -**Step 1: PMD setting** - -The ``dpdk-test-compress-perf`` tool depends on compression device drivers PMD which -can be disabled by default in the build configuration file ``common_base``. -The compression device drivers PMD which should be tested can be enabled by setting e.g.:: - - CONFIG_RTE_LIBRTE_PMD_ISAL=y +See :doc:`../linux_gsg/build_dpdk.rst` for compilation steps. Running the Tool
@@ -116,5 +110,5 @@ The tool has a number of command line options. Here is the sample command line: .. code-block:: console - ./build/app/dpdk-test-compress-perf -l 4 -- --driver-name compress_qat --input-file test.txt --seg-sz 8192 + ./<build_dir>/app/dpdk-test-compress-perf -l 4 -- --driver-name compress_qat --input-file test.txt --seg-sz 8192 --compress-level 1:1:9 --num-iter 10 --extended-input-sz 1048576 --max-num-sgl-segs 16 --huffman-enc fixed
doc/guides/tools/cryptoperf.rst +3 -17
@@ -33,19 +33,8 @@ the hardware accelerator fully loaded and so measure maximum throughput. Compiling the Application ------------------------- -**Step 1: PMD setting** -The ``dpdk-test-crypto-perf`` tool depends on crypto device drivers PMD which -are disabled by default in the build configuration file ``common_base``. -The crypto device drivers PMD which should be tested can be enabled by setting:: - - CONFIG_RTE_LIBRTE_PMD_<name>=y - -Setting example for open ssl PMD:: - - CONFIG_RTE_LIBRTE_PMD_OPENSSL=y - -**Step 2: Linearization setting** +**Step 1: Linearization setting** It is possible linearized input segmented packets just before crypto operation for devices which doesn't support scatter-gather, and allows to measure
@@ -56,13 +45,10 @@ To set on the linearization options add below definition to the #define CPERF_LINEARIZATION_ENABLE -**Step 3: Build the application** +**Step 2: Build the application** -Execute the ``dpdk-setup.sh`` script to build the DPDK library together with the -``dpdk-test-crypto-perf`` application. +See :doc:`../linux_gsg/build_dpdk.rst` for compilation steps. -Initially, the user must select a DPDK target to choose the correct target type -and compiler options to use when building the libraries. The user must have all libraries, modules, updates and compilers installed in the system prior to this, as described in the earlier chapters in this Getting Started Guide.
doc/guides/tools/pdump.rst +6 -9
@@ -19,12 +19,9 @@ a DPDK secondary process and is capable of enabling packet capture on dpdk ports framework initialization code. Refer ``app/test-pmd/testpmd.c`` code to see how this is done. - * The ``dpdk-pdump`` tool depends on libpcap based PMD which is disabled - by default in the build configuration files, - owing to an external dependency on the libpcap development files - which must be installed on the board. - Once the libpcap development files are installed, the libpcap based PMD - can be enabled by setting CONFIG_RTE_LIBRTE_PMD_PCAP=y and recompiling the DPDK. + * The ``dpdk-pdump`` tool depends on libpcap based PMD which must be + installed on the board. + Once the libpcap development files are installed, recompile the DPDK. * The ``dpdk-pdump`` tool runs as a DPDK secondary process. It exits when the primary application exits.
@@ -37,7 +34,7 @@ The tool has a number of command line options: .. code-block:: console - ./build/app/dpdk-pdump -- + ./<build_dir>/app/dpdk-pdump -- [--multi] --pdump '(port=<port id> | device_id=<pci id or vdev name>), (queue=<queue_id>),
@@ -120,5 +117,5 @@ Example .. code-block:: console - $ sudo ./build/app/dpdk-pdump -l 3 -- --pdump 'port=0,queue=*,rx-dev=/tmp/rx.pcap' - $ sudo ./build/app/dpdk-pdump -l 3,4,5 -- --multi --pdump 'port=0,queue=*,rx-dev=/tmp/rx-1.pcap' --pdump 'port=1,queue=*,rx-dev=/tmp/rx-2.pcap' + $ sudo ./<build_dir>/app/dpdk-pdump -l 3 -- --pdump 'port=0,queue=*,rx-dev=/tmp/rx.pcap' + $ sudo ./<build_dir>/app/dpdk-pdump -l 3,4,5 -- --multi --pdump 'port=0,queue=*,rx-dev=/tmp/rx-1.pcap' --pdump 'port=1,queue=*,rx-dev=/tmp/rx-2.pcap'
doc/guides/tools/proc_info.rst +1 -1
@@ -17,7 +17,7 @@ The application has a number of command line options: .. code-block:: console - ./$(RTE_TARGET)/app/dpdk-procinfo -- -m | [-p PORTMASK] [--stats | --xstats | + ./<build_dir>/app/dpdk-procinfo -- -m | [-p PORTMASK] [--stats | --xstats | --stats-reset | --xstats-reset] [ --show-port | --show-tm | --show-crypto | --show-ring[=name] | --show-mempool[=name] | --iter-mempool=name ]
doc/guides/tools/testbbdev.rst +10 -26
@@ -13,25 +13,10 @@ parameters passed to a python running script. Compiling the Application ------------------------- -**Step 1: PMD setting** +**Build the application** -The ``dpdk-test-bbdev`` tool depends on crypto device drivers PMD which -are disabled by default in the build configuration file ``common_base``. -The bbdevice drivers PMD which should be tested can be enabled by setting +See :doc:`../linux_gsg/build_dpdk.rst` for compilation steps. - ``CONFIG_RTE_LIBRTE_PMD_<name>=y`` - -Setting example for (*baseband_turbo_sw*) PMD - - ``CONFIG_RTE_LIBRTE_PMD_BBDEV_TURBO_SW=y`` - -**Step 2: Build the application** - -Execute the ``dpdk-setup.sh`` script to build the DPDK library together with the -``dpdk-test-bbdev`` application. - -Initially, the user must select a DPDK target to choose the correct target type -and compiler options to use when building the libraries. The user must have all libraries, modules, updates and compilers installed in the system prior to this, as described in the earlier chapters in this Getting Started Guide.
@@ -60,7 +45,7 @@ The following are the command-line options: ``-p TESTAPP_PATH, --testapp_path TESTAPP_PATH`` Indicates the path to the bbdev test app. If not specified path is set based - on *$RTE_SDK* environment variable concatenated with "*/build/app/testbbdev*". + on "../.." concatenated with "*/build/app/testbbdev*". ``-e EAL_PARAMS, --eal_params EAL_PARAMS`` Specifies EAL arguments which are passed to the test app. For more details,
@@ -82,9 +67,8 @@ The following are the command-line options: ``-v TEST_VECTOR [TEST_VECTOR ...], --test_vector TEST_VECTOR [TEST_VECTOR ...]`` Specifies paths to the test vector files. If not specified path is set based - on *$RTE_SDK* environment variable concatenated with - "*/app/test-bbdev/test_vectors/bbdev_null.data*" and indicates default - data file. + on "../.." concatenated with "*/app/test-bbdev/test_vectors/bbdev_null.data*" +and indicates default data file. **Example usage:**
@@ -259,8 +243,8 @@ They are chosen to have a good coverage across sizes and processing parameters while still keeping their number limited as part of sanity regression. -Shortened tree of isg_cid-wireless_dpdk_ae with dpdk compiled for -x86_64-native-linux-icc target: +Shortened tree of isg_cid-wireless_dpdk_ae with dpdk compiled and output +to the build directory: ::
@@ -268,7 +252,7 @@ x86_64-native-linux-icc target: |-- test-bbdev |-- test_vectors - |-- x86_64-native-linux-icc + |-- build |-- app |-- testbbdev
@@ -277,7 +261,7 @@ All bbdev devices .. code-block:: console - ./test-bbdev.py -p ../../x86_64-native-linux-icc/app/testbbdev + ./test-bbdev.py -p ../../build/app/dpdk-test-bbdev -v turbo_dec_default.data It runs all available tests using the test vector filled based on
@@ -291,7 +275,7 @@ baseband turbo_sw device .. code-block:: console - ./test-bbdev.py -p ../../x86_64-native-linux-icc/app/testbbdev + ./test-bbdev.py -p ../../build/app/dpdk-test-bbdev -e="--vdev=baseband_turbo_sw" -t 120 -c validation -v ./test_vectors/* -n 64 -b 8 32
doc/guides/tools/testeventdev.rst +9 -12
@@ -15,11 +15,8 @@ Compiling the Application **Build the application** -Execute the ``dpdk-setup.sh`` script to build the DPDK library together with the -``dpdk-test-eventdev`` application. +See :doc:`../linux_gsg/build_dpdk.rst` for compilation steps. -Initially, the user must select a DPDK target to choose the correct target type -and compiler options to use when building the libraries. The user must have all libraries, modules, updates and compilers installed in the system prior to this, as described in the earlier chapters in this Getting Started Guide.
@@ -251,7 +248,7 @@ Example command to run order queue test: .. code-block:: console - sudo build/app/dpdk-test-eventdev --vdev=event_sw0 -- \ + sudo <build_dir>/app/dpdk-test-eventdev --vdev=event_sw0 -- \ --test=order_queue --plcores 1 --wlcores 2,3
@@ -314,7 +311,7 @@ Example command to run order ``all types queue`` test: .. code-block:: console - sudo build/app/dpdk-test-eventdev --vdev=event_octeontx -- \ + sudo <build_dir>/app/dpdk-test-eventdev --vdev=event_octeontx -- \ --test=order_atq --plcores 1 --wlcores 2,3
@@ -414,7 +411,7 @@ Example command to run perf queue test: .. code-block:: console - sudo build/app/dpdk-test-eventdev -c 0xf -s 0x1 --vdev=event_sw0 -- \ + sudo <build_dir>/app/dpdk-test-eventdev -c 0xf -s 0x1 --vdev=event_sw0 -- \ --test=perf_queue --plcores=2 --wlcore=3 --stlist=p --nb_pkts=0 Example command to run perf queue test with ethernet ports:
@@ -428,7 +425,7 @@ Example command to run perf queue test with event timer adapter: .. code-block:: console - sudo build/app/dpdk-test-eventdev --vdev="event_octeontx" -- \ + sudo <build_dir>/app/dpdk-test-eventdev --vdev="event_octeontx" -- \ --wlcores 4 --plcores 12 --test perf_queue --stlist=a \ --prod_type_timerdev --fwd_latency
@@ -514,14 +511,14 @@ Example command to run perf ``all types queue`` test: .. code-block:: console - sudo build/app/dpdk-test-eventdev --vdev=event_octeontx -- \ + sudo <build_dir>/app/dpdk-test-eventdev --vdev=event_octeontx -- \ --test=perf_atq --plcores=2 --wlcore=3 --stlist=p --nb_pkts=0 Example command to run perf ``all types queue`` test with event timer adapter: .. code-block:: console - sudo build/app/dpdk-test-eventdev --vdev="event_octeontx" -- \ + sudo <build_dir>/app/dpdk-test-eventdev --vdev="event_octeontx" -- \ --wlcores 4 --plcores 12 --test perf_atq --verbose 20 \ --stlist=a --prod_type_timerdev --fwd_latency
@@ -633,7 +630,7 @@ Example command to run pipeline queue test: .. code-block:: console - sudo build/app/dpdk-test-eventdev -c 0xf -s 0x8 --vdev=event_sw0 -- \ + sudo <build_dir>/app/dpdk-test-eventdev -c 0xf -s 0x8 --vdev=event_sw0 -- \ --test=pipeline_queue --wlcore=1 --prod_type_ethdev --stlist=a
@@ -725,5 +722,5 @@ Example command to run pipeline queue test: .. code-block:: console - sudo build/app/dpdk-test-eventdev -c 0xf -s 0x8 --vdev=event_sw0 -- \ + sudo <build_dir>/app/dpdk-test-eventdev -c 0xf -s 0x8 --vdev=event_sw0 -- \ --test=pipeline_atq --wlcore=1 --prod_type_ethdev --stlist=a
Signature · 1 line
2.17.1
Re: [dpdk-dev] [PATCH v3 35/37] doc: remove reference to make in tools guides
Hi Ciara,
Fine with me for test-bbdev. (Ignore my parallel comment to point more explicitly to the build stage directory, that is already fine below).
Quoted 350 lines
-----Original Message-----
From: Power, Ciara <[email protected]>
Sent: Thursday, September 3, 2020 8:27 AM
To: [email protected]
Cc: Power, Ciara <[email protected]>; Mcnamara, John <[email protected]>; Kovacevic, Marko <[email protected]>; Doherty, Declan <[email protected]>; Pattan, Reshma <[email protected]>; Tahhan, Maryam <[email protected]>; Chautru, Nicolas <[email protected]>; Jerin Jacob <[email protected]>
Subject: [PATCH v3 35/37] doc: remove reference to make in tools guidesMake is no longer supported for compiling DPDK, references are now removed in the documentation.
Signed-off-by Ciara Power <[email protected]>Reviewed-by Kevin Laatz <[email protected]>--- doc/guides/tools/comp_perf.rst | 10 ++------- doc/guides/tools/cryptoperf.rst | 20 +++-------------- doc/guides/tools/pdump.rst | 15 ++++++------- doc/guides/tools/proc_info.rst | 2 +- doc/guides/tools/testbbdev.rst | 36 +++++++++---------------------- doc/guides/tools/testeventdev.rst | 21 ++++++++---------- 6 files changed, 31 insertions(+), 73 deletions(-)doc/guides/tools/comp_perf.rst +0
-3@@ -100,13 +100,7 @@ Application Options Compiling the Tool ------------------ -**Step 1: PMD setting** - -The ``dpdk-test-compress-perf`` tool depends on compression device driversPMD which -can be disabled by default in the build configuration file ``common_base``.
-The compression device drivers PMD which should be tested can be enabled by setting e.g.::doc/guides/tools/comp_perf.rst +1
-2- - CONFIG_RTE_LIBRTE_PMD_ISAL=y +See :doc:`../linux_gsg/build_dpdk.rst` for compilation steps. Running the Tool@@ -116,5 +110,5 @@ The tool has a number of command line options. Hereis the sample command line:
.. code-block:: console
- ./build/app/dpdk-test-compress-perf -l 4 -- --driver-name
compress_qat--
input-file test.txt --seg-sz 8192
+ ./<build_dir>/app/dpdk-test-compress-perf -l 4 -- --driver-name
+compress_qat--input-file test.txt --seg-sz 8192--compress-level 1:1:9 --num-iter 10 --extended-input-sz 1048576 --max-num-sgl-segs 16 --huffman-enc fixed diff --git
a/doc/guides/tools/cryptoperf.rstb/doc/guides/tools/cryptoperf.rstindex28b729dbda..e7ea2ba1a5100644doc/guides/tools/cryptoperf.rst +0
-0@@ -33,19 +33,8 @@ the hardware accelerator fully loaded and so measuremaximum throughput.
Compiling the Application
-------------------------doc/guides/tools/cryptoperf.rst +0
-4-**Step 1: PMD setting** -The ``dpdk-test-crypto-perf`` tool depends on crypto device drivers PMD which -are disabled by default in the build configuration file ``common_base``. -The crypto device drivers PMD which should be tested can be enabled bysetting::
doc/guides/tools/cryptoperf.rst +1
-8- - CONFIG_RTE_LIBRTE_PMD_<name>=y - -Setting example for open ssl PMD:: - - CONFIG_RTE_LIBRTE_PMD_OPENSSL=y - -**Step 2: Linearization setting** +**Step 1: Linearization setting** It is possible linearized input segmented packets just before crypto operationfor devices which doesn't support scatter-gather, and allows to measure @@ - 56,13 +45,10 @@ To set on the linearization options add below definition to the
#define CPERF_LINEARIZATION_ENABLEdoc/guides/tools/cryptoperf.rst +2
-4-**Step 3: Build the application** +**Step 2: Build the application** -Execute the ``dpdk-setup.sh`` script to build the DPDK library together with the -``dpdk-test-crypto-perf`` application. +See :doc:`../linux_gsg/build_dpdk.rst` for compilation steps. -Initially, the user must select a DPDK target to choose the correct target type -and compiler options to use when building the libraries.
The user must have all libraries, modules, updates and compilers installed in
the system prior to this, as described in the earlier chapters in this Getting Started Guide.doc/guides/tools/pdump.rst index renamed from doc/guides/tools/pdump.rst +0
-0
8a499c6c5b..70f03db9cc100644doc/guides/tools/pdump.rst +0
-0@@ -19,12 +19,9 @@ a DPDK secondary process and is capable of enablingpacket capture on dpdk ports
framework initialization code. Refer ``app/test-pmd/testpmd.c`` code to see how this is done.- * The ``dpdk-pdump`` tool depends on libpcap based PMD which is
disableddoc/guides/tools/pdump.rst +0
-5- by default in the build configuration files, - owing to an external dependency on the libpcap development files - which must be installed on the board. - Once the libpcap development files are installed, the libpcap based PMD - can be enabled by setting CONFIG_RTE_LIBRTE_PMD_PCAP=y andrecompiling the DPDK.
doc/guides/tools/pdump.rst +4
-1+ * The ``dpdk-pdump`` tool depends on libpcap based PMD which must be + installed on the board. + Once the libpcap development files are installed, recompile the DPDK. * The ``dpdk-pdump`` tool runs as a DPDK secondary process. It exits when the primary application exits.@@ -37,7 +34,7 @@ The tool has a number of command line options: .. code-block:: console - ./build/app/dpdk-pdump -- + ./<build_dir>/app/dpdk-pdump -- [--multi] --pdump '(port=<port id> | device_id=<pci id or vdev name>), (queue=<queue_id>), @@ -120,5 +117,5 @@ Example.. code-block:: console
- $ sudo ./build/app/dpdk-pdump -l 3 -- --pdump 'port=0,queue=*,rx-
dev=/tmp/rx.pcap'
- $ sudo ./build/app/dpdk-pdump -l 3,4,5 -- --multi --pdump
'port=0,queue=*,rx-dev=/tmp/rx-1.pcap' --pdump 'port=1,queue=*,rx- dev=/tmp/rx-2.pcap'
+ $ sudo ./<build_dir>/app/dpdk-pdump -l 3 -- --pdump 'port=0,queue=*,rx-
dev=/tmp/rx.pcap'
+ $ sudo ./<build_dir>/app/dpdk-pdump -l 3,4,5 -- --multi --pdump
'port=0,queue=*,rx-dev=/tmp/rx-1.pcap' --pdump 'port=1,queue=*,rx- dev=/tmp/rx-2.pcap'doc/guides/tools/proc_info.rst +0
-1@@ -17,7 +17,7 @@ The application has a number of command line options: .. code-block:: console - ./$(RTE_TARGET)/app/dpdk-procinfo -- -m | [-p PORTMASK] [--stats | --xstats|
doc/guides/tools/proc_info.rst +2
-0+ ./<build_dir>/app/dpdk-procinfo -- -m | [-p PORTMASK] [--stats | + --xstats | --stats-reset | --xstats-reset] [ --show-port | --show-tm | --show-crypto | --show-ring[=name] | --show-mempool[=name] | --iter-mempool=name ]doc/guides/tools/testbbdev.rst +1
-2@@ -13,25 +13,10 @@ parameters passed to a python running script. Compiling the Application ------------------------- -**Step 1: PMD setting** +**Build the application** -The ``dpdk-test-bbdev`` tool depends on crypto device drivers PMD which -aredisabled by default in the build configuration file ``common_base``.
doc/guides/tools/testbbdev.rst +1
-13-The bbdevice drivers PMD which should be tested can be enabled by setting +See :doc:`../linux_gsg/build_dpdk.rst` for compilation steps. - ``CONFIG_RTE_LIBRTE_PMD_<name>=y`` - -Setting example for (*baseband_turbo_sw*) PMD - - ``CONFIG_RTE_LIBRTE_PMD_BBDEV_TURBO_SW=y`` - -**Step 2: Build the application** - -Execute the ``dpdk-setup.sh`` script to build the DPDK library together with the -``dpdk-test-bbdev`` application. - -Initially, the user must select a DPDK target to choose the correct target type -and compiler options to use when building the libraries.
The user must have all libraries, modules, updates and compilers installed in
the system prior to this, as described in the earlier chapters in this Getting Started Guide.doc/guides/tools/testbbdev.rst +0
-1@@ -60,7 +45,7 @@ The following are the command-line options: ``-p TESTAPP_PATH, --testapp_path TESTAPP_PATH`` Indicates the path to the bbdev test app. If not specified path is set based - on *$RTE_SDK* environment variable concatenated with"*/build/app/testbbdev*".
+ on "../.." concatenated with "*/build/app/testbbdev*".``-e
EAL_PARAMS, --eal_params EAL_PARAMS``
Specifies EAL arguments which are passed to the test app. For more details,doc/guides/tools/testbbdev.rst +0
-0@@ -82,9 +67,8 @@ The following are the command-line options: ``-v TEST_VECTOR [TEST_VECTOR ...], --test_vector TEST_VECTOR[
TEST_VECTOR...]``
Specifies paths to the test vector files. If not specified path is set based
- on *$RTE_SDK* environment variable concatenated with
- "*/app/test-bbdev/test_vectors/bbdev_null.data*" and indicates default
- data file.
+ on "../.." concatenated with "*/app/test- bbdev/test_vectors/bbdev_null.data*"doc/guides/tools/testbbdev.rst +1
-0+and indicates default data file. **Example usage:**@@ -259,8 +243,8 @@ They are chosen to have a good coverage across sizesand processing parameters while still keeping their number limited as part of sanity regression.
-Shortened tree of isg_cid-wireless_dpdk_ae with dpdk compiled for -x86_64- native-linux-icc target:
doc/guides/tools/testbbdev.rst +6
-3+Shortened tree of isg_cid-wireless_dpdk_ae with dpdk compiled and +output to the build directory: ::@@ -268,7 +252,7 @@ x86_64-native-linux-icc target: |-- test-bbdev |-- test_vectors - |-- x86_64-native-linux-icc + |-- build |-- app |-- testbbdev@@ -277,7 +261,7 @@ All bbdev devices .. code-block:: console - ./test-bbdev.py -p ../../x86_64-native-linux-icc/app/testbbdev + ./test-bbdev.py -p ../../build/app/dpdk-test-bbdev -v turbo_dec_default.data It runs all available tests using the test vector filled based on @@ -291,7 +275,7 @@ baseband turbo_sw device .. code-block:: console - ./test-bbdev.py -p ../../x86_64-native-linux-icc/app/testbbdev + ./test-bbdev.py -p ../../build/app/dpdk-test-bbdev -e="--vdev=baseband_turbo_sw" -t 120 -c validation -v ./test_vectors/* -n 64 -b 8 32doc/guides/tools/testeventdev.rst +1
-3@@ -15,11 +15,8 @@ Compiling the Application **Build the application** -Execute the ``dpdk-setup.sh`` script to build the DPDK library together with the -``dpdk-test-eventdev`` application. +See :doc:`../linux_gsg/build_dpdk.rst` for compilation steps. -Initially, the user must select a DPDK target to choose the correct target type -and compiler options to use when building the libraries.
The user must have all libraries, modules, updates and compilers installed in
the system prior to this, as described in the earlier chapters in this Getting Started Guide.doc/guides/tools/testeventdev.rst +4
-3@@ -251,7 +248,7 @@ Example command to run order queue test: .. code-block:: console - sudo build/app/dpdk-test-eventdev --vdev=event_sw0 -- \ + sudo <build_dir>/app/dpdk-test-eventdev --vdev=event_sw0 -- \ --test=order_queue --plcores 1 --wlcores 2,3@@ -314,7 +311,7 @@ Example command to run order ``all types queue`` test: .. code-block:: console - sudo build/app/dpdk-test-eventdev --vdev=event_octeontx -- \ + sudo <build_dir>/app/dpdk-test-eventdev --vdev=event_octeontx -- \ --test=order_atq --plcores 1 --wlcores 2,3@@ -414,7 +411,7 @@ Example command to run perf queue test: .. code-block:: console - sudo build/app/dpdk-test-eventdev -c 0xf -s 0x1 --vdev=event_sw0 -- \ + sudo <build_dir>/app/dpdk-test-eventdev -c 0xf -s 0x1 + --vdev=event_sw0 -- \ --test=perf_queue --plcores=2 --wlcore=3 --stlist=p --nb_pkts=0 Example command to run perf queue test with ethernet ports:@@ -428,7 +425,7 @@ Example command to run perf queue test with eventtimer adapter:
.. code-block:: console
doc/guides/tools/testeventdev.rst +2
-1- sudo build/app/dpdk-test-eventdev --vdev="event_octeontx" -- \ + sudo <build_dir>/app/dpdk-test-eventdev --vdev="event_octeontx" -- + \ --wlcores 4 --plcores 12 --test perf_queue --stlist=a \ --prod_type_timerdev --fwd_latency@@ -514,14 +511,14 @@ Example command to run perf ``all types queue``test:
.. code-block:: console
doc/guides/tools/testeventdev.rst +1
-1- sudo build/app/dpdk-test-eventdev --vdev=event_octeontx -- \ + sudo <build_dir>/app/dpdk-test-eventdev --vdev=event_octeontx -- \ --test=perf_atq --plcores=2 --wlcore=3 --stlist=p --nb_pkts=0 Example command to run perf ``all types queue`` test with event timeradapter:
.. code-block:: console
doc/guides/tools/testeventdev.rst +6
-4- sudo build/app/dpdk-test-eventdev --vdev="event_octeontx" -- \ + sudo <build_dir>/app/dpdk-test-eventdev --vdev="event_octeontx" -- + \ --wlcores 4 --plcores 12 --test perf_atq --verbose 20 \ --stlist=a --prod_type_timerdev --fwd_latency@@ -633,7 +630,7 @@ Example command to run pipeline queue test: .. code-block:: console - sudo build/app/dpdk-test-eventdev -c 0xf -s 0x8 --vdev=event_sw0 -- \ + sudo <build_dir>/app/dpdk-test-eventdev -c 0xf -s 0x8 + --vdev=event_sw0 -- \ --test=pipeline_queue --wlcore=1 --prod_type_ethdev --stlist=a@@ -725,5 +722,5 @@ Example command to run pipeline queue test: .. code-block:: console - sudo build/app/dpdk-test-eventdev -c 0xf -s 0x8 --vdev=event_sw0 -- \ + sudo <build_dir>/app/dpdk-test-eventdev -c 0xf -s 0x8 + --vdev=event_sw0 -- \ --test=pipeline_atq --wlcore=1 --prod_type_ethdev --stlist=a --2.17.1
Re: [dpdk-dev] [PATCH v3 35/37] doc: remove reference to make in tools guides
In reply to Ciara Powerdoc/guides/tools/pdump.rst index
Quoted 11 lines
-----Original Message-----
From: Power, Ciara <[email protected]>doc/guides/tools/pdump.rst index renamed from doc/guides/tools/pdump.rst +3
-0+ * The ``dpdk-pdump`` tool depends on libpcap based PMD which must be + installed on the board. + Once the libpcap development files are installed, recompile the DPDK.
Might be rewrite the sentence as below
The ``dpdk-pdump`` tool depends on DPDK pcap PMD, so the system should have libpcap development files installed
and the pcap PMD enabled in the build.
Thanks,
Reshma
Re: [dpdk-dev] [PATCH v3 35/37] doc: remove reference to make in tools guides
Quoted 13 lines · Reshma
Quoted 10 lines
-----Original Message----- From: Power, Ciara <[email protected]>
doc/guides/tools/pdump.rst +0
-0which must be + installed on the board. + Once the
libpcap development files are installed, recompile the DPDK.Might be rewrite the sentence as below
Quoted 4 lines
The ``dpdk-pdump`` tool depends on DPDK pcap PMD, so the system should have libpcap development files installed and the pcap PMD enabled in the build.
Sounds good, though I'd suggest changing "enabled" to "not disabled" since all drivers are enabled if their dependencies are present, unless they are explicitly disabled.
Re: [dpdk-dev] [PATCH v3 35/37] doc: remove reference to make in tools guides
Quoted 5 lines
-----Original Message-----
From: Bruce Richardson <[email protected]>Quoted 1 line
Quoted 7 lines
Quoted 4 lines
The ``dpdk-pdump`` tool depends on DPDK pcap PMD, so the system should have libpcap development files installed and the pcap PMD enabled in the build.
Sounds good, though I'd suggest changing "enabled" to "not disabled" since all drivers are enabled if their dependencies are present, unless they are explicitly disabled.
Good point.
PATCH v3 36/37 doc: remove references to make in testpmd guides
In reply to Ciara PowerMake is no longer supported for compiling DPDK, references are now removed in the documentation.
---
v3: Added back in ieee1588 description.
--- doc/guides/testpmd_app_ug/run_app.rst | 6 +++--- doc/guides/testpmd_app_ug/testpmd_funcs.rst | 9 ++------- 2 files changed, 5 insertions(+), 10 deletions(-)
doc/guides/testpmd_app_ug/run_app.rst +3 -3
@@ -20,7 +20,7 @@ They must be separated from the EAL options, shown in the previous section, with .. code-block:: console - sudo ./testpmd -l 0-3 -n 4 -- -i --portmask=0x1 --nb-cores=2 + sudo ./dpdk-testpmd -l 0-3 -n 4 -- -i --portmask=0x1 --nb-cores=2 The command line options are:
@@ -59,13 +59,13 @@ The command line options are: * ``--nb-cores=N`` Set the number of forwarding cores, - where 1 <= N <= "number of cores" or ``CONFIG_RTE_MAX_LCORE`` from the configuration file. + where 1 <= N <= "number of cores" or ``RTE_MAX_LCORE`` from the configuration file. The default value is 1. * ``--nb-ports=N`` Set the number of forwarding ports, - where 1 <= N <= "number of ports" on the board or ``CONFIG_RTE_MAX_ETHPORTS`` from the configuration file. + where 1 <= N <= "number of ports" on the board or ``RTE_MAX_ETHPORTS`` from the configuration file. The default value is the number of ports on the board. * ``--coremask=0xXX``
doc/guides/testpmd_app_ug/testpmd_funcs.rst +2 -7
@@ -71,7 +71,7 @@ practical or possible testpmd supports alternative methods for executing command .. code-block:: console - ./testpmd -n4 -r2 ... -- -i --cmdline-file=/home/ubuntu/flow-create-commands.txt + ./dpdk-testpmd -n4 -r2 ... -- -i --cmdline-file=/home/ubuntu/flow-create-commands.txt Interactive-mode selected CLI commands to be read from /home/ubuntu/flow-create-commands.txt Configuring Port 0 (socket 0)
@@ -329,7 +329,7 @@ The available information categories are: * ``icmpecho``: Receives a burst of packets, lookup for ICMP echo requests and, if any, send back ICMP echo replies. -* ``ieee1588``: Demonstrate L2 IEEE1588 V2 PTP timestamping for RX and TX. Requires ``CONFIG_RTE_LIBRTE_IEEE1588=y``. +* ``ieee1588``: Demonstrate L2 IEEE1588 V2 PTP timestamping for RX and TX. * ``noisy``: Noisy neighbor simulation. Simulate more realistic behavior of a guest machine engaged in receiving
@@ -379,11 +379,6 @@ Example for the io forwarding engine, with some packet drops on the tx side:: TX-packets: 548595568 TX-dropped: 128 TX-total: 548595696 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -.. note:: - - Enabling CONFIG_RTE_TEST_PMD_RECORD_CORE_CYCLES appends "CPU cycles/packet" stats, like: - - CPU cycles/packet=xx.dd (total cycles=xxxx / total RX packets=xxxx) at xxx MHz clock clear fwd ~~~~~~~~~
Signature · 1 line
2.17.1
PATCH v3 37/37 doc: update quick build doc to remove make references
In reply to Ciara PowerMake is no longer supported for compiling DPDK, references are now removed in the documentation.
--- doc/build-sdk-quick.txt | 55 ++++++++++++++++------------------------- 1 file changed, 21 insertions(+), 34 deletions(-)
doc/build-sdk-quick.txt +21 -34
@@ -1,34 +1,21 @@ -Basic build - make defconfig && make - or - make config T=x86_64-native-linux-gcc && make -Build commands - config get configuration from target template (T=) - defconfig auto-select target template based on arch, OS, etc. - all same as build (default rule) - build build in a configured directory - clean remove files but keep configuration - install T= configure, build and install a target in DESTDIR - install install optionally staged in DESTDIR - examples build examples for given targets (T=) - examples_clean clean examples for given targets (T=) - test compile tests and run basic unit tests - test-* run specific subset of unit tests - tags|etags|gtags generate tags database for given targets (T=) - cscope generate cscope database for given targets (T=) -Build variables - EXTRA_CPPFLAGS preprocessor options - EXTRA_CFLAGS compiler options - EXTRA_LDFLAGS linker options - EXTRA_LDLIBS linker library options - RTE_KERNELDIR linux headers path - RTE_DEVEL_BUILD stricter options (default: y in git tree) - CROSS toolchain prefix - V verbose - D debug dependencies - O build directory (default: build/ - install T= default: ./) - DESTDIR staging install directory (default: empty) - prefix root install directory (default: /usr/local) - T target template - used with config or install - format: <arch-machine-execenv-toolchain> - templates in config/defconfig_* +For many platforms, compiling and installing DPDK should work using the +following set of commands:: + + meson build + cd build + ninja + ninja install + +This will compile DPDK in the ``build`` subdirectory, and then install the +resulting libraries, drivers and header files onto the system - generally +in /usr/local. A package-config file, ``libdpdk.pc``, for DPDK will also +be installed to allow ease of compiling and linking with applications. + +After installation, to use DPDK, the necessary CFLAG and LDFLAG variables +can be got from pkg-config:: + + pkg-config --cflags libdpdk + pkg-config --libs libdpdk + +More detail on each of these steps can be got from the +"Installing DPDK Using the meson build system" section of the programming guides.
Signature · 1 line
2.17.1
Re: [dpdk-dev] [PATCH v3 37/37] doc: update quick build doc to remove make references
Quoted 8 lines · Ciara Power
Make is no longer supported for compiling DPDK, references are now removed in the documentation.
Signed-off-by Ciara Power <[email protected]>Reviewed-by Kevin Laatz <[email protected]>---
doc/build-sdk-quick.txt| 55 ++++++++++++++++-------------------------1 file changed, 21 insertions(+), 34 deletions(-)
This file was printed in "make help".
Instead of copy pasting the intro of build-sdk-meson.rst, I think it would be better to just remove this file, avoiding duplicates.
Quoted 11 lines · Ciara Power
v3: Fixed comments on v2.
v2:
- Fixed comments on v1.
- Removed additional make references.
- Added some meson replacements where necessary.
- Added dummy rootMakefile.As previously decided [1] and communicated via deprecation notice [2], the
make build system is to be removed in the 20.11 release.
Quoted 7 lines
This patchset removes support for compiling DPDK with the legacy make build system. Some make support is maintained for example applications, where pkg-config is used rather than the legacy make method.
References to the make build system are removed from all documentation, please review to see if replacement meson instructions are needed in some cases.
I think it deserves a bit more reviews in some scripts, apps and docs. I am going to squash and merge some patches while keeping some parts untouched so we can discuss how to follow-up on those details.
Please wait for the merge of the main parts, but keep replying, thanks.
v4 cover remove make support in DPDK
In reply to Ciara PowerThe first 13 commits of this series are pushed to the main branch, making the make-based build an old story.
The last 18 commits (devtools, app and doc) are pending for more reviews, especially because the doc rework is still in progress. This is a big change which requires to be split but must be completed soon.
*All*, please make the documentation update your highest priority. I will be reluctant to merge some driver changes if the related doc is not updated.
v4: rearrange commits and fix as commented
v3: Fixed comments on v2.
v2:
- Fixed comments on v1.
- Removed additional make references.
- Added some meson replacements where necessary.
- Added dummy root Makefile.
As previously decided [1] and communicated via deprecation notice [2], the make build system is to be removed in the 20.11 release.
This patchset removes support for compiling DPDK with the legacy make build system. Some make support is maintained for example applications, where pkg-config is used rather than the legacy make method.
References to the make build system are removed from all documentation, please review to see if replacement meson instructions are needed in some cases.
[1] https://mails.dpdk.org/archives/dev/2020-April/162839.html
[2] http://git.dpdk.org/dpdk/commit/?id=a5449d78d1413e7bd1d66f6e70884e46cfb5e673
Bruce Richardson (5):
doc: build without using make examples/multi_process: convert to pkg-config-based build examples/vm_power: convert to pkg-config-based build examples/ethtool: convert to pkg-config-based build
build: create dummy Makefile
Ciara Power (23):
examples: remove legacy sections of makefiles
examples: remove old build system references
build: remove makefiles
buildtools: remove scripts used only with make
config: remove default configs used with make
devtools: remove legacy flags from includes check
app: remove references to make-based config
doc: remove references to make from Linux guide
doc: remove references to make from FreeBSD guide
doc: remove references to make from howto guides
doc: remove references to make from prog guide
doc: remove references to make from platforms guides
doc: remove references to make from mempool guide
doc: remove references to make from NICs guides
doc: remove references to make from vdpadevs guides
doc: remove references to make from bbdevs guides
doc: remove references to make from cryptodevs guides
doc: remove references to make from compressdevs guides
doc: remove references to make from eventdevs guides
doc: remove references to make from rawdevs guides
doc: remove references to make from app guides
doc: remove reference to make from tools guides
doc: remove references to make from contributing guide
Kevin Laatz (3):
examples/ka-agent: convert to pkg-config-based build examples/server_node_efd: convert to pkg-config-based build examples/performance-thread: convert to pkg-config-based build
GNUmakefile | 17 - MAINTAINERS | 25 +- Makefile | 7 +- app/Makefile | 34 - app/pdump/Makefile | 18 - app/proc-info/Makefile | 14 - app/test-acl/Makefile | 17 - app/test-bbdev/Makefile | 30 - app/test-bbdev/test-bbdev.py | 11 +- app/test-cmdline/Makefile | 24 - app/test-compress-perf/Makefile | 19 - app/test-crypto-perf/Makefile | 28 - app/test-eventdev/Makefile | 32 - app/test-fib/Makefile | 18 - app/test-flow-perf/Makefile | 26 - app/test-pipeline/Makefile | 33 - app/test-pmd/Makefile | 73 -- app/test-regex/Makefile | 13 - app/test-sad/Makefile | 17 - app/test/Makefile | 310 ----- app/test/test_cryptodev.c | 89 +- app/test/test_cryptodev_asym.c | 18 +- buildtools/Makefile | 9 - buildtools/auto-config-h.sh | 108 -- buildtools/call-sphinx-build.py | 5 +- buildtools/gen-build-mk.sh | 23 - buildtools/gen-config-h.sh | 15 - buildtools/pmdinfogen/Makefile | 20 - buildtools/relpath.sh | 76 -- config/common_armv8a_linux | 43 - config/common_base | 1154 ----------------- config/common_freebsd | 15 - config/common_linux | 68 - config/defconfig_arm-armv7a-linux-gcc | 1 - config/defconfig_arm-armv7a-linuxapp-gcc | 49 - config/defconfig_arm64-armada-linux-gcc | 1 - config/defconfig_arm64-armada-linuxapp-gcc | 41 - config/defconfig_arm64-armv8a-linux-clang | 1 - config/defconfig_arm64-armv8a-linux-gcc | 1 - config/defconfig_arm64-armv8a-linuxapp-clang | 8 - config/defconfig_arm64-armv8a-linuxapp-gcc | 9 - config/defconfig_arm64-bluefield-linux-gcc | 1 - config/defconfig_arm64-bluefield-linuxapp-gcc | 18 - config/defconfig_arm64-dpaa-linux-gcc | 1 - config/defconfig_arm64-dpaa-linuxapp-gcc | 31 - config/defconfig_arm64-emag-linux-gcc | 1 - config/defconfig_arm64-emag-linuxapp-gcc | 11 - config/defconfig_arm64-n1sdp-linux-gcc | 1 - config/defconfig_arm64-n1sdp-linuxapp-gcc | 14 - config/defconfig_arm64-octeontx2-linux-gcc | 1 - config/defconfig_arm64-octeontx2-linuxapp-gcc | 18 - config/defconfig_arm64-stingray-linux-gcc | 1 - config/defconfig_arm64-stingray-linuxapp-gcc | 14 - config/defconfig_arm64-thunderx-linux-gcc | 1 - config/defconfig_arm64-thunderx-linuxapp-gcc | 17 - config/defconfig_arm64-thunderx2-linux-gcc | 1 - config/defconfig_arm64-thunderx2-linuxapp-gcc | 12 - config/defconfig_arm64-xgene1-linux-gcc | 1 - config/defconfig_arm64-xgene1-linuxapp-gcc | 8 - config/defconfig_i686-native-linux-gcc | 1 - config/defconfig_i686-native-linux-icc | 1 - config/defconfig_i686-native-linuxapp-gcc | 66 - config/defconfig_i686-native-linuxapp-icc | 66 - config/defconfig_ppc_64-power8-linux-gcc | 1 - config/defconfig_ppc_64-power8-linuxapp-gcc | 35 - config/defconfig_x86_64-native-bsdapp-clang | 14 - config/defconfig_x86_64-native-bsdapp-gcc | 14 - config/defconfig_x86_64-native-freebsd-clang | 1 - config/defconfig_x86_64-native-freebsd-gcc | 1 - config/defconfig_x86_64-native-linux-clang | 1 - config/defconfig_x86_64-native-linux-gcc | 1 - config/defconfig_x86_64-native-linux-icc | 1 - config/defconfig_x86_64-native-linuxapp-clang | 14 - config/defconfig_x86_64-native-linuxapp-gcc | 14 - config/defconfig_x86_64-native-linuxapp-icc | 29 - config/defconfig_x86_x32-native-linux-gcc | 1 - config/defconfig_x86_x32-native-linuxapp-gcc | 46 - config/rte_config.h | 4 - devtools/build-tags.sh | 15 +- devtools/check-includes.sh | 11 +- devtools/git-log-fixes.sh | 2 +- devtools/test-build.sh | 315 ----- doc/build-sdk-quick.txt | 34 - doc/guides/bbdevs/fpga_5gnr_fec.rst | 7 +- doc/guides/bbdevs/fpga_lte_fec.rst | 7 +- doc/guides/bbdevs/turbo_sw.rst | 15 - doc/guides/compressdevs/isal.rst | 4 - doc/guides/compressdevs/octeontx.rst | 24 +- doc/guides/compressdevs/zlib.rst | 4 - doc/guides/conf.py | 7 +- doc/guides/contributing/coding_style.rst | 48 +- doc/guides/contributing/design.rst | 127 +- doc/guides/contributing/documentation.rst | 31 +- doc/guides/contributing/patches.rst | 49 - doc/guides/cryptodevs/aesni_gcm.rst | 4 +- doc/guides/cryptodevs/aesni_mb.rst | 4 +- doc/guides/cryptodevs/armv8.rst | 3 - doc/guides/cryptodevs/caam_jr.rst | 30 - doc/guides/cryptodevs/ccp.rst | 14 +- doc/guides/cryptodevs/dpaa2_sec.rst | 25 - doc/guides/cryptodevs/dpaa_sec.rst | 25 - doc/guides/cryptodevs/kasumi.rst | 11 +- doc/guides/cryptodevs/mvsam.rst | 10 +- doc/guides/cryptodevs/nitrox.rst | 7 - doc/guides/cryptodevs/null.rst | 2 +- doc/guides/cryptodevs/octeontx.rst | 12 +- doc/guides/cryptodevs/octeontx2.rst | 8 +- doc/guides/cryptodevs/openssl.rst | 6 +- doc/guides/cryptodevs/qat.rst | 67 +- doc/guides/cryptodevs/scheduler.rst | 8 - doc/guides/cryptodevs/snow3g.rst | 10 +- doc/guides/cryptodevs/virtio.rst | 18 +- doc/guides/cryptodevs/zuc.rst | 10 +- doc/guides/eventdevs/dpaa.rst | 20 - doc/guides/eventdevs/dpaa2.rst | 20 - doc/guides/eventdevs/octeontx.rst | 24 - doc/guides/eventdevs/octeontx2.rst | 8 - doc/guides/freebsd_gsg/build_dpdk.rst | 2 +- doc/guides/freebsd_gsg/intro.rst | 4 +- doc/guides/howto/lm_bond_virtio_sriov.rst | 4 +- doc/guides/howto/lm_virtio_vhost_user.rst | 4 +- doc/guides/howto/packet_capture_framework.rst | 21 +- doc/guides/howto/pvp_reference_benchmark.rst | 27 +- doc/guides/howto/vfd.rst | 4 +- .../virtio_user_for_container_networking.rst | 2 +- doc/guides/linux_gsg/build_dpdk.rst | 84 +- doc/guides/linux_gsg/build_sample_apps.rst | 69 +- .../linux_gsg/cross_build_dpdk_for_arm64.rst | 48 +- doc/guides/linux_gsg/enable_func.rst | 13 +- doc/guides/linux_gsg/intro.rst | 2 +- doc/guides/linux_gsg/linux_drivers.rst | 18 +- doc/guides/linux_gsg/sys_reqs.rst | 16 +- doc/guides/mempool/octeontx.rst | 28 +- doc/guides/mempool/octeontx2.rst | 10 +- doc/guides/meson.build | 3 +- doc/guides/nics/ark.rst | 26 - doc/guides/nics/atlantic.rst | 4 - doc/guides/nics/axgbe.rst | 15 - doc/guides/nics/bnx2x.rst | 27 - doc/guides/nics/bnxt.rst | 5 +- doc/guides/nics/build_and_test.rst | 8 +- doc/guides/nics/cxgbe.rst | 36 +- doc/guides/nics/dpaa.rst | 27 +- doc/guides/nics/dpaa2.rst | 26 +- doc/guides/nics/ena.rst | 16 - doc/guides/nics/enetc.rst | 2 - doc/guides/nics/enic.rst | 9 - doc/guides/nics/fail_safe.rst | 20 +- doc/guides/nics/features.rst | 9 - doc/guides/nics/fm10k.rst | 4 - doc/guides/nics/hinic.rst | 9 - doc/guides/nics/hns3.rst | 10 - doc/guides/nics/i40e.rst | 44 +- doc/guides/nics/ice.rst | 25 +- doc/guides/nics/igc.rst | 18 +- doc/guides/nics/intel_vf.rst | 13 +- doc/guides/nics/ionic.rst | 8 - doc/guides/nics/ipn3ke.rst | 12 +- doc/guides/nics/kni.rst | 4 +- doc/guides/nics/liquidio.rst | 27 - doc/guides/nics/memif.rst | 10 +- doc/guides/nics/mlx4.rst | 55 +- doc/guides/nics/mlx5.rst | 62 +- doc/guides/nics/mvneta.rst | 36 +- doc/guides/nics/mvpp2.rst | 43 +- doc/guides/nics/nfb.rst | 19 +- doc/guides/nics/nfp.rst | 4 - doc/guides/nics/null.rst | 6 +- doc/guides/nics/octeontx.rst | 19 +- doc/guides/nics/octeontx2.rst | 13 +- doc/guides/nics/pcap_ring.rst | 24 +- doc/guides/nics/qede.rst | 17 +- doc/guides/nics/sfc_efx.rst | 15 - doc/guides/nics/softnic.rst | 13 +- doc/guides/nics/szedata2.rst | 18 +- doc/guides/nics/thunderx.rst | 25 +- doc/guides/nics/vdev_netvsc.rst | 6 - doc/guides/nics/vhost.rst | 2 +- doc/guides/nics/virtio.rst | 4 +- doc/guides/platform/bluefield.rst | 22 - doc/guides/platform/octeontx.rst | 33 +- doc/guides/platform/octeontx2.rst | 32 - doc/guides/prog_guide/build_app.rst | 56 +- .../prog_guide/dev_kit_build_system.rst | 331 ----- .../prog_guide/dev_kit_root_make_help.rst | 188 --- .../prog_guide/env_abstraction_layer.rst | 17 +- .../prog_guide/ext_app_lib_make_help.rst | 98 -- doc/guides/prog_guide/graph_lib.rst | 6 +- doc/guides/prog_guide/index.rst | 3 - doc/guides/prog_guide/intro.rst | 2 +- .../prog_guide/ip_fragment_reassembly_lib.rst | 5 - .../prog_guide/kernel_nic_interface.rst | 14 +- .../link_bonding_poll_mode_drv_lib.rst | 15 +- doc/guides/prog_guide/lto.rst | 12 +- doc/guides/prog_guide/mbuf_lib.rst | 4 +- doc/guides/prog_guide/mempool_lib.rst | 7 +- doc/guides/prog_guide/overview.rst | 12 +- doc/guides/prog_guide/profile_app.rst | 17 +- doc/guides/prog_guide/qos_framework.rst | 10 +- doc/guides/prog_guide/rcu_lib.rst | 7 +- doc/guides/prog_guide/source_org.rst | 23 +- doc/guides/prog_guide/trace_lib.rst | 3 +- .../prog_guide/writing_efficient_code.rst | 3 +- doc/guides/rawdevs/dpaa2_cmdif.rst | 21 - doc/guides/rawdevs/dpaa2_qdma.rst | 21 - doc/guides/rawdevs/ifpga.rst | 10 - doc/guides/rawdevs/ioat.rst | 8 +- doc/guides/rawdevs/ntb.rst | 6 - doc/guides/rawdevs/octeontx2_dma.rst | 12 - doc/guides/rawdevs/octeontx2_ep.rst | 8 - doc/guides/rel_notes/deprecation.rst | 7 - doc/guides/sample_app_ug/bbdev_app.rst | 34 +- doc/guides/sample_app_ug/cmd_line.rst | 2 +- doc/guides/sample_app_ug/compiling.rst | 89 +- doc/guides/sample_app_ug/dist_app.rst | 4 +- doc/guides/sample_app_ug/ethtool.rst | 2 +- .../sample_app_ug/eventdev_pipeline.rst | 3 +- doc/guides/sample_app_ug/fips_validation.rst | 10 +- doc/guides/sample_app_ug/flow_classify.rst | 4 +- doc/guides/sample_app_ug/flow_filtering.rst | 25 +- doc/guides/sample_app_ug/hello_world.rst | 2 +- doc/guides/sample_app_ug/ioat.rst | 6 +- doc/guides/sample_app_ug/ip_frag.rst | 6 +- doc/guides/sample_app_ug/ip_pipeline.rst | 4 +- doc/guides/sample_app_ug/ip_reassembly.rst | 9 +- doc/guides/sample_app_ug/ipsec_secgw.rst | 14 +- doc/guides/sample_app_ug/ipv4_multicast.rst | 4 +- doc/guides/sample_app_ug/keep_alive.rst | 4 +- .../sample_app_ug/kernel_nic_interface.rst | 14 +- doc/guides/sample_app_ug/l2_forward_cat.rst | 4 +- .../sample_app_ug/l2_forward_crypto.rst | 4 +- doc/guides/sample_app_ug/l2_forward_event.rst | 10 +- .../sample_app_ug/l2_forward_job_stats.rst | 4 +- .../sample_app_ug/l2_forward_real_virtual.rst | 6 +- doc/guides/sample_app_ug/l3_forward.rst | 10 +- .../sample_app_ug/l3_forward_access_ctrl.rst | 6 +- doc/guides/sample_app_ug/l3_forward_graph.rst | 4 +- .../sample_app_ug/l3_forward_power_man.rst | 14 +- doc/guides/sample_app_ug/link_status_intr.rst | 4 +- doc/guides/sample_app_ug/multi_process.rst | 20 +- doc/guides/sample_app_ug/ntb.rst | 2 +- doc/guides/sample_app_ug/packet_ordering.rst | 3 +- .../sample_app_ug/performance_thread.rst | 44 +- doc/guides/sample_app_ug/ptpclient.rst | 9 +- doc/guides/sample_app_ug/qos_metering.rst | 2 +- doc/guides/sample_app_ug/qos_scheduler.rst | 10 +- doc/guides/sample_app_ug/rxtx_callbacks.rst | 9 +- doc/guides/sample_app_ug/server_node_efd.rst | 2 +- doc/guides/sample_app_ug/service_cores.rst | 23 +- doc/guides/sample_app_ug/skeleton.rst | 2 +- doc/guides/sample_app_ug/tep_termination.rst | 43 +- doc/guides/sample_app_ug/test_pipeline.rst | 4 +- doc/guides/sample_app_ug/timer.rst | 2 +- doc/guides/sample_app_ug/vdpa.rst | 4 +- doc/guides/sample_app_ug/vhost.rst | 11 +- doc/guides/sample_app_ug/vhost_blk.rst | 2 +- doc/guides/sample_app_ug/vhost_crypto.rst | 2 +- .../sample_app_ug/vm_power_management.rst | 34 +- .../sample_app_ug/vmdq_dcb_forwarding.rst | 8 +- doc/guides/sample_app_ug/vmdq_forwarding.rst | 8 +- doc/guides/testpmd_app_ug/run_app.rst | 6 +- doc/guides/testpmd_app_ug/testpmd_funcs.rst | 9 +- doc/guides/tools/comp_perf.rst | 10 +- doc/guides/tools/cryptoperf.rst | 20 +- doc/guides/tools/pdump.rst | 15 +- doc/guides/tools/proc_info.rst | 2 +- doc/guides/tools/testbbdev.rst | 36 +- doc/guides/tools/testeventdev.rst | 21 +- doc/guides/vdpadevs/ifc.rst | 13 - doc/guides/vdpadevs/mlx5.rst | 40 +- drivers/Makefile | 34 - drivers/baseband/Makefile | 18 - drivers/baseband/fpga_5gnr_fec/Makefile | 28 - drivers/baseband/fpga_lte_fec/Makefile | 25 - drivers/baseband/null/Makefile | 21 - drivers/baseband/turbo_sw/Makefile | 52 - drivers/bus/Makefile | 15 - drivers/bus/dpaa/Makefile | 48 - drivers/bus/fslmc/Makefile | 47 - drivers/bus/ifpga/Makefile | 28 - drivers/bus/pci/Makefile | 33 - drivers/bus/pci/bsd/Makefile | 4 - drivers/bus/pci/linux/Makefile | 6 - drivers/bus/pci/linux/pci_vfio.c | 1 - drivers/bus/vdev/Makefile | 27 - drivers/bus/vmbus/Makefile | 33 - drivers/bus/vmbus/linux/Makefile | 3 - drivers/common/Makefile | 39 - drivers/common/cpt/Makefile | 24 - drivers/common/dpaax/Makefile | 30 - drivers/common/iavf/Makefile | 27 - drivers/common/mlx5/Makefile | 404 ------ drivers/common/mvep/Makefile | 35 - drivers/common/octeontx/Makefile | 22 - drivers/common/octeontx2/Makefile | 39 - drivers/common/qat/Makefile | 74 -- drivers/compress/Makefile | 10 - drivers/compress/isal/Makefile | 27 - drivers/compress/octeontx/Makefile | 26 - drivers/compress/zlib/Makefile | 25 - drivers/crypto/Makefile | 31 - drivers/crypto/aesni_gcm/Makefile | 43 - drivers/crypto/aesni_mb/Makefile | 42 - drivers/crypto/armv8/Makefile | 36 - drivers/crypto/caam_jr/Makefile | 39 - drivers/crypto/ccp/Makefile | 32 - drivers/crypto/dpaa2_sec/Makefile | 45 - drivers/crypto/dpaa_sec/Makefile | 38 - drivers/crypto/kasumi/Makefile | 42 - drivers/crypto/mvsam/Makefile | 40 - drivers/crypto/nitrox/Makefile | 30 - drivers/crypto/null/Makefile | 27 - drivers/crypto/octeontx/Makefile | 36 - drivers/crypto/octeontx2/Makefile | 49 - drivers/crypto/openssl/Makefile | 26 - drivers/crypto/scheduler/Makefile | 34 - drivers/crypto/snow3g/Makefile | 43 - drivers/crypto/virtio/Makefile | 33 - drivers/crypto/zuc/Makefile | 42 - drivers/event/Makefile | 20 - drivers/event/dpaa/Makefile | 39 - drivers/event/dpaa2/Makefile | 41 - drivers/event/dsw/Makefile | 26 - drivers/event/octeontx/Makefile | 51 - drivers/event/octeontx2/Makefile | 47 - drivers/event/opdl/Makefile | 29 - drivers/event/skeleton/Makefile | 24 - drivers/event/sw/Makefile | 29 - drivers/mempool/Makefile | 18 - drivers/mempool/bucket/Makefile | 25 - drivers/mempool/dpaa/Makefile | 30 - drivers/mempool/dpaa2/Makefile | 31 - drivers/mempool/octeontx/Makefile | 39 - drivers/mempool/octeontx2/Makefile | 40 - drivers/mempool/ring/Makefile | 19 - drivers/mempool/stack/Makefile | 22 - drivers/net/Makefile | 84 -- drivers/net/af_packet/Makefile | 27 - drivers/net/af_xdp/Makefile | 26 - drivers/net/ark/Makefile | 39 - drivers/net/atlantic/Makefile | 34 - drivers/net/avp/Makefile | 29 - drivers/net/axgbe/Makefile | 33 - drivers/net/bnx2x/Makefile | 33 - drivers/net/bnxt/Makefile | 63 - drivers/net/bnxt/hcapi/Makefile | 5 - drivers/net/bnxt/tf_core/Makefile | 31 - drivers/net/bnxt/tf_ulp/Makefile | 20 - drivers/net/bonding/Makefile | 36 - drivers/net/cxgbe/Makefile | 57 - drivers/net/dpaa/Makefile | 41 - drivers/net/dpaa2/Makefile | 47 - drivers/net/e1000/Makefile | 79 -- drivers/net/ena/Makefile | 30 - drivers/net/enetc/Makefile | 23 - drivers/net/enic/Makefile | 68 - drivers/net/failsafe/Makefile | 43 - drivers/net/fm10k/Makefile | 77 -- drivers/net/hinic/Makefile | 67 - drivers/net/hns3/Makefile | 42 - drivers/net/i40e/Makefile | 112 -- drivers/net/i40e/i40e_rxtx.c | 1 - drivers/net/iavf/Makefile | 54 - drivers/net/ice/Makefile | 96 -- drivers/net/igc/Makefile | 40 - drivers/net/ionic/Makefile | 31 - drivers/net/ipn3ke/Makefile | 38 - drivers/net/ixgbe/Makefile | 110 -- drivers/net/kni/Makefile | 30 - drivers/net/liquidio/Makefile | 30 - drivers/net/memif/Makefile | 26 - drivers/net/mlx4/Makefile | 142 -- drivers/net/mlx5/Makefile | 82 -- drivers/net/mvneta/Makefile | 39 - drivers/net/mvpp2/Makefile | 42 - drivers/net/netvsc/Makefile | 21 - drivers/net/nfb/Makefile | 40 - drivers/net/nfp/Makefile | 41 - drivers/net/null/Makefile | 24 - drivers/net/octeontx/Makefile | 53 - drivers/net/octeontx2/Makefile | 63 - drivers/net/pcap/Makefile | 32 - drivers/net/pfe/Makefile | 31 - drivers/net/qede/Makefile | 109 -- drivers/net/ring/Makefile | 29 - drivers/net/sfc/Makefile | 133 -- drivers/net/softnic/Makefile | 54 - drivers/net/szedata2/Makefile | 30 - drivers/net/tap/Makefile | 97 -- drivers/net/thunderx/Makefile | 41 - drivers/net/vdev_netvsc/Makefile | 30 - drivers/net/vhost/Makefile | 31 - drivers/net/virtio/Makefile | 82 -- drivers/net/vmxnet3/Makefile | 53 - drivers/raw/Makefile | 18 - drivers/raw/dpaa2_cmdif/Makefile | 35 - drivers/raw/dpaa2_qdma/Makefile | 36 - drivers/raw/ifpga/Makefile | 39 - drivers/raw/ifpga/base/Makefile | 32 - drivers/raw/ioat/Makefile | 28 - drivers/raw/ntb/Makefile | 28 - drivers/raw/octeontx2_dma/Makefile | 34 - drivers/raw/octeontx2_ep/Makefile | 42 - drivers/raw/skeleton/Makefile | 26 - drivers/regex/Makefile | 8 - drivers/regex/mlx5/Makefile | 41 - drivers/vdpa/Makefile | 12 - drivers/vdpa/ifc/Makefile | 33 - drivers/vdpa/mlx5/Makefile | 58 - examples/Makefile | 90 -- examples/bbdev_app/Makefile | 23 +- examples/bond/Makefile | 34 +- examples/bpf/t2.c | 6 +- examples/bpf/t3.c | 10 +- examples/cmdline/Makefile | 29 +- examples/distributor/Makefile | 30 +- examples/ethtool/Makefile | 26 +- examples/ethtool/ethtool-app/Makefile | 56 +- examples/ethtool/lib/Makefile | 62 +- examples/eventdev_pipeline/Makefile | 23 +- examples/fips_validation/Makefile | 34 +- examples/flow_classify/Makefile | 29 +- examples/flow_filtering/Makefile | 23 +- examples/helloworld/Makefile | 23 +- examples/ioat/Makefile | 22 +- examples/ip_fragmentation/Makefile | 29 +- examples/ip_pipeline/Makefile | 36 +- examples/ip_reassembly/Makefile | 29 +- examples/ipsec-secgw/Makefile | 36 +- examples/ipsec-secgw/test/common_defs.sh | 4 +- examples/ipv4_multicast/Makefile | 29 +- examples/kni/Makefile | 27 +- examples/l2fwd-cat/Makefile | 38 +- examples/l2fwd-crypto/Makefile | 28 +- examples/l2fwd-event/Makefile | 22 +- examples/l2fwd-jobstats/Makefile | 23 +- examples/l2fwd-keepalive/Makefile | 23 +- examples/l2fwd-keepalive/ka-agent/Makefile | 51 +- examples/l2fwd/Makefile | 23 +- examples/l3fwd-acl/Makefile | 28 +- examples/l3fwd-graph/Makefile | 23 +- examples/l3fwd-power/Makefile | 36 +- examples/l3fwd/Makefile | 23 +- examples/link_status_interrupt/Makefile | 22 +- examples/multi_process/Makefile | 21 +- .../multi_process/client_server_mp/Makefile | 19 +- .../client_server_mp/mp_client/Makefile | 44 +- .../client_server_mp/mp_server/Makefile | 53 +- examples/multi_process/hotplug_mp/Makefile | 46 +- examples/multi_process/simple_mp/Makefile | 44 +- examples/multi_process/symmetric_mp/Makefile | 44 +- examples/ntb/Makefile | 32 +- examples/packet_ordering/Makefile | 22 +- examples/performance-thread/Makefile | 21 +- examples/performance-thread/common/common.mk | 6 +- .../performance-thread/l3fwd-thread/Makefile | 47 +- .../performance-thread/pthread_shim/Makefile | 56 +- examples/ptpclient/Makefile | 28 +- examples/qos_meter/Makefile | 28 +- examples/qos_sched/Makefile | 31 +- examples/rxtx_callbacks/Makefile | 31 +- examples/server_node_efd/Makefile | 18 +- examples/server_node_efd/node/Makefile | 46 +- examples/server_node_efd/server/Makefile | 53 +- examples/service_cores/Makefile | 28 +- examples/skeleton/Makefile | 29 +- examples/tep_termination/Makefile | 27 +- examples/timer/Makefile | 28 +- examples/vdpa/Makefile | 32 +- examples/vhost/Makefile | 30 +- examples/vhost_blk/Makefile | 31 +- examples/vhost_crypto/Makefile | 31 +- examples/vm_power_manager/Makefile | 76 +- examples/vm_power_manager/guest_cli/Makefile | 50 +- examples/vmdq/Makefile | 23 +- examples/vmdq_dcb/Makefile | 31 +- kernel/Makefile | 9 - kernel/freebsd/Makefile | 9 - kernel/freebsd/contigmem/Makefile | 24 - kernel/freebsd/nic_uio/Makefile | 24 - kernel/linux/Makefile | 9 - kernel/linux/igb_uio/Makefile | 25 - kernel/linux/kni/Makefile | 34 - lib/Makefile | 138 -- lib/librte_acl/Makefile | 65 - lib/librte_bbdev/Makefile | 25 - lib/librte_bitratestats/Makefile | 20 - lib/librte_bpf/Makefile | 40 - lib/librte_cfgfile/Makefile | 26 - lib/librte_cmdline/Makefile | 34 - lib/librte_compressdev/Makefile | 27 - lib/librte_cryptodev/Makefile | 30 - lib/librte_distributor/Makefile | 28 - lib/librte_eal/Makefile | 12 - lib/librte_eal/freebsd/Makefile | 104 -- lib/librte_eal/include/Makefile | 19 - lib/librte_eal/linux/Makefile | 112 -- lib/librte_efd/Makefile | 21 - lib/librte_ethdev/Makefile | 46 - lib/librte_eventdev/Makefile | 47 - lib/librte_fib/Makefile | 22 - lib/librte_flow_classify/Makefile | 23 - lib/librte_graph/Makefile | 28 - lib/librte_gro/Makefile | 23 - lib/librte_gso/Makefile | 25 - lib/librte_hash/Makefile | 31 - lib/librte_ip_frag/Makefile | 27 - lib/librte_ipsec/Makefile | 29 - lib/librte_jobstats/Makefile | 21 - lib/librte_kni/Makefile | 20 - lib/librte_kvargs/Makefile | 21 - lib/librte_latencystats/Makefile | 22 - lib/librte_lpm/Makefile | 29 - lib/librte_mbuf/Makefile | 26 - lib/librte_member/Makefile | 22 - lib/librte_mempool/Makefile | 24 - lib/librte_mempool/rte_mempool.h | 2 +- lib/librte_meter/Makefile | 27 - lib/librte_metrics/Makefile | 30 - lib/librte_net/Makefile | 25 - lib/librte_node/Makefile | 33 - lib/librte_pci/Makefile | 19 - lib/librte_pdump/Makefile | 20 - lib/librte_pipeline/Makefile | 28 - lib/librte_port/Makefile | 59 - lib/librte_power/Makefile | 24 - lib/librte_rawdev/Makefile | 24 - lib/librte_rcu/Makefile | 20 - lib/librte_regexdev/Makefile | 32 - lib/librte_reorder/Makefile | 21 - lib/librte_rib/Makefile | 22 - lib/librte_ring/Makefile | 30 - lib/librte_ring/rte_ring_elem.h | 3 +- lib/librte_sched/Makefile | 29 - lib/librte_security/Makefile | 24 - lib/librte_stack/Makefile | 27 - lib/librte_table/Makefile | 59 - lib/librte_telemetry/Makefile | 30 - lib/librte_timer/Makefile | 20 - lib/librte_vhost/Makefile | 54 - mk/arch/arm/rte.vars.mk | 16 - mk/arch/arm64/rte.vars.mk | 37 - mk/arch/i686/rte.vars.mk | 36 - mk/arch/ppc_64/rte.vars.mk | 17 - mk/arch/x86_64/rte.vars.mk | 36 - mk/arch/x86_x32/rte.vars.mk | 40 - mk/exec-env/bsdapp | 1 - mk/exec-env/freebsd/rte.app.mk | 8 - mk/exec-env/freebsd/rte.vars.mk | 36 - mk/exec-env/linux/rte.app.mk | 8 - mk/exec-env/linux/rte.vars.mk | 44 - mk/exec-env/linuxapp | 1 - mk/internal/rte.build-post.mk | 34 - mk/internal/rte.build-pre.mk | 7 - mk/internal/rte.clean-post.mk | 34 - mk/internal/rte.clean-pre.mk | 4 - mk/internal/rte.compile-post.mk | 5 - mk/internal/rte.compile-pre.mk | 164 --- mk/internal/rte.extvars.mk | 55 - mk/internal/rte.install-post.mk | 71 - mk/internal/rte.install-pre.mk | 32 - mk/machine/armv7a/rte.vars.mk | 36 - mk/machine/armv8a/rte.vars.mk | 31 - mk/machine/default/rte.vars.mk | 30 - mk/machine/dpaa/rte.vars.mk | 37 - mk/machine/emag/rte.vars.mk | 32 - mk/machine/hsw/rte.vars.mk | 30 - mk/machine/ivb/rte.vars.mk | 30 - mk/machine/n1sdp/rte.vars.mk | 34 - mk/machine/native/rte.vars.mk | 39 - mk/machine/nhm/rte.vars.mk | 30 - mk/machine/octeontx2/rte.vars.mk | 34 - mk/machine/power8/rte.vars.mk | 30 - mk/machine/silvermont/rte.vars.mk | 30 - mk/machine/snb/rte.vars.mk | 30 - mk/machine/thunderx/rte.vars.mk | 31 - mk/machine/thunderx2/rte.vars.mk | 34 - mk/machine/wsm/rte.vars.mk | 30 - mk/machine/xgene1/rte.vars.mk | 31 - mk/rte.app.mk | 509 -------- mk/rte.bsdmodule.mk | 89 -- mk/rte.combinedlib.mk | 30 - mk/rte.cpuflags.mk | 124 -- mk/rte.extapp.mk | 24 - mk/rte.extlib.mk | 26 - mk/rte.extobj.mk | 24 - mk/rte.extshared.mk | 26 - mk/rte.extsubdir.mk | 39 - mk/rte.gnuconfigure.mk | 44 - mk/rte.helper.mk | 10 - mk/rte.hostapp.mk | 93 -- mk/rte.hostlib.mk | 86 -- mk/rte.install.mk | 28 - mk/rte.lib.mk | 156 --- mk/rte.module.mk | 86 -- mk/rte.obj.mk | 82 -- mk/rte.sdkbuild.mk | 77 -- mk/rte.sdkconfig.mk | 142 -- mk/rte.sdkdepdirs.mk | 9 - mk/rte.sdkdoc.mk | 104 -- mk/rte.sdkexamples.mk | 50 - mk/rte.sdkgcov.mk | 39 - mk/rte.sdkinstall.mk | 152 --- mk/rte.sdkroot.mk | 115 -- mk/rte.sdktest.mk | 76 -- mk/rte.shared.mk | 108 -- mk/rte.subdir.mk | 65 - mk/rte.vars.mk | 102 -- mk/target/generic/rte.app.mk | 13 - mk/target/generic/rte.vars.mk | 132 -- mk/toolchain/clang/rte.toolchain-compat.mk | 22 - mk/toolchain/clang/rte.vars.mk | 60 - mk/toolchain/gcc/rte.toolchain-compat.mk | 120 -- mk/toolchain/gcc/rte.vars.mk | 109 -- mk/toolchain/icc/rte.toolchain-compat.mk | 58 - mk/toolchain/icc/rte.vars.mk | 62 - 616 files changed, 1213 insertions(+), 20010 deletions(-) delete mode 100644 GNUmakefile delete mode 100644 app/Makefile delete mode 100644 app/pdump/Makefile delete mode 100644 app/proc-info/Makefile delete mode 100644 app/test-acl/Makefile delete mode 100644 app/test-bbdev/Makefile delete mode 100644 app/test-cmdline/Makefile delete mode 100644 app/test-compress-perf/Makefile delete mode 100644 app/test-crypto-perf/Makefile delete mode 100644 app/test-eventdev/Makefile delete mode 100644 app/test-fib/Makefile delete mode 100644 app/test-flow-perf/Makefile delete mode 100644 app/test-pipeline/Makefile delete mode 100644 app/test-pmd/Makefile delete mode 100644 app/test-regex/Makefile delete mode 100644 app/test-sad/Makefile delete mode 100644 app/test/Makefile delete mode 100644 buildtools/Makefile delete mode 100755 buildtools/auto-config-h.sh delete mode 100755 buildtools/gen-build-mk.sh delete mode 100755 buildtools/gen-config-h.sh delete mode 100644 buildtools/pmdinfogen/Makefile delete mode 100755 buildtools/relpath.sh delete mode 100644 config/common_armv8a_linux delete mode 100644 config/common_base delete mode 100644 config/common_freebsd delete mode 100644 config/common_linux delete mode 120000 config/defconfig_arm-armv7a-linux-gcc delete mode 100644 config/defconfig_arm-armv7a-linuxapp-gcc delete mode 120000 config/defconfig_arm64-armada-linux-gcc delete mode 100644 config/defconfig_arm64-armada-linuxapp-gcc delete mode 120000 config/defconfig_arm64-armv8a-linux-clang delete mode 120000 config/defconfig_arm64-armv8a-linux-gcc delete mode 100644 config/defconfig_arm64-armv8a-linuxapp-clang delete mode 100644 config/defconfig_arm64-armv8a-linuxapp-gcc delete mode 120000 config/defconfig_arm64-bluefield-linux-gcc delete mode 100644 config/defconfig_arm64-bluefield-linuxapp-gcc delete mode 120000 config/defconfig_arm64-dpaa-linux-gcc delete mode 100644 config/defconfig_arm64-dpaa-linuxapp-gcc delete mode 120000 config/defconfig_arm64-emag-linux-gcc delete mode 100644 config/defconfig_arm64-emag-linuxapp-gcc delete mode 120000 config/defconfig_arm64-n1sdp-linux-gcc delete mode 100644 config/defconfig_arm64-n1sdp-linuxapp-gcc delete mode 120000 config/defconfig_arm64-octeontx2-linux-gcc delete mode 100644 config/defconfig_arm64-octeontx2-linuxapp-gcc delete mode 120000 config/defconfig_arm64-stingray-linux-gcc delete mode 100644 config/defconfig_arm64-stingray-linuxapp-gcc delete mode 120000 config/defconfig_arm64-thunderx-linux-gcc delete mode 100644 config/defconfig_arm64-thunderx-linuxapp-gcc delete mode 120000 config/defconfig_arm64-thunderx2-linux-gcc delete mode 100644 config/defconfig_arm64-thunderx2-linuxapp-gcc delete mode 120000 config/defconfig_arm64-xgene1-linux-gcc delete mode 100644 config/defconfig_arm64-xgene1-linuxapp-gcc delete mode 120000 config/defconfig_i686-native-linux-gcc delete mode 120000 config/defconfig_i686-native-linux-icc delete mode 100644 config/defconfig_i686-native-linuxapp-gcc delete mode 100644 config/defconfig_i686-native-linuxapp-icc delete mode 120000 config/defconfig_ppc_64-power8-linux-gcc delete mode 100644 config/defconfig_ppc_64-power8-linuxapp-gcc delete mode 100644 config/defconfig_x86_64-native-bsdapp-clang delete mode 100644 config/defconfig_x86_64-native-bsdapp-gcc delete mode 120000 config/defconfig_x86_64-native-freebsd-clang delete mode 120000 config/defconfig_x86_64-native-freebsd-gcc delete mode 120000 config/defconfig_x86_64-native-linux-clang delete mode 120000 config/defconfig_x86_64-native-linux-gcc delete mode 120000 config/defconfig_x86_64-native-linux-icc delete mode 100644 config/defconfig_x86_64-native-linuxapp-clang delete mode 100644 config/defconfig_x86_64-native-linuxapp-gcc delete mode 100644 config/defconfig_x86_64-native-linuxapp-icc delete mode 120000 config/defconfig_x86_x32-native-linux-gcc delete mode 100644 config/defconfig_x86_x32-native-linuxapp-gcc delete mode 100755 devtools/test-build.sh delete mode 100644 doc/build-sdk-quick.txt delete mode 100644 doc/guides/prog_guide/dev_kit_build_system.rst delete mode 100644 doc/guides/prog_guide/dev_kit_root_make_help.rst delete mode 100644 doc/guides/prog_guide/ext_app_lib_make_help.rst delete mode 100644 drivers/Makefile delete mode 100644 drivers/baseband/Makefile delete mode 100644 drivers/baseband/fpga_5gnr_fec/Makefile delete mode 100644 drivers/baseband/fpga_lte_fec/Makefile delete mode 100644 drivers/baseband/null/Makefile delete mode 100644 drivers/baseband/turbo_sw/Makefile delete mode 100644 drivers/bus/Makefile delete mode 100644 drivers/bus/dpaa/Makefile delete mode 100644 drivers/bus/fslmc/Makefile delete mode 100644 drivers/bus/ifpga/Makefile delete mode 100644 drivers/bus/pci/Makefile delete mode 100644 drivers/bus/pci/bsd/Makefile delete mode 100644 drivers/bus/pci/linux/Makefile delete mode 100644 drivers/bus/vdev/Makefile delete mode 100644 drivers/bus/vmbus/Makefile delete mode 100644 drivers/bus/vmbus/linux/Makefile delete mode 100644 drivers/common/Makefile delete mode 100644 drivers/common/cpt/Makefile delete mode 100644 drivers/common/dpaax/Makefile delete mode 100644 drivers/common/iavf/Makefile delete mode 100644 drivers/common/mlx5/Makefile delete mode 100644 drivers/common/mvep/Makefile delete mode 100644 drivers/common/octeontx/Makefile delete mode 100644 drivers/common/octeontx2/Makefile delete mode 100644 drivers/common/qat/Makefile delete mode 100644 drivers/compress/Makefile delete mode 100644 drivers/compress/isal/Makefile delete mode 100644 drivers/compress/octeontx/Makefile delete mode 100644 drivers/compress/zlib/Makefile delete mode 100644 drivers/crypto/Makefile delete mode 100644 drivers/crypto/aesni_gcm/Makefile delete mode 100644 drivers/crypto/aesni_mb/Makefile delete mode 100644 drivers/crypto/armv8/Makefile delete mode 100644 drivers/crypto/caam_jr/Makefile delete mode 100644 drivers/crypto/ccp/Makefile delete mode 100644 drivers/crypto/dpaa2_sec/Makefile delete mode 100644 drivers/crypto/dpaa_sec/Makefile delete mode 100644 drivers/crypto/kasumi/Makefile delete mode 100644 drivers/crypto/mvsam/Makefile delete mode 100644 drivers/crypto/nitrox/Makefile delete mode 100644 drivers/crypto/null/Makefile delete mode 100644 drivers/crypto/octeontx/Makefile delete mode 100644 drivers/crypto/octeontx2/Makefile delete mode 100644 drivers/crypto/openssl/Makefile delete mode 100644 drivers/crypto/scheduler/Makefile delete mode 100644 drivers/crypto/snow3g/Makefile delete mode 100644 drivers/crypto/virtio/Makefile delete mode 100644 drivers/crypto/zuc/Makefile delete mode 100644 drivers/event/Makefile delete mode 100644 drivers/event/dpaa/Makefile delete mode 100644 drivers/event/dpaa2/Makefile delete mode 100644 drivers/event/dsw/Makefile delete mode 100644 drivers/event/octeontx/Makefile delete mode 100644 drivers/event/octeontx2/Makefile delete mode 100644 drivers/event/opdl/Makefile delete mode 100644 drivers/event/skeleton/Makefile delete mode 100644 drivers/event/sw/Makefile delete mode 100644 drivers/mempool/Makefile delete mode 100644 drivers/mempool/bucket/Makefile delete mode 100644 drivers/mempool/dpaa/Makefile delete mode 100644 drivers/mempool/dpaa2/Makefile delete mode 100644 drivers/mempool/octeontx/Makefile delete mode 100644 drivers/mempool/octeontx2/Makefile delete mode 100644 drivers/mempool/ring/Makefile delete mode 100644 drivers/mempool/stack/Makefile delete mode 100644 drivers/net/Makefile delete mode 100644 drivers/net/af_packet/Makefile delete mode 100644 drivers/net/af_xdp/Makefile delete mode 100644 drivers/net/ark/Makefile delete mode 100644 drivers/net/atlantic/Makefile delete mode 100644 drivers/net/avp/Makefile delete mode 100644 drivers/net/axgbe/Makefile delete mode 100644 drivers/net/bnx2x/Makefile delete mode 100644 drivers/net/bnxt/Makefile delete mode 100644 drivers/net/bnxt/hcapi/Makefile delete mode 100644 drivers/net/bnxt/tf_core/Makefile delete mode 100644 drivers/net/bnxt/tf_ulp/Makefile delete mode 100644 drivers/net/bonding/Makefile delete mode 100644 drivers/net/cxgbe/Makefile delete mode 100644 drivers/net/dpaa/Makefile delete mode 100644 drivers/net/dpaa2/Makefile delete mode 100644 drivers/net/e1000/Makefile delete mode 100644 drivers/net/ena/Makefile delete mode 100644 drivers/net/enetc/Makefile delete mode 100644 drivers/net/enic/Makefile delete mode 100644 drivers/net/failsafe/Makefile delete mode 100644 drivers/net/fm10k/Makefile delete mode 100644 drivers/net/hinic/Makefile delete mode 100644 drivers/net/hns3/Makefile delete mode 100644 drivers/net/i40e/Makefile delete mode 100644 drivers/net/iavf/Makefile delete mode 100644 drivers/net/ice/Makefile delete mode 100644 drivers/net/igc/Makefile delete mode 100644 drivers/net/ionic/Makefile delete mode 100644 drivers/net/ipn3ke/Makefile delete mode 100644 drivers/net/ixgbe/Makefile delete mode 100644 drivers/net/kni/Makefile delete mode 100644 drivers/net/liquidio/Makefile delete mode 100644 drivers/net/memif/Makefile delete mode 100644 drivers/net/mlx4/Makefile delete mode 100644 drivers/net/mlx5/Makefile delete mode 100644 drivers/net/mvneta/Makefile delete mode 100644 drivers/net/mvpp2/Makefile delete mode 100644 drivers/net/netvsc/Makefile delete mode 100644 drivers/net/nfb/Makefile delete mode 100644 drivers/net/nfp/Makefile delete mode 100644 drivers/net/null/Makefile delete mode 100644 drivers/net/octeontx/Makefile delete mode 100644 drivers/net/octeontx2/Makefile delete mode 100644 drivers/net/pcap/Makefile delete mode 100644 drivers/net/pfe/Makefile delete mode 100644 drivers/net/qede/Makefile delete mode 100644 drivers/net/ring/Makefile delete mode 100644 drivers/net/sfc/Makefile delete mode 100644 drivers/net/softnic/Makefile delete mode 100644 drivers/net/szedata2/Makefile delete mode 100644 drivers/net/tap/Makefile delete mode 100644 drivers/net/thunderx/Makefile delete mode 100644 drivers/net/vdev_netvsc/Makefile delete mode 100644 drivers/net/vhost/Makefile delete mode 100644 drivers/net/virtio/Makefile delete mode 100644 drivers/net/vmxnet3/Makefile delete mode 100644 drivers/raw/Makefile delete mode 100644 drivers/raw/dpaa2_cmdif/Makefile delete mode 100644 drivers/raw/dpaa2_qdma/Makefile delete mode 100644 drivers/raw/ifpga/Makefile delete mode 100644 drivers/raw/ifpga/base/Makefile delete mode 100644 drivers/raw/ioat/Makefile delete mode 100644 drivers/raw/ntb/Makefile delete mode 100644 drivers/raw/octeontx2_dma/Makefile delete mode 100644 drivers/raw/octeontx2_ep/Makefile delete mode 100644 drivers/raw/skeleton/Makefile delete mode 100644 drivers/regex/Makefile delete mode 100644 drivers/regex/mlx5/Makefile delete mode 100644 drivers/vdpa/Makefile delete mode 100644 drivers/vdpa/ifc/Makefile delete mode 100644 drivers/vdpa/mlx5/Makefile delete mode 100644 examples/Makefile delete mode 100644 kernel/Makefile delete mode 100644 kernel/freebsd/Makefile delete mode 100644 kernel/freebsd/contigmem/Makefile delete mode 100644 kernel/freebsd/nic_uio/Makefile delete mode 100644 kernel/linux/Makefile delete mode 100644 kernel/linux/igb_uio/Makefile delete mode 100644 kernel/linux/kni/Makefile delete mode 100644 lib/Makefile delete mode 100644 lib/librte_acl/Makefile delete mode 100644 lib/librte_bbdev/Makefile delete mode 100644 lib/librte_bitratestats/Makefile delete mode 100644 lib/librte_bpf/Makefile delete mode 100644 lib/librte_cfgfile/Makefile delete mode 100644 lib/librte_cmdline/Makefile delete mode 100644 lib/librte_compressdev/Makefile delete mode 100644 lib/librte_cryptodev/Makefile delete mode 100644 lib/librte_distributor/Makefile delete mode 100644 lib/librte_eal/Makefile delete mode 100644 lib/librte_eal/freebsd/Makefile delete mode 100644 lib/librte_eal/include/Makefile delete mode 100644 lib/librte_eal/linux/Makefile delete mode 100644 lib/librte_efd/Makefile delete mode 100644 lib/librte_ethdev/Makefile delete mode 100644 lib/librte_eventdev/Makefile delete mode 100644 lib/librte_fib/Makefile delete mode 100644 lib/librte_flow_classify/Makefile delete mode 100644 lib/librte_graph/Makefile delete mode 100644 lib/librte_gro/Makefile delete mode 100644 lib/librte_gso/Makefile delete mode 100644 lib/librte_hash/Makefile delete mode 100644 lib/librte_ip_frag/Makefile delete mode 100644 lib/librte_ipsec/Makefile delete mode 100644 lib/librte_jobstats/Makefile delete mode 100644 lib/librte_kni/Makefile delete mode 100644 lib/librte_kvargs/Makefile delete mode 100644 lib/librte_latencystats/Makefile delete mode 100644 lib/librte_lpm/Makefile delete mode 100644 lib/librte_mbuf/Makefile delete mode 100644 lib/librte_member/Makefile delete mode 100644 lib/librte_mempool/Makefile delete mode 100644 lib/librte_meter/Makefile delete mode 100644 lib/librte_metrics/Makefile delete mode 100644 lib/librte_net/Makefile delete mode 100644 lib/librte_node/Makefile delete mode 100644 lib/librte_pci/Makefile delete mode 100644 lib/librte_pdump/Makefile delete mode 100644 lib/librte_pipeline/Makefile delete mode 100644 lib/librte_port/Makefile delete mode 100644 lib/librte_power/Makefile delete mode 100644 lib/librte_rawdev/Makefile delete mode 100644 lib/librte_rcu/Makefile delete mode 100644 lib/librte_regexdev/Makefile delete mode 100644 lib/librte_reorder/Makefile delete mode 100644 lib/librte_rib/Makefile delete mode 100644 lib/librte_ring/Makefile delete mode 100644 lib/librte_sched/Makefile delete mode 100644 lib/librte_security/Makefile delete mode 100644 lib/librte_stack/Makefile delete mode 100644 lib/librte_table/Makefile delete mode 100644 lib/librte_telemetry/Makefile delete mode 100644 lib/librte_timer/Makefile delete mode 100644 lib/librte_vhost/Makefile delete mode 100644 mk/arch/arm/rte.vars.mk delete mode 100644 mk/arch/arm64/rte.vars.mk delete mode 100644 mk/arch/i686/rte.vars.mk delete mode 100644 mk/arch/ppc_64/rte.vars.mk delete mode 100644 mk/arch/x86_64/rte.vars.mk delete mode 100644 mk/arch/x86_x32/rte.vars.mk delete mode 120000 mk/exec-env/bsdapp delete mode 100644 mk/exec-env/freebsd/rte.app.mk delete mode 100644 mk/exec-env/freebsd/rte.vars.mk delete mode 100644 mk/exec-env/linux/rte.app.mk delete mode 100644 mk/exec-env/linux/rte.vars.mk delete mode 120000 mk/exec-env/linuxapp delete mode 100644 mk/internal/rte.build-post.mk delete mode 100644 mk/internal/rte.build-pre.mk delete mode 100644 mk/internal/rte.clean-post.mk delete mode 100644 mk/internal/rte.clean-pre.mk delete mode 100644 mk/internal/rte.compile-post.mk delete mode 100644 mk/internal/rte.compile-pre.mk delete mode 100644 mk/internal/rte.extvars.mk delete mode 100644 mk/internal/rte.install-post.mk delete mode 100644 mk/internal/rte.install-pre.mk delete mode 100644 mk/machine/armv7a/rte.vars.mk delete mode 100644 mk/machine/armv8a/rte.vars.mk delete mode 100644 mk/machine/default/rte.vars.mk delete mode 100644 mk/machine/dpaa/rte.vars.mk delete mode 100644 mk/machine/emag/rte.vars.mk delete mode 100644 mk/machine/hsw/rte.vars.mk delete mode 100644 mk/machine/ivb/rte.vars.mk delete mode 100644 mk/machine/n1sdp/rte.vars.mk delete mode 100644 mk/machine/native/rte.vars.mk delete mode 100644 mk/machine/nhm/rte.vars.mk delete mode 100644 mk/machine/octeontx2/rte.vars.mk delete mode 100644 mk/machine/power8/rte.vars.mk delete mode 100644 mk/machine/silvermont/rte.vars.mk delete mode 100644 mk/machine/snb/rte.vars.mk delete mode 100644 mk/machine/thunderx/rte.vars.mk delete mode 100644 mk/machine/thunderx2/rte.vars.mk delete mode 100644 mk/machine/wsm/rte.vars.mk delete mode 100644 mk/machine/xgene1/rte.vars.mk delete mode 100644 mk/rte.app.mk delete mode 100644 mk/rte.bsdmodule.mk delete mode 100644 mk/rte.combinedlib.mk delete mode 100644 mk/rte.cpuflags.mk delete mode 100644 mk/rte.extapp.mk delete mode 100644 mk/rte.extlib.mk delete mode 100644 mk/rte.extobj.mk delete mode 100644 mk/rte.extshared.mk delete mode 100644 mk/rte.extsubdir.mk delete mode 100644 mk/rte.gnuconfigure.mk delete mode 100644 mk/rte.helper.mk delete mode 100644 mk/rte.hostapp.mk delete mode 100644 mk/rte.hostlib.mk delete mode 100644 mk/rte.install.mk delete mode 100644 mk/rte.lib.mk delete mode 100644 mk/rte.module.mk delete mode 100644 mk/rte.obj.mk delete mode 100644 mk/rte.sdkbuild.mk delete mode 100644 mk/rte.sdkconfig.mk delete mode 100644 mk/rte.sdkdepdirs.mk delete mode 100644 mk/rte.sdkdoc.mk delete mode 100644 mk/rte.sdkexamples.mk delete mode 100644 mk/rte.sdkgcov.mk delete mode 100644 mk/rte.sdkinstall.mk delete mode 100644 mk/rte.sdkroot.mk delete mode 100644 mk/rte.sdktest.mk delete mode 100644 mk/rte.shared.mk delete mode 100644 mk/rte.subdir.mk delete mode 100644 mk/rte.vars.mk delete mode 100644 mk/target/generic/rte.app.mk delete mode 100644 mk/target/generic/rte.vars.mk delete mode 100644 mk/toolchain/clang/rte.toolchain-compat.mk delete mode 100644 mk/toolchain/clang/rte.vars.mk delete mode 100644 mk/toolchain/gcc/rte.toolchain-compat.mk delete mode 100644 mk/toolchain/gcc/rte.vars.mk delete mode 100644 mk/toolchain/icc/rte.toolchain-compat.mk delete mode 100644 mk/toolchain/icc/rte.vars.mk
Signature · 1 line
2.28.0
PATCH v4 1/31 doc: build without using make
From: Bruce Richardson <[email protected]>
When building the DPDK guide documents, the DPDK version information was pulled using "make showversion", which meant there was a dependency on the DPDK make-based build system. Change this to have the version info passed in from meson itself.
--- buildtools/call-sphinx-build.py | 5 ++++- doc/guides/conf.py | 7 +------ doc/guides/meson.build | 3 ++- 3 files changed, 7 insertions(+), 8 deletions(-)
buildtools/call-sphinx-build.py +4 -1
@@ -9,7 +9,10 @@ from subprocess import run, PIPE, STDOUT from distutils.version import StrictVersion -(sphinx, src, dst) = sys.argv[1:] # assign parameters to variables +(sphinx, version, src, dst) = sys.argv[1:] # assign parameters to variables + +# set the version in environment for sphinx to pick up +os.environ['DPDK_VERSION'] = version # for sphinx version >= 1.7 add parallelism using "-j auto" ver = run([sphinx, '--version'], stdout=PIPE,
doc/guides/conf.py +1 -6
@@ -2,7 +2,6 @@ # Copyright(c) 2010-2015 Intel Corporation from __future__ import print_function -import subprocess from docutils import nodes from distutils.version import LooseVersion from sphinx import __version__ as sphinx_version
@@ -38,11 +37,7 @@ html_show_copyright = False highlight_language = 'none' -# If MAKEFLAGS is exported by the user, garbage text might end up in version -version = subprocess.check_output(['make', '-sRrC', '../../', 'showversion'], - env=dict(environ, MAKEFLAGS="")) -version = version.decode('utf-8').rstrip() -release = version +release = environ['DPDK_VERSION'] master_doc = 'index'
doc/guides/meson.build +2 -1
@@ -11,7 +11,8 @@ htmldir = join_paths(get_option('datadir'), 'doc', 'dpdk') html_guides = custom_target('html_guides', input: files('index.rst'), output: 'html', - command: [sphinx_wrapper, sphinx, meson.current_source_dir(), meson.current_build_dir()], + command: [sphinx_wrapper, sphinx, meson.project_version(), + meson.current_source_dir(), meson.current_build_dir()], depfile: '.html.d', build_by_default: get_option('enable_docs'), install: get_option('enable_docs'),
Signature · 1 line
2.28.0
PATCH v4 2/31 examples: remove legacy sections of makefiles
In reply to Thomas MonjalonFrom: Ciara Power <[email protected]>
The example app makefiles contained sections using the legacy method of compiling with make. These are no longer needed, and are removed, leaving only the section that uses pkg-config for the make build.
--- examples/bbdev_app/Makefile | 23 ++------------- examples/bond/Makefile | 34 ++-------------------- examples/cmdline/Makefile | 29 ++----------------- examples/distributor/Makefile | 30 ++----------------- examples/eventdev_pipeline/Makefile | 23 ++------------- examples/fips_validation/Makefile | 34 ++-------------------- examples/flow_classify/Makefile | 29 ++----------------- examples/flow_filtering/Makefile | 23 ++------------- examples/helloworld/Makefile | 23 ++------------- examples/ioat/Makefile | 22 ++------------ examples/ip_fragmentation/Makefile | 29 ++----------------- examples/ip_pipeline/Makefile | 36 ++--------------------- examples/ip_reassembly/Makefile | 29 ++----------------- examples/ipsec-secgw/Makefile | 36 ++--------------------- examples/ipv4_multicast/Makefile | 29 ++----------------- examples/kni/Makefile | 27 ++---------------- examples/l2fwd-cat/Makefile | 38 ++----------------------- examples/l2fwd-crypto/Makefile | 28 ++---------------- examples/l2fwd-event/Makefile | 22 ++------------ examples/l2fwd-jobstats/Makefile | 23 ++------------- examples/l2fwd-keepalive/Makefile | 23 ++------------- examples/l2fwd/Makefile | 23 ++------------- examples/l3fwd-acl/Makefile | 28 ++---------------- examples/l3fwd-graph/Makefile | 23 ++------------- examples/l3fwd-power/Makefile | 36 ++--------------------- examples/l3fwd/Makefile | 23 ++------------- examples/link_status_interrupt/Makefile | 22 ++------------ examples/ntb/Makefile | 32 ++------------------- examples/packet_ordering/Makefile | 22 ++------------ examples/ptpclient/Makefile | 28 ++---------------- examples/qos_meter/Makefile | 28 ++---------------- examples/qos_sched/Makefile | 31 ++------------------ examples/rxtx_callbacks/Makefile | 31 ++------------------ examples/service_cores/Makefile | 28 ++---------------- examples/skeleton/Makefile | 29 ++----------------- examples/tep_termination/Makefile | 27 ++---------------- examples/timer/Makefile | 28 ++---------------- examples/vdpa/Makefile | 32 ++------------------- examples/vhost/Makefile | 30 ++----------------- examples/vhost_blk/Makefile | 31 ++------------------ examples/vhost_crypto/Makefile | 31 ++------------------ examples/vmdq/Makefile | 23 ++------------- examples/vmdq_dcb/Makefile | 31 ++------------------ 43 files changed, 129 insertions(+), 1078 deletions(-)
examples/bbdev_app/Makefile +3 -20
@@ -8,7 +8,9 @@ APP = bbdev SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -39,22 +41,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -DALLOW_EXPERIMENTAL_API -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif
examples/bond/Makefile +3 -31
@@ -8,7 +8,9 @@ APP = bond_app SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -41,33 +43,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += $(WERROR_FLAGS) - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -CFLAGS += -O3 -CFLAGS += -DALLOW_EXPERIMENTAL_API - -ifeq ($(CONFIG_RTE_BUILD_SHARED_LIB),y) -LDLIBS += -lrte_pmd_bond -endif - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif
examples/cmdline/Makefile +3 -26
@@ -8,7 +8,9 @@ APP = cmdline SRCS-y := main.c commands.c parse_obj_list.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,28 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -# binary name -APP = cmdline - -# all source are stored in SRCS-y -SRCS-y := main.c commands.c parse_obj_list.c - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif
examples/distributor/Makefile +3 -27
@@ -8,7 +8,9 @@ APP = distributor_app SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,29 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -EXTRA_CFLAGS += -O3 -Wfatal-errors - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif
examples/eventdev_pipeline/Makefile +3 -20
@@ -10,7 +10,9 @@ SRCS-y += pipeline_worker_generic.c SRCS-y += pipeline_worker_tx.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -39,22 +41,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -DALLOW_EXPERIMENTAL_API -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif
examples/fips_validation/Makefile +3 -31
@@ -18,7 +18,9 @@ SRCS-y += fips_validation_xts.c SRCS-y += main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -47,33 +49,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -INC += $(sort $(wildcard *.h)) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += $(WERROR_FLAGS) - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -CFLAGS += -DALLOW_EXPERIMENTAL_API -CFLAGS += -I$(SRCDIR) -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif
examples/flow_classify/Makefile +3 -26
@@ -8,7 +8,9 @@ APP = flow_classify SRCS-y := flow_classify.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -39,28 +41,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -DALLOW_EXPERIMENTAL_API -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif
examples/flow_filtering/Makefile +3 -20
@@ -6,7 +6,9 @@ APP = flow SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -35,22 +37,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif
examples/helloworld/Makefile +3 -20
@@ -8,7 +8,9 @@ APP = helloworld SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,22 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif
examples/ioat/Makefile +3 -19
@@ -8,7 +8,9 @@ APP = ioatfwd SRCS-y := ioatfwd.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,21 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/ip_fragmentation/Makefile +3 -26
@@ -9,7 +9,9 @@ APP = ip_fragmentation SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -39,28 +41,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif
examples/ip_pipeline/Makefile +3 -33
@@ -21,7 +21,9 @@ SRCS-y += tmgr.c SRCS-y += cryptodev.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -57,35 +59,3 @@ build: clean: rm -f build/$(APP)* build/*.o test -d build && rmdir -p build || true - -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -ifneq ($(CONFIG_RTE_EXEC_ENV_LINUX),y) -$(info This application can only operate in a linux environment, \ -please change the definition of the RTE_TARGET environment variable) -all: -clean: -else - -INC += $(sort $(wildcard *.h)) - -SRCS-$(CONFIG_RTE_LIBRTE_PIPELINE) := $(SRCS-y) - -CFLAGS += -DALLOW_EXPERIMENTAL_API -CFLAGS += -I$(SRCDIR) -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif -endif
examples/ip_reassembly/Makefile +3 -26
@@ -9,7 +9,9 @@ APP = ip_reassembly SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -38,28 +40,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif
examples/ipsec-secgw/Makefile +3 -33
@@ -23,7 +23,9 @@ SRCS-y += flow.c CFLAGS += -gdwarf-2 # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -54,35 +56,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -ifneq ($(MAKECMDGOALS),clean) -ifneq ($(CONFIG_RTE_LIBRTE_IPSEC),y) -$(error "RTE_LIBRTE_IPSEC is required to build ipsec-secgw") -endif -endif - -CFLAGS += -DALLOW_EXPERIMENTAL_API -CFLAGS += -O3 -gdwarf-2 -CFLAGS += $(WERROR_FLAGS) -ifeq ($(CONFIG_RTE_TOOLCHAIN_ICC),y) -CFLAGS_sa.o += -diag-disable=vec -endif - -ifeq ($(DEBUG),1) -CFLAGS += -DIPSEC_DEBUG -fstack-protector-all -O0 -endif - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif
examples/ipv4_multicast/Makefile +3 -26
@@ -9,7 +9,9 @@ APP = ipv4_multicast SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -38,28 +40,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif
examples/kni/Makefile +3 -24
@@ -8,7 +8,9 @@ APP = kni SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -38,26 +40,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -ifneq ($(CONFIG_RTE_EXEC_ENV_LINUX),y) -$(error This application can only operate in a linux environment, \ -please change the definition of the RTE_TARGET environment variable) -endif - -CFLAGS += -O3 -CFLAGS += -DALLOW_EXPERIMENTAL_API -CFLAGS += $(WERROR_FLAGS) - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/l2fwd-cat/Makefile +3 -35
@@ -8,7 +8,9 @@ APP = l2fwd-cat SRCS-y := l2fwd-cat.c cat.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -39,37 +41,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -ifeq ($(PQOS_INSTALL_PATH),) -$(error "Please define PQOS_INSTALL_PATH environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -EXTRA_CFLAGS += -O3 -g -Wfatal-errors - -CFLAGS += -I$(PQOS_INSTALL_PATH)/../include - -LDLIBS += -L$(PQOS_INSTALL_PATH) -LDLIBS += -lpqos - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/l2fwd-crypto/Makefile +3 -25
@@ -8,7 +8,9 @@ APP = l2fwd-crypto SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,27 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -DALLOW_EXPERIMENTAL_API -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) - -ifeq ($(CONFIG_RTE_BUILD_SHARED_LIB),y) -ifeq ($(CONFIG_RTE_LIBRTE_PMD_CRYPTO_SCHEDULER),y) -LDLIBS += -lrte_pmd_crypto_scheduler -endif -endif - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/l2fwd-event/Makefile +3 -19
@@ -14,7 +14,9 @@ SRCS-y += l2fwd_event_generic.c SRCS-y += l2fwd_event_internal_port.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -43,21 +45,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/l2fwd-jobstats/Makefile +3 -20
@@ -8,7 +8,9 @@ APP = l2fwd-jobstats SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,22 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/l2fwd-keepalive/Makefile +3 -20
@@ -8,7 +8,9 @@ APP = l2fwd-keepalive SRCS-y := main.c shm.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -39,22 +41,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API -LDFLAGS += -lrt - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/l2fwd/Makefile +3 -20
@@ -8,7 +8,9 @@ APP = l2fwd SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -39,22 +41,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -# Add flag to allow experimental API as l2fwd uses rte_ethdev_set_ptype API -CFLAGS += -DALLOW_EXPERIMENTAL_API - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/l3fwd-acl/Makefile +3 -25
@@ -8,7 +8,9 @@ APP = l3fwd-acl SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,27 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/l3fwd-graph/Makefile +3 -20
@@ -8,7 +8,9 @@ APP = l3fwd-graph SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,22 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -DALLOW_EXPERIMENTAL_API -CFLAGS += -I$(SRCDIR) -CFLAGS += -O3 $(USER_FLAGS) -CFLAGS += $(WERROR_FLAGS) - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/l3fwd-power/Makefile +3 -33
@@ -8,7 +8,9 @@ APP = l3fwd-power SRCS-y := main.c perf_core.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -39,35 +41,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -ifneq ($(CONFIG_RTE_EXEC_ENV_LINUX),y) -$(info This application can only operate in a linux environment, \ -please change the definition of the RTE_TARGET environment variable) -all: -else - -CFLAGS += -DALLOW_EXPERIMENTAL_API -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -LDLIBS += -lm -lrte_telemetry - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -include $(RTE_SDK)/mk/rte.extapp.mk -endif -endif
examples/l3fwd/Makefile +3 -20
@@ -9,7 +9,9 @@ SRCS-y := main.c l3fwd_lpm.c l3fwd_em.c l3fwd_event.c SRCS-y += l3fwd_event_generic.c l3fwd_event_internal_port.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -38,22 +40,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -I$(SRCDIR) -CFLAGS += -O3 $(USER_FLAGS) -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/link_status_interrupt/Makefile +3 -19
@@ -8,7 +8,9 @@ APP = link_status_interrupt SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,21 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/ntb/Makefile +3 -29
@@ -8,8 +8,9 @@ APP = ntb_fwd SRCS-y := ntb_fwd.c # Build using pkg-config variables if possible -$(shell pkg-config --exists libdpdk) -ifeq ($(.SHELLSTATUS),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -42,30 +43,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared rmdir --ignore-fail-on-non-empty build - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, can be overridden by command line or environment -RTE_TARGET ?= x86_64-native-linuxapp-gcc - -include $(RTE_SDK)/mk/rte.vars.mk - -ifneq ($(CONFIG_RTE_EXEC_ENV_LINUXAPP),y) -$(info This application can only operate in a linuxapp environment, \ -please change the definition of the RTE_TARGET environment variable) -all: -else - -CFLAGS += -D_FILE_OFFSET_BITS=64 -CFLAGS += -O2 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif -endif
examples/packet_ordering/Makefile +3 -19
@@ -8,7 +8,9 @@ APP = packet_ordering SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,21 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/ptpclient/Makefile +3 -25
@@ -8,7 +8,9 @@ APP = ptpclient SRCS-y := ptpclient.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,27 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/qos_meter/Makefile +3 -25
@@ -8,7 +8,9 @@ APP = qos_meter SRCS-y := main.c rte_policer.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -39,27 +41,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/qos_sched/Makefile +3 -28
@@ -8,7 +8,9 @@ APP = qos_sched SRCS-y := main.c args.c init.c app_thread.c cfg_file.c cmdline.c stats.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,30 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -ifneq ($(CONFIG_RTE_EXEC_ENV_LINUX),y) -$(info This application can only operate in a linux environment, \ -please change the definition of the RTE_TARGET environment variable) -all: -clean: -else - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif -endif
examples/rxtx_callbacks/Makefile +3 -28
@@ -8,7 +8,9 @@ APP = rxtx_callbacks SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,30 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += $(WERROR_FLAGS) - -# rte_eth_read_clock is experimental -CFLAGS += -DALLOW_EXPERIMENTAL_API - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -EXTRA_CFLAGS += -O3 -g -Wfatal-errors - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/service_cores/Makefile +3 -25
@@ -8,7 +8,9 @@ APP = service_cores SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,27 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif
examples/skeleton/Makefile +3 -26
@@ -8,7 +8,9 @@ APP = basicfwd SRCS-y := basicfwd.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,28 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -EXTRA_CFLAGS += -O3 -g -Wfatal-errors - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/tep_termination/Makefile +3 -24
@@ -8,7 +8,9 @@ APP = tep_termination SRCS-y := main.c vxlan_setup.c vxlan.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -41,26 +43,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -ifneq ($(CONFIG_RTE_EXEC_ENV_LINUX),y) -$(error This application can only operate in a linux environment, \ -please change the definition of the RTE_TARGET environment variable) -endif - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -Wno-deprecated-declarations - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/timer/Makefile +3 -25
@@ -8,7 +8,9 @@ APP = timer SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,27 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/vdpa/Makefile +3 -29
@@ -9,7 +9,9 @@ SRCS-y := main.c CFLAGS += -DALLOW_EXPERIMENTAL_API # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -38,31 +40,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -ifneq ($(CONFIG_RTE_EXEC_ENV_LINUX),y) -$(info This application can only operate in a linux environment, \ -please change the definition of the RTE_TARGET environment variable) -all: -else - -CFLAGS += -O2 -D_FILE_OFFSET_BITS=64 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -D_GNU_SOURCE -CFLAGS += -DALLOW_EXPERIMENTAL_API - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif # linuxapp - -endif # pkg-config
examples/vhost/Makefile +3 -27
@@ -8,7 +8,9 @@ APP = vhost-switch SRCS-y := main.c virtio_net.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -41,29 +43,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -ifneq ($(CONFIG_RTE_EXEC_ENV_LINUX),y) -$(info This application can only operate in a linux environment, \ -please change the definition of the RTE_TARGET environment variable) -all: -else - -CFLAGS += -DALLOW_EXPERIMENTAL_API -CFLAGS += -O2 -D_FILE_OFFSET_BITS=64 -CFLAGS += $(WERROR_FLAGS) - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif -endif
examples/vhost_blk/Makefile +3 -28
@@ -8,8 +8,9 @@ APP = vhost-blk SRCS-y := blk.c vhost_blk.c vhost_blk_compat.c # Build using pkg-config variables if possible -$(shell pkg-config --exists libdpdk) -ifeq ($(.SHELLSTATUS),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -42,29 +43,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -ifneq ($(CONFIG_RTE_EXEC_ENV_LINUX),y) -$(info This application can only operate in a linux environment, \ -please change the definition of the RTE_TARGET environment variable) -all: -else - -CFLAGS += -DALLOW_EXPERIMENTAL_API -CFLAGS += -O2 -D_FILE_OFFSET_BITS=64 -CFLAGS += $(WERROR_FLAGS) - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif -endif
examples/vhost_crypto/Makefile +3 -28
@@ -9,7 +9,9 @@ SRCS-y := main.c CFLAGS += -DALLOW_EXPERIMENTAL_API # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -38,30 +40,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -ifneq ($(CONFIG_RTE_EXEC_ENV_LINUX),y) -$(info This application can only operate in a linux environment, \ -please change the definition of the RTE_TARGET environment variable) -all: -else - -CFLAGS += -DALLOW_EXPERIMENTAL_API -CFLAGS += -O2 -D_FILE_OFFSET_BITS=64 -CFLAGS += $(WERROR_FLAGS) - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif # Linux - -endif # pkg-config
examples/vmdq/Makefile +3 -20
@@ -8,7 +8,9 @@ APP = vmdq_app SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,22 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -EXTRA_CFLAGS += -O3 - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
examples/vmdq_dcb/Makefile +3 -28
@@ -8,7 +8,9 @@ APP = vmdq_dcb_app SRCS-y := main.c # Build using pkg-config variables if possible -ifeq ($(shell pkg-config --exists libdpdk && echo 0),0) +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif all: shared .PHONY: shared static
@@ -37,30 +39,3 @@ build: clean: rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared test -d build && rmdir -p build || true - -else # Build using legacy build system - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif -ifeq ($(CONFIG_RTE_TOOLCHAIN_ICC),y) -CFLAGS_main.o += -diag-disable=vec -endif -EXTRA_CFLAGS += -O3 -g - -include $(RTE_SDK)/mk/rte.extapp.mk -endif
Signature · 1 line
2.28.0
PATCH v4 3/31 examples/ka-agent: convert to pkg-config-based build
In reply to Thomas MonjalonFrom: Kevin Laatz <[email protected]>
Remove references to the old make build system and use pkg-config for building these examples.
--- examples/l2fwd-keepalive/ka-agent/Makefile | 51 ++++++++++++++++------ 1 file changed, 37 insertions(+), 14 deletions(-)
examples/l2fwd-keepalive/ka-agent/Makefile +37 -14
@@ -1,14 +1,5 @@ # SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2016 Intel Corporation - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif - -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk +# Copyright(c) 2016-2020 Intel Corporation # binary name APP = ka-agent
@@ -16,7 +7,39 @@ APP = ka-agent # all source are stored in SRCS-y SRCS-y := main.c -CFLAGS += $(WERROR_FLAGS) -I$(SRCDIR)/../ -CFLAGS += -DALLOW_EXPERIMENTAL_API -LDFLAGS += -lrt -include $(RTE_SDK)/mk/rte.extapp.mk +CFLAGS += -I.. + +# Build using pkg-config variables if possible +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") +endif + +all: shared +.PHONY: shared static +shared: build/$(APP)-shared + ln -sf $(APP)-shared build/$(APP) +static: build/$(APP)-static + ln -sf $(APP)-static build/$(APP) + +LDFLAGS += -lpthread -lrt + +PKGCONF ?= pkg-config + +PC_FILE := $(shell $(PKGCONF) --path libdpdk 2>/dev/null) +CFLAGS += -O3 $(shell $(PKGCONF) --cflags libdpdk) +LDFLAGS_SHARED = $(shell $(PKGCONF) --libs libdpdk) +LDFLAGS_STATIC = $(shell $(PKGCONF) --static --libs libdpdk) + +build/$(APP)-shared: $(SRCS-y) Makefile $(PC_FILE) | build + $(CC) $(CFLAGS) $(SRCS-y) -o $@ $(LDFLAGS) $(LDFLAGS_SHARED) + +build/$(APP)-static: $(SRCS-y) Makefile $(PC_FILE) | build + $(CC) $(CFLAGS) $(SRCS-y) -o $@ $(LDFLAGS) $(LDFLAGS_STATIC) + +build: + @mkdir -p $@ + +.PHONY: clean +clean: + rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared + test -d build && rmdir -p build || true
Signature · 1 line
2.28.0
PATCH v4 4/31 examples/server_node_efd: convert to pkg-config-based build
In reply to Thomas MonjalonFrom: Kevin Laatz <[email protected]>
Remove references to the old make build system and use pkg-config for building these examples.
--- examples/server_node_efd/Makefile | 18 +++----- examples/server_node_efd/node/Makefile | 46 ++++++++++++++------ examples/server_node_efd/server/Makefile | 53 +++++++++++++++--------- 3 files changed, 73 insertions(+), 44 deletions(-)
examples/server_node_efd/Makefile +6 -12
@@ -1,16 +1,10 @@ # SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2016-2017 Intel Corporation +# Copyright(c) 2016-2020 Intel Corporation -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif +subdirs := node server -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) +.PHONY: all static shared clean $(subdirs) +all static shared clean: $(subdirs) -include $(RTE_SDK)/mk/rte.vars.mk - -DIRS-$(CONFIG_RTE_EXEC_ENV_LINUX) += server -DIRS-$(CONFIG_RTE_EXEC_ENV_LINUX) += node - -include $(RTE_SDK)/mk/rte.extsubdir.mk +$(subdirs): + $(MAKE) -C $@ $(MAKECMDGOALS)
examples/server_node_efd/node/Makefile +34 -12
54 lines not on this page · raw message
examples/server_node_efd/server/Makefile +33 -20
62 lines not on this page · raw message
Signature · 1 line
2.28.0
PATCH v4 5/31 examples/performance-thread: convert to pkg-config-based build
In reply to Thomas MonjalonFrom: Kevin Laatz <[email protected]>
Remove references to the old make build system and use pkg-config for building these examples.
--- examples/performance-thread/Makefile | 21 +++---- examples/performance-thread/common/common.mk | 6 +- .../performance-thread/l3fwd-thread/Makefile | 47 +++++++++++----- .../performance-thread/pthread_shim/Makefile | 56 +++++++++++++------ 4 files changed, 83 insertions(+), 47 deletions(-)
examples/performance-thread/Makefile +7 -14
@@ -1,21 +1,14 @@ # SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2015 Intel Corporation +# Copyright(c) 2015-2020 Intel Corporation -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif +subdirs := l3fwd-thread pthread_shim -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) +.PHONY: all static shared clean $(subdirs) +all static shared clean: $(subdirs) -include $(RTE_SDK)/mk/rte.vars.mk - -ifeq ($(filter y,$(CONFIG_RTE_ARCH_X86_64) $(CONFIG_RTE_ARCH_ARM64)),) +ifeq ($(filter $(shell uname -m),x86_64 arm64),) $(error This application is only supported for x86_64 and arm64 targets) endif -DIRS-y += l3fwd-thread -DIRS-y += pthread_shim - - -include $(RTE_SDK)/mk/rte.extsubdir.mk +$(subdirs): + $(MAKE) -C $@ $(MAKECMDGOALS)
examples/performance-thread/common/common.mk +3 -3
@@ -8,9 +8,9 @@ MKFILE_PATH=$(abspath $(dir $(lastword $(MAKEFILE_LIST)))) -ifeq ($(CONFIG_RTE_ARCH_X86_64),y) +ifeq ($(shell uname -m),x86_64) ARCH_PATH += $(MKFILE_PATH)/arch/x86 -else ifeq ($(CONFIG_RTE_ARCH_ARM64),y) +else ifeq ($(shell uname -m),arm64) ARCH_PATH += $(MKFILE_PATH)/arch/arm64 endif
@@ -18,4 +18,4 @@ VPATH := $(MKFILE_PATH) $(ARCH_PATH) SRCS-y += lthread.c lthread_sched.c lthread_cond.c lthread_tls.c lthread_mutex.c lthread_diag.c ctx.c -INCLUDES += -I$(MKFILE_PATH) -I$(ARCH_PATH) +CFLAGS += -I$(MKFILE_PATH) -I$(ARCH_PATH)
examples/performance-thread/l3fwd-thread/Makefile +34 -13
57 lines not on this page · raw message
examples/performance-thread/pthread_shim/Makefile +39 -17
72 lines not on this page · raw message
Signature · 1 line
2.28.0
PATCH v4 6/31 examples/multi_process: convert to pkg-config-based build
In reply to Thomas MonjalonFrom: Bruce Richardson <[email protected]>
Remove references to the old make build system and use pkg-config for building these examples.
--- examples/multi_process/Makefile | 21 ++------ .../multi_process/client_server_mp/Makefile | 19 ++----- .../client_server_mp/mp_client/Makefile | 44 +++++++++++---- .../client_server_mp/mp_server/Makefile | 53 +++++++++++-------- examples/multi_process/hotplug_mp/Makefile | 46 +++++++++++----- examples/multi_process/simple_mp/Makefile | 44 ++++++++++----- examples/multi_process/symmetric_mp/Makefile | 44 ++++++++++----- 7 files changed, 168 insertions(+), 103 deletions(-)
examples/multi_process/Makefile +5 -16
@@ -1,18 +1,7 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014 Intel Corporation +subdirs := client_server_mp hotplug_mp simple_mp symmetric_mp -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif +.PHONY: all static shared clean $(subdirs) +all static shared clean: $(subdirs) -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -DIRS-$(CONFIG_RTE_EXEC_ENV_LINUX) += client_server_mp -DIRS-$(CONFIG_RTE_EXEC_ENV_LINUX) += simple_mp -DIRS-$(CONFIG_RTE_EXEC_ENV_LINUX) += symmetric_mp -DIRS-$(CONFIG_RTE_EXEC_ENV_LINUX) += hotplug_mp - -include $(RTE_SDK)/mk/rte.extsubdir.mk +$(subdirs): + $(MAKE) -C $@ $(MAKECMDGOALS)
examples/multi_process/client_server_mp/Makefile +5 -14
@@ -1,16 +1,7 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014 Intel Corporation +subdirs := mp_client mp_server -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif +.PHONY: all static shared clean $(subdirs) +all static shared clean: $(subdirs) -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - -DIRS-$(CONFIG_RTE_EXEC_ENV_LINUX) += mp_client -DIRS-$(CONFIG_RTE_EXEC_ENV_LINUX) += mp_server - -include $(RTE_SDK)/mk/rte.extsubdir.mk +$(subdirs): + $(MAKE) -C $@ $(MAKECMDGOALS)
examples/multi_process/client_server_mp/mp_client/Makefile +33 -11
54 lines not on this page · raw message
examples/multi_process/client_server_mp/mp_server/Makefile +31 -22
65 lines not on this page · raw message
examples/multi_process/hotplug_mp/Makefile +32 -14
54 lines not on this page · raw message
examples/multi_process/simple_mp/Makefile +31 -13
54 lines not on this page · raw message
examples/multi_process/symmetric_mp/Makefile +31 -13
54 lines not on this page · raw message
Signature · 1 line
2.28.0
PATCH v4 7/31 examples/vm_power: convert to pkg-config-based build
In reply to Thomas MonjalonFrom: Bruce Richardson <[email protected]>
Convert the makefiles to build using pkg-config
rather than the old build system.
--- examples/vm_power_manager/Makefile | 76 ++++++++++---------- examples/vm_power_manager/guest_cli/Makefile | 50 ++++++++----- 2 files changed, 67 insertions(+), 59 deletions(-)
examples/vm_power_manager/Makefile +36 -40
@@ -1,65 +1,61 @@ # SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014 Intel Corporation +# Copyright(c) 2010-2020 Intel Corporation -ifneq ($(shell pkg-config --atleast-version=0.9.3 libvirt; echo $$?), 0) -$(error vm_power_manager requires libvirt >= 0.9.3) -else - -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") +# Build using pkg-config variables if possible +ifneq ($(shell pkg-config --exists libdpdk && echo 0),0) +$(error "no installation of DPDK found") endif -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) - -include $(RTE_SDK)/mk/rte.vars.mk - # binary name APP = vm_power_mgr # all source are stored in SRCS-y SRCS-y := main.c vm_power_cli.c power_manager.c channel_manager.c SRCS-y += channel_monitor.c parse.c -ifeq ($(CONFIG_RTE_ARCH_X86_64),y) +ifeq ($(shell uname -m),x86_64) SRCS-y += oob_monitor_x86.c else SRCS-y += oob_monitor_nop.c endif -CFLAGS += -O3 -I$(RTE_SDK)/lib/librte_power/ -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -DALLOW_EXPERIMENTAL_API +all: shared +.PHONY: shared static +shared: build/$(APP)-shared + ln -sf $(APP)-shared build/$(APP) +static: build/$(APP)-static + ln -sf $(APP)-static build/$(APP) -LDLIBS += -lvirt +PKGCONF ?= pkg-config -JANSSON := $(shell pkg-config --exists jansson; echo $$?) +PC_FILE := $(shell $(PKGCONF) --path libdpdk 2>/dev/null) +CFLAGS += -O3 $(shell $(PKGCONF) --cflags libdpdk) +LDFLAGS_SHARED = $(shell $(PKGCONF) --libs libdpdk) +LDFLAGS_STATIC = $(shell $(PKGCONF) --static --libs libdpdk) + +ifneq ($(shell $(PKGCONF) --atleast-version=0.9.3 libvirt; echo $$?), 0) +$(error vm_power_manager requires libvirt >= 0.9.3) +endif +LDFLAGS += $(shell $(PKGCONF) --libs libvirt) + +JANSSON := $(shell $(PKGCONF) --exists jansson; echo $$?) ifeq ($(JANSSON), 0) -LDLIBS += $(shell pkg-config --libs jansson) +LDFLAGS += $(shell $(PKGCONF) --libs jansson) CFLAGS += -DUSE_JANSSON endif -ifeq ($(CONFIG_RTE_BUILD_SHARED_LIB),y) +# for shared library builds, we need to explicitly link these PMDs +LDFLAGS_SHARED += -lrte_pmd_ixgbe -lrte_pmd_i40e -lrte_pmd_bnxt -ifeq ($(CONFIG_RTE_LIBRTE_IXGBE_PMD),y) -LDLIBS += -lrte_pmd_ixgbe -endif +build/$(APP)-shared: $(SRCS-y) Makefile $(PC_FILE) | build + $(CC) $(CFLAGS) $(SRCS-y) -o $@ $(LDFLAGS) $(LDFLAGS_SHARED) -ifeq ($(CONFIG_RTE_LIBRTE_I40E_PMD),y) -LDLIBS += -lrte_pmd_i40e -endif +build/$(APP)-static: $(SRCS-y) Makefile $(PC_FILE) | build + $(CC) $(CFLAGS) $(SRCS-y) -o $@ $(LDFLAGS) $(LDFLAGS_STATIC) -ifeq ($(CONFIG_RTE_LIBRTE_BNXT_PMD),y) -LDLIBS += -lrte_pmd_bnxt -endif +build: + @mkdir -p $@ -endif - -# workaround for a gcc bug with noreturn attribute -# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12603 -ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y) -CFLAGS_main.o += -Wno-return-type -endif - -include $(RTE_SDK)/mk/rte.extapp.mk - -endif # libvirt check +.PHONY: clean +clean: + rm -f build/$(APP) build/$(APP)-static build/$(APP)-shared + test -d build && rmdir -p build || true
examples/vm_power_manager/guest_cli/Makefile +31 -19
59 lines not on this page · raw message
Signature · 1 line
2.28.0
PATCH v4 8/31 examples/ethtool: convert to pkg-config-based build
In reply to Thomas MonjalonFrom: Bruce Richardson <[email protected]>
Remove references to the old DPDK build system from the makefiles, and use pkg-config provided flags instead.
--- examples/ethtool/Makefile | 26 +++-------- examples/ethtool/ethtool-app/Makefile | 56 +++++++++++++++--------- examples/ethtool/lib/Makefile | 62 ++++++++++++++++----------- 3 files changed, 79 insertions(+), 65 deletions(-)
examples/ethtool/Makefile +7 -19
@@ -1,23 +1,11 @@ # SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2015 Intel Corporation +# Copyright(c) 2015-2020 Intel Corporation -ifeq ($(RTE_SDK),) -$(error "Please define RTE_SDK environment variable") -endif +subdirs := lib ethtool-app -# Default target, detect a build directory, by looking for a path with a .config -RTE_TARGET ?= $(notdir $(abspath $(dir $(firstword $(wildcard $(RTE_SDK)/*/.config))))) +.PHONY: all static shared clean $(subdirs) +all static shared clean: $(subdirs) -include $(RTE_SDK)/mk/rte.vars.mk - -ifneq ($(CONFIG_RTE_EXEC_ENV_LINUX),y) -$(info This application can only operate in a linux environment, \ -please change the definition of the RTE_TARGET environment variable) -else - -DIRS-y += lib ethtool-app -endif - -DEPDIRS-ethtool-app := lib - -include $(RTE_SDK)/mk/rte.extsubdir.mk +ethtool-app: lib +$(subdirs): + $(MAKE) -C $@ $(MAKECMDGOALS)
examples/ethtool/ethtool-app/Makefile +35 -21
66 lines not on this page · raw message
examples/ethtool/lib/Makefile +37 -25
74 lines not on this page · raw message
Signature · 1 line
2.28.0
PATCH v4 9/31 examples: remove old build system references
In reply to Thomas MonjalonFrom: Ciara Power <[email protected]>
Remove the references to RTE_SDK and RTE_TARGET environment variables from the build instructions in the comments of the various BPF files, and in the ipsec-secgw common definition script.
--- examples/bpf/t2.c | 6 ++++-- examples/bpf/t3.c | 10 ++++++---- examples/ipsec-secgw/test/common_defs.sh | 4 ++-- 3 files changed, 12 insertions(+), 8 deletions(-)
examples/bpf/t2.c +4 -2
@@ -9,8 +9,10 @@* (PKT_RX_VLAN_PKT | PKT_RX_VLAN_STRIPPED). * Doesn't touch contents of packet data. * To compile: -* clang -O2 -I${RTE_SDK}/${RTE_TARGET}/include \ -* -target bpf -Wno-int-to-void-pointer-cast -c t2.c +* clang -O2 -target bpf -Wno-int-to-void-pointer-cast -c t2.c +* +* NOTE: if DPDK is not installed system-wide, add compiler flag with path +* to DPDK rte_mbuf.h file, e.g. "clang -I/path/to/dpdk/headers -O2 ..." */ #include <stdint.h>
examples/bpf/t3.c +6 -4
@@ -8,13 +8,15 @@* Dump the mbuf into stdout if it is an ARP packet (aka tcpdump 'arp'). * * To compile on x86: -* clang -O2 -U __GNUC__ -I${RTE_SDK}/${RTE_TARGET}/include \ -* -target bpf -Wno-int-to-void-pointer-cast -c t3.c +* clang -O2 -U __GNUC__ -target bpf -Wno-int-to-void-pointer-cast -c t3.c * * To compile on ARM: -* clang -O2 -I/usr/include/aarch64-linux-gnu \ -* -I${RTE_SDK}/${RTE_TARGET}/include -target bpf \ +* clang -O2 -I/usr/include/aarch64-linux-gnu -target bpf \ * -Wno-int-to-void-pointer-cast -c t3.c +* +* NOTE: if DPDK is not installed system-wide, add compiler flag with path +* to DPDK rte_mbuf.h file to above commands, +* e.g. "clang -I/path/to/dpdk/headers -O2 ..." */ #include <stdint.h>
examples/ipsec-secgw/test/common_defs.sh +2 -2
@@ -34,8 +34,8 @@ LOCAL_IPV4=192.168.31.92 REMOTE_IPV6=fd12:3456:789a:0031:0000:0000:0000:0014 LOCAL_IPV6=fd12:3456:789a:0031:0000:0000:0000:0092 -DPDK_PATH=${RTE_SDK:-${PWD}} -DPDK_BUILD=${RTE_TARGET:-x86_64-native-linux-gcc} +DPDK_PATH=${PWD} +DPDK_BUILD="build" DPDK_VARS="" # by default ipsec-secgw can't deal with multi-segment packets
Signature · 1 line
2.28.0
PATCH v4 10/31 build: create dummy Makefile
In reply to Thomas MonjalonFrom: Bruce Richardson <[email protected]>
This patch modifies the root Makefile to act as a dummy Makefile for when the make support is removed from DPDK in subsequent patches.
--- Makefile | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
Makefile +5 -2
@@ -1,4 +1,7 @@ # SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014 Intel Corporation +# Copyright(c) 2010-2020 Intel Corporation -.error Error please compile using GNU Make (gmake) +.PHONY: all +all: + @echo "To build DPDK please use meson and ninja as described at" + @echo " https://core.dpdk.org/doc/quick-start/"
Signature · 1 line
2.28.0
PATCH v4 11/31 build: remove makefiles
In reply to Thomas MonjalonFrom: Ciara Power <[email protected]>
A decision was made [1] to no longer support Make in DPDK, this patch removes all Makefiles that do not make use of pkg-config, along with the mk directory previously used by make.
[1] https://mails.dpdk.org/archives/dev/2020-April/162839.html
--- GNUmakefile | 17 - MAINTAINERS | 11 +- app/Makefile | 34 -- app/pdump/Makefile | 18 - app/proc-info/Makefile | 14 - app/test-acl/Makefile | 17 - app/test-bbdev/Makefile | 30 -- app/test-cmdline/Makefile | 24 - app/test-compress-perf/Makefile | 19 - app/test-crypto-perf/Makefile | 28 - app/test-eventdev/Makefile | 32 -- app/test-fib/Makefile | 18 - app/test-flow-perf/Makefile | 26 - app/test-pipeline/Makefile | 33 -- app/test-pmd/Makefile | 73 --- app/test-regex/Makefile | 13 - app/test-sad/Makefile | 17 - app/test/Makefile | 310 ----------- buildtools/Makefile | 9 - buildtools/pmdinfogen/Makefile | 20 - devtools/git-log-fixes.sh | 2 +- devtools/test-build.sh | 315 ----------- doc/build-sdk-quick.txt | 34 -- doc/guides/contributing/coding_style.rst | 48 +- doc/guides/contributing/patches.rst | 49 -- doc/guides/freebsd_gsg/intro.rst | 4 +- doc/guides/linux_gsg/build_dpdk.rst | 68 +-- doc/guides/linux_gsg/build_sample_apps.rst | 51 +- .../linux_gsg/cross_build_dpdk_for_arm64.rst | 48 +- doc/guides/linux_gsg/intro.rst | 2 +- doc/guides/linux_gsg/sys_reqs.rst | 10 +- doc/guides/prog_guide/build_app.rst | 56 +- .../prog_guide/dev_kit_build_system.rst | 331 ------------ .../prog_guide/dev_kit_root_make_help.rst | 188 ------- .../prog_guide/ext_app_lib_make_help.rst | 98 ---- doc/guides/prog_guide/index.rst | 3 - doc/guides/prog_guide/intro.rst | 2 +- doc/guides/prog_guide/overview.rst | 12 +- doc/guides/prog_guide/source_org.rst | 23 +- doc/guides/rel_notes/deprecation.rst | 7 - drivers/Makefile | 34 -- drivers/baseband/Makefile | 18 - drivers/baseband/fpga_5gnr_fec/Makefile | 28 - drivers/baseband/fpga_lte_fec/Makefile | 25 - drivers/baseband/null/Makefile | 21 - drivers/baseband/turbo_sw/Makefile | 52 -- drivers/bus/Makefile | 15 - drivers/bus/dpaa/Makefile | 48 -- drivers/bus/fslmc/Makefile | 47 -- drivers/bus/ifpga/Makefile | 28 - drivers/bus/pci/Makefile | 33 -- drivers/bus/pci/bsd/Makefile | 4 - drivers/bus/pci/linux/Makefile | 6 - drivers/bus/vdev/Makefile | 27 - drivers/bus/vmbus/Makefile | 33 -- drivers/bus/vmbus/linux/Makefile | 3 - drivers/common/Makefile | 39 -- drivers/common/cpt/Makefile | 24 - drivers/common/dpaax/Makefile | 30 -- drivers/common/iavf/Makefile | 27 - drivers/common/mlx5/Makefile | 404 -------------- drivers/common/mvep/Makefile | 35 -- drivers/common/octeontx/Makefile | 22 - drivers/common/octeontx2/Makefile | 39 -- drivers/common/qat/Makefile | 74 --- drivers/compress/Makefile | 10 - drivers/compress/isal/Makefile | 27 - drivers/compress/octeontx/Makefile | 26 - drivers/compress/zlib/Makefile | 25 - drivers/crypto/Makefile | 31 -- drivers/crypto/aesni_gcm/Makefile | 43 -- drivers/crypto/aesni_mb/Makefile | 42 -- drivers/crypto/armv8/Makefile | 36 -- drivers/crypto/caam_jr/Makefile | 39 -- drivers/crypto/ccp/Makefile | 32 -- drivers/crypto/dpaa2_sec/Makefile | 45 -- drivers/crypto/dpaa_sec/Makefile | 38 -- drivers/crypto/kasumi/Makefile | 42 -- drivers/crypto/mvsam/Makefile | 40 -- drivers/crypto/nitrox/Makefile | 30 -- drivers/crypto/null/Makefile | 27 - drivers/crypto/octeontx/Makefile | 36 -- drivers/crypto/octeontx2/Makefile | 49 -- drivers/crypto/openssl/Makefile | 26 - drivers/crypto/scheduler/Makefile | 34 -- drivers/crypto/snow3g/Makefile | 43 -- drivers/crypto/virtio/Makefile | 33 -- drivers/crypto/zuc/Makefile | 42 -- drivers/event/Makefile | 20 - drivers/event/dpaa/Makefile | 39 -- drivers/event/dpaa2/Makefile | 41 -- drivers/event/dsw/Makefile | 26 - drivers/event/octeontx/Makefile | 51 -- drivers/event/octeontx2/Makefile | 47 -- drivers/event/opdl/Makefile | 29 - drivers/event/skeleton/Makefile | 24 - drivers/event/sw/Makefile | 29 - drivers/mempool/Makefile | 18 - drivers/mempool/bucket/Makefile | 25 - drivers/mempool/dpaa/Makefile | 30 -- drivers/mempool/dpaa2/Makefile | 31 -- drivers/mempool/octeontx/Makefile | 39 -- drivers/mempool/octeontx2/Makefile | 40 -- drivers/mempool/ring/Makefile | 19 - drivers/mempool/stack/Makefile | 22 - drivers/net/Makefile | 84 --- drivers/net/af_packet/Makefile | 27 - drivers/net/af_xdp/Makefile | 26 - drivers/net/ark/Makefile | 39 -- drivers/net/atlantic/Makefile | 34 -- drivers/net/avp/Makefile | 29 - drivers/net/axgbe/Makefile | 33 -- drivers/net/bnx2x/Makefile | 33 -- drivers/net/bnxt/Makefile | 63 --- drivers/net/bnxt/hcapi/Makefile | 5 - drivers/net/bnxt/tf_core/Makefile | 31 -- drivers/net/bnxt/tf_ulp/Makefile | 20 - drivers/net/bonding/Makefile | 36 -- drivers/net/cxgbe/Makefile | 57 -- drivers/net/dpaa/Makefile | 41 -- drivers/net/dpaa2/Makefile | 47 -- drivers/net/e1000/Makefile | 79 --- drivers/net/ena/Makefile | 30 -- drivers/net/enetc/Makefile | 23 - drivers/net/enic/Makefile | 68 --- drivers/net/failsafe/Makefile | 43 -- drivers/net/fm10k/Makefile | 77 --- drivers/net/hinic/Makefile | 67 --- drivers/net/hns3/Makefile | 42 -- drivers/net/i40e/Makefile | 112 ---- drivers/net/iavf/Makefile | 54 -- drivers/net/ice/Makefile | 96 ---- drivers/net/igc/Makefile | 40 -- drivers/net/ionic/Makefile | 31 -- drivers/net/ipn3ke/Makefile | 38 -- drivers/net/ixgbe/Makefile | 110 ---- drivers/net/kni/Makefile | 30 -- drivers/net/liquidio/Makefile | 30 -- drivers/net/memif/Makefile | 26 - drivers/net/mlx4/Makefile | 142 ----- drivers/net/mlx5/Makefile | 82 --- drivers/net/mvneta/Makefile | 39 -- drivers/net/mvpp2/Makefile | 42 -- drivers/net/netvsc/Makefile | 21 - drivers/net/nfb/Makefile | 40 -- drivers/net/nfp/Makefile | 41 -- drivers/net/null/Makefile | 24 - drivers/net/octeontx/Makefile | 53 -- drivers/net/octeontx2/Makefile | 63 --- drivers/net/pcap/Makefile | 32 -- drivers/net/pfe/Makefile | 31 -- drivers/net/qede/Makefile | 109 ---- drivers/net/ring/Makefile | 29 - drivers/net/sfc/Makefile | 133 ----- drivers/net/softnic/Makefile | 54 -- drivers/net/szedata2/Makefile | 30 -- drivers/net/tap/Makefile | 97 ---- drivers/net/thunderx/Makefile | 41 -- drivers/net/vdev_netvsc/Makefile | 30 -- drivers/net/vhost/Makefile | 31 -- drivers/net/virtio/Makefile | 82 --- drivers/net/vmxnet3/Makefile | 53 -- drivers/raw/Makefile | 18 - drivers/raw/dpaa2_cmdif/Makefile | 35 -- drivers/raw/dpaa2_qdma/Makefile | 36 -- drivers/raw/ifpga/Makefile | 39 -- drivers/raw/ifpga/base/Makefile | 32 -- drivers/raw/ioat/Makefile | 28 - drivers/raw/ntb/Makefile | 28 - drivers/raw/octeontx2_dma/Makefile | 34 -- drivers/raw/octeontx2_ep/Makefile | 42 -- drivers/raw/skeleton/Makefile | 26 - drivers/regex/Makefile | 8 - drivers/regex/mlx5/Makefile | 41 -- drivers/vdpa/Makefile | 12 - drivers/vdpa/ifc/Makefile | 33 -- drivers/vdpa/mlx5/Makefile | 58 -- examples/Makefile | 90 ---- kernel/Makefile | 9 - kernel/freebsd/Makefile | 9 - kernel/freebsd/contigmem/Makefile | 24 - kernel/freebsd/nic_uio/Makefile | 24 - kernel/linux/Makefile | 9 - kernel/linux/igb_uio/Makefile | 25 - kernel/linux/kni/Makefile | 34 -- lib/Makefile | 138 ----- lib/librte_acl/Makefile | 65 --- lib/librte_bbdev/Makefile | 25 - lib/librte_bitratestats/Makefile | 20 - lib/librte_bpf/Makefile | 40 -- lib/librte_cfgfile/Makefile | 26 - lib/librte_cmdline/Makefile | 34 -- lib/librte_compressdev/Makefile | 27 - lib/librte_cryptodev/Makefile | 30 -- lib/librte_distributor/Makefile | 28 - lib/librte_eal/Makefile | 12 - lib/librte_eal/freebsd/Makefile | 104 ---- lib/librte_eal/include/Makefile | 19 - lib/librte_eal/linux/Makefile | 112 ---- lib/librte_efd/Makefile | 21 - lib/librte_ethdev/Makefile | 46 -- lib/librte_eventdev/Makefile | 47 -- lib/librte_fib/Makefile | 22 - lib/librte_flow_classify/Makefile | 23 - lib/librte_graph/Makefile | 28 - lib/librte_gro/Makefile | 23 - lib/librte_gso/Makefile | 25 - lib/librte_hash/Makefile | 31 -- lib/librte_ip_frag/Makefile | 27 - lib/librte_ipsec/Makefile | 29 - lib/librte_jobstats/Makefile | 21 - lib/librte_kni/Makefile | 20 - lib/librte_kvargs/Makefile | 21 - lib/librte_latencystats/Makefile | 22 - lib/librte_lpm/Makefile | 29 - lib/librte_mbuf/Makefile | 26 - lib/librte_member/Makefile | 22 - lib/librte_mempool/Makefile | 24 - lib/librte_meter/Makefile | 27 - lib/librte_metrics/Makefile | 30 -- lib/librte_net/Makefile | 25 - lib/librte_node/Makefile | 33 -- lib/librte_pci/Makefile | 19 - lib/librte_pdump/Makefile | 20 - lib/librte_pipeline/Makefile | 28 - lib/librte_port/Makefile | 59 -- lib/librte_power/Makefile | 24 - lib/librte_rawdev/Makefile | 24 - lib/librte_rcu/Makefile | 20 - lib/librte_regexdev/Makefile | 32 -- lib/librte_reorder/Makefile | 21 - lib/librte_rib/Makefile | 22 - lib/librte_ring/Makefile | 30 -- lib/librte_sched/Makefile | 29 - lib/librte_security/Makefile | 24 - lib/librte_stack/Makefile | 27 - lib/librte_table/Makefile | 59 -- lib/librte_telemetry/Makefile | 30 -- lib/librte_timer/Makefile | 20 - lib/librte_vhost/Makefile | 54 -- mk/arch/arm/rte.vars.mk | 16 - mk/arch/arm64/rte.vars.mk | 37 -- mk/arch/i686/rte.vars.mk | 36 -- mk/arch/ppc_64/rte.vars.mk | 17 - mk/arch/x86_64/rte.vars.mk | 36 -- mk/arch/x86_x32/rte.vars.mk | 40 -- mk/exec-env/bsdapp | 1 - mk/exec-env/freebsd/rte.app.mk | 8 - mk/exec-env/freebsd/rte.vars.mk | 36 -- mk/exec-env/linux/rte.app.mk | 8 - mk/exec-env/linux/rte.vars.mk | 44 -- mk/exec-env/linuxapp | 1 - mk/internal/rte.build-post.mk | 34 -- mk/internal/rte.build-pre.mk | 7 - mk/internal/rte.clean-post.mk | 34 -- mk/internal/rte.clean-pre.mk | 4 - mk/internal/rte.compile-post.mk | 5 - mk/internal/rte.compile-pre.mk | 164 ------ mk/internal/rte.extvars.mk | 55 -- mk/internal/rte.install-post.mk | 71 --- mk/internal/rte.install-pre.mk | 32 -- mk/machine/armv7a/rte.vars.mk | 36 -- mk/machine/armv8a/rte.vars.mk | 31 -- mk/machine/default/rte.vars.mk | 30 -- mk/machine/dpaa/rte.vars.mk | 37 -- mk/machine/emag/rte.vars.mk | 32 -- mk/machine/hsw/rte.vars.mk | 30 -- mk/machine/ivb/rte.vars.mk | 30 -- mk/machine/n1sdp/rte.vars.mk | 34 -- mk/machine/native/rte.vars.mk | 39 -- mk/machine/nhm/rte.vars.mk | 30 -- mk/machine/octeontx2/rte.vars.mk | 34 -- mk/machine/power8/rte.vars.mk | 30 -- mk/machine/silvermont/rte.vars.mk | 30 -- mk/machine/snb/rte.vars.mk | 30 -- mk/machine/thunderx/rte.vars.mk | 31 -- mk/machine/thunderx2/rte.vars.mk | 34 -- mk/machine/wsm/rte.vars.mk | 30 -- mk/machine/xgene1/rte.vars.mk | 31 -- mk/rte.app.mk | 509 ------------------ mk/rte.bsdmodule.mk | 89 --- mk/rte.combinedlib.mk | 30 -- mk/rte.cpuflags.mk | 124 ----- mk/rte.extapp.mk | 24 - mk/rte.extlib.mk | 26 - mk/rte.extobj.mk | 24 - mk/rte.extshared.mk | 26 - mk/rte.extsubdir.mk | 39 -- mk/rte.gnuconfigure.mk | 44 -- mk/rte.helper.mk | 10 - mk/rte.hostapp.mk | 93 ---- mk/rte.hostlib.mk | 86 --- mk/rte.install.mk | 28 - mk/rte.lib.mk | 156 ------ mk/rte.module.mk | 86 --- mk/rte.obj.mk | 82 --- mk/rte.sdkbuild.mk | 77 --- mk/rte.sdkconfig.mk | 142 ----- mk/rte.sdkdepdirs.mk | 9 - mk/rte.sdkdoc.mk | 104 ---- mk/rte.sdkexamples.mk | 50 -- mk/rte.sdkgcov.mk | 39 -- mk/rte.sdkinstall.mk | 152 ------ mk/rte.sdkroot.mk | 115 ---- mk/rte.sdktest.mk | 76 --- mk/rte.shared.mk | 108 ---- mk/rte.subdir.mk | 65 --- mk/rte.vars.mk | 102 ---- mk/target/generic/rte.app.mk | 13 - mk/target/generic/rte.vars.mk | 132 ----- mk/toolchain/clang/rte.toolchain-compat.mk | 22 - mk/toolchain/clang/rte.vars.mk | 60 --- mk/toolchain/gcc/rte.toolchain-compat.mk | 120 ----- mk/toolchain/gcc/rte.vars.mk | 109 ---- mk/toolchain/icc/rte.toolchain-compat.mk | 58 -- mk/toolchain/icc/rte.vars.mk | 62 --- 316 files changed, 26 insertions(+), 14324 deletions(-) delete mode 100644 GNUmakefile delete mode 100644 app/Makefile delete mode 100644 app/pdump/Makefile delete mode 100644 app/proc-info/Makefile delete mode 100644 app/test-acl/Makefile delete mode 100644 app/test-bbdev/Makefile delete mode 100644 app/test-cmdline/Makefile delete mode 100644 app/test-compress-perf/Makefile delete mode 100644 app/test-crypto-perf/Makefile delete mode 100644 app/test-eventdev/Makefile delete mode 100644 app/test-fib/Makefile delete mode 100644 app/test-flow-perf/Makefile delete mode 100644 app/test-pipeline/Makefile delete mode 100644 app/test-pmd/Makefile delete mode 100644 app/test-regex/Makefile delete mode 100644 app/test-sad/Makefile delete mode 100644 app/test/Makefile delete mode 100644 buildtools/Makefile delete mode 100644 buildtools/pmdinfogen/Makefile delete mode 100755 devtools/test-build.sh delete mode 100644 doc/build-sdk-quick.txt delete mode 100644 doc/guides/prog_guide/dev_kit_build_system.rst delete mode 100644 doc/guides/prog_guide/dev_kit_root_make_help.rst delete mode 100644 doc/guides/prog_guide/ext_app_lib_make_help.rst delete mode 100644 drivers/Makefile delete mode 100644 drivers/baseband/Makefile delete mode 100644 drivers/baseband/fpga_5gnr_fec/Makefile delete mode 100644 drivers/baseband/fpga_lte_fec/Makefile delete mode 100644 drivers/baseband/null/Makefile delete mode 100644 drivers/baseband/turbo_sw/Makefile delete mode 100644 drivers/bus/Makefile delete mode 100644 drivers/bus/dpaa/Makefile delete mode 100644 drivers/bus/fslmc/Makefile delete mode 100644 drivers/bus/ifpga/Makefile delete mode 100644 drivers/bus/pci/Makefile delete mode 100644 drivers/bus/pci/bsd/Makefile delete mode 100644 drivers/bus/pci/linux/Makefile delete mode 100644 drivers/bus/vdev/Makefile delete mode 100644 drivers/bus/vmbus/Makefile delete mode 100644 drivers/bus/vmbus/linux/Makefile delete mode 100644 drivers/common/Makefile delete mode 100644 drivers/common/cpt/Makefile delete mode 100644 drivers/common/dpaax/Makefile delete mode 100644 drivers/common/iavf/Makefile delete mode 100644 drivers/common/mlx5/Makefile delete mode 100644 drivers/common/mvep/Makefile delete mode 100644 drivers/common/octeontx/Makefile delete mode 100644 drivers/common/octeontx2/Makefile delete mode 100644 drivers/common/qat/Makefile delete mode 100644 drivers/compress/Makefile delete mode 100644 drivers/compress/isal/Makefile delete mode 100644 drivers/compress/octeontx/Makefile delete mode 100644 drivers/compress/zlib/Makefile delete mode 100644 drivers/crypto/Makefile delete mode 100644 drivers/crypto/aesni_gcm/Makefile delete mode 100644 drivers/crypto/aesni_mb/Makefile delete mode 100644 drivers/crypto/armv8/Makefile delete mode 100644 drivers/crypto/caam_jr/Makefile delete mode 100644 drivers/crypto/ccp/Makefile delete mode 100644 drivers/crypto/dpaa2_sec/Makefile delete mode 100644 drivers/crypto/dpaa_sec/Makefile delete mode 100644 drivers/crypto/kasumi/Makefile delete mode 100644 drivers/crypto/mvsam/Makefile delete mode 100644 drivers/crypto/nitrox/Makefile delete mode 100644 drivers/crypto/null/Makefile delete mode 100644 drivers/crypto/octeontx/Makefile delete mode 100644 drivers/crypto/octeontx2/Makefile delete mode 100644 drivers/crypto/openssl/Makefile delete mode 100644 drivers/crypto/scheduler/Makefile delete mode 100644 drivers/crypto/snow3g/Makefile delete mode 100644 drivers/crypto/virtio/Makefile delete mode 100644 drivers/crypto/zuc/Makefile delete mode 100644 drivers/event/Makefile delete mode 100644 drivers/event/dpaa/Makefile delete mode 100644 drivers/event/dpaa2/Makefile delete mode 100644 drivers/event/dsw/Makefile delete mode 100644 drivers/event/octeontx/Makefile delete mode 100644 drivers/event/octeontx2/Makefile delete mode 100644 drivers/event/opdl/Makefile delete mode 100644 drivers/event/skeleton/Makefile delete mode 100644 drivers/event/sw/Makefile delete mode 100644 drivers/mempool/Makefile delete mode 100644 drivers/mempool/bucket/Makefile delete mode 100644 drivers/mempool/dpaa/Makefile delete mode 100644 drivers/mempool/dpaa2/Makefile delete mode 100644 drivers/mempool/octeontx/Makefile delete mode 100644 drivers/mempool/octeontx2/Makefile delete mode 100644 drivers/mempool/ring/Makefile delete mode 100644 drivers/mempool/stack/Makefile delete mode 100644 drivers/net/Makefile delete mode 100644 drivers/net/af_packet/Makefile delete mode 100644 drivers/net/af_xdp/Makefile delete mode 100644 drivers/net/ark/Makefile delete mode 100644 drivers/net/atlantic/Makefile delete mode 100644 drivers/net/avp/Makefile delete mode 100644 drivers/net/axgbe/Makefile delete mode 100644 drivers/net/bnx2x/Makefile delete mode 100644 drivers/net/bnxt/Makefile delete mode 100644 drivers/net/bnxt/hcapi/Makefile delete mode 100644 drivers/net/bnxt/tf_core/Makefile delete mode 100644 drivers/net/bnxt/tf_ulp/Makefile delete mode 100644 drivers/net/bonding/Makefile delete mode 100644 drivers/net/cxgbe/Makefile delete mode 100644 drivers/net/dpaa/Makefile delete mode 100644 drivers/net/dpaa2/Makefile delete mode 100644 drivers/net/e1000/Makefile delete mode 100644 drivers/net/ena/Makefile delete mode 100644 drivers/net/enetc/Makefile delete mode 100644 drivers/net/enic/Makefile delete mode 100644 drivers/net/failsafe/Makefile delete mode 100644 drivers/net/fm10k/Makefile delete mode 100644 drivers/net/hinic/Makefile delete mode 100644 drivers/net/hns3/Makefile delete mode 100644 drivers/net/i40e/Makefile delete mode 100644 drivers/net/iavf/Makefile delete mode 100644 drivers/net/ice/Makefile delete mode 100644 drivers/net/igc/Makefile delete mode 100644 drivers/net/ionic/Makefile delete mode 100644 drivers/net/ipn3ke/Makefile delete mode 100644 drivers/net/ixgbe/Makefile delete mode 100644 drivers/net/kni/Makefile delete mode 100644 drivers/net/liquidio/Makefile delete mode 100644 drivers/net/memif/Makefile delete mode 100644 drivers/net/mlx4/Makefile delete mode 100644 drivers/net/mlx5/Makefile delete mode 100644 drivers/net/mvneta/Makefile delete mode 100644 drivers/net/mvpp2/Makefile delete mode 100644 drivers/net/netvsc/Makefile delete mode 100644 drivers/net/nfb/Makefile delete mode 100644 drivers/net/nfp/Makefile delete mode 100644 drivers/net/null/Makefile delete mode 100644 drivers/net/octeontx/Makefile delete mode 100644 drivers/net/octeontx2/Makefile delete mode 100644 drivers/net/pcap/Makefile delete mode 100644 drivers/net/pfe/Makefile delete mode 100644 drivers/net/qede/Makefile delete mode 100644 drivers/net/ring/Makefile delete mode 100644 drivers/net/sfc/Makefile delete mode 100644 drivers/net/softnic/Makefile delete mode 100644 drivers/net/szedata2/Makefile delete mode 100644 drivers/net/tap/Makefile delete mode 100644 drivers/net/thunderx/Makefile delete mode 100644 drivers/net/vdev_netvsc/Makefile delete mode 100644 drivers/net/vhost/Makefile delete mode 100644 drivers/net/virtio/Makefile delete mode 100644 drivers/net/vmxnet3/Makefile delete mode 100644 drivers/raw/Makefile delete mode 100644 drivers/raw/dpaa2_cmdif/Makefile delete mode 100644 drivers/raw/dpaa2_qdma/Makefile delete mode 100644 drivers/raw/ifpga/Makefile delete mode 100644 drivers/raw/ifpga/base/Makefile delete mode 100644 drivers/raw/ioat/Makefile delete mode 100644 drivers/raw/ntb/Makefile delete mode 100644 drivers/raw/octeontx2_dma/Makefile delete mode 100644 drivers/raw/octeontx2_ep/Makefile delete mode 100644 drivers/raw/skeleton/Makefile delete mode 100644 drivers/regex/Makefile delete mode 100644 drivers/regex/mlx5/Makefile delete mode 100644 drivers/vdpa/Makefile delete mode 100644 drivers/vdpa/ifc/Makefile delete mode 100644 drivers/vdpa/mlx5/Makefile delete mode 100644 examples/Makefile delete mode 100644 kernel/Makefile delete mode 100644 kernel/freebsd/Makefile delete mode 100644 kernel/freebsd/contigmem/Makefile delete mode 100644 kernel/freebsd/nic_uio/Makefile delete mode 100644 kernel/linux/Makefile delete mode 100644 kernel/linux/igb_uio/Makefile delete mode 100644 kernel/linux/kni/Makefile delete mode 100644 lib/Makefile delete mode 100644 lib/librte_acl/Makefile delete mode 100644 lib/librte_bbdev/Makefile delete mode 100644 lib/librte_bitratestats/Makefile delete mode 100644 lib/librte_bpf/Makefile delete mode 100644 lib/librte_cfgfile/Makefile delete mode 100644 lib/librte_cmdline/Makefile delete mode 100644 lib/librte_compressdev/Makefile delete mode 100644 lib/librte_cryptodev/Makefile delete mode 100644 lib/librte_distributor/Makefile delete mode 100644 lib/librte_eal/Makefile delete mode 100644 lib/librte_eal/freebsd/Makefile delete mode 100644 lib/librte_eal/include/Makefile delete mode 100644 lib/librte_eal/linux/Makefile delete mode 100644 lib/librte_efd/Makefile delete mode 100644 lib/librte_ethdev/Makefile delete mode 100644 lib/librte_eventdev/Makefile delete mode 100644 lib/librte_fib/Makefile delete mode 100644 lib/librte_flow_classify/Makefile delete mode 100644 lib/librte_graph/Makefile delete mode 100644 lib/librte_gro/Makefile delete mode 100644 lib/librte_gso/Makefile delete mode 100644 lib/librte_hash/Makefile delete mode 100644 lib/librte_ip_frag/Makefile delete mode 100644 lib/librte_ipsec/Makefile delete mode 100644 lib/librte_jobstats/Makefile delete mode 100644 lib/librte_kni/Makefile delete mode 100644 lib/librte_kvargs/Makefile delete mode 100644 lib/librte_latencystats/Makefile delete mode 100644 lib/librte_lpm/Makefile delete mode 100644 lib/librte_mbuf/Makefile delete mode 100644 lib/librte_member/Makefile delete mode 100644 lib/librte_mempool/Makefile delete mode 100644 lib/librte_meter/Makefile delete mode 100644 lib/librte_metrics/Makefile delete mode 100644 lib/librte_net/Makefile delete mode 100644 lib/librte_node/Makefile delete mode 100644 lib/librte_pci/Makefile delete mode 100644 lib/librte_pdump/Makefile delete mode 100644 lib/librte_pipeline/Makefile delete mode 100644 lib/librte_port/Makefile delete mode 100644 lib/librte_power/Makefile delete mode 100644 lib/librte_rawdev/Makefile delete mode 100644 lib/librte_rcu/Makefile delete mode 100644 lib/librte_regexdev/Makefile delete mode 100644 lib/librte_reorder/Makefile delete mode 100644 lib/librte_rib/Makefile delete mode 100644 lib/librte_ring/Makefile delete mode 100644 lib/librte_sched/Makefile delete mode 100644 lib/librte_security/Makefile delete mode 100644 lib/librte_stack/Makefile delete mode 100644 lib/librte_table/Makefile delete mode 100644 lib/librte_telemetry/Makefile delete mode 100644 lib/librte_timer/Makefile delete mode 100644 lib/librte_vhost/Makefile delete mode 100644 mk/arch/arm/rte.vars.mk delete mode 100644 mk/arch/arm64/rte.vars.mk delete mode 100644 mk/arch/i686/rte.vars.mk delete mode 100644 mk/arch/ppc_64/rte.vars.mk delete mode 100644 mk/arch/x86_64/rte.vars.mk delete mode 100644 mk/arch/x86_x32/rte.vars.mk delete mode 120000 mk/exec-env/bsdapp delete mode 100644 mk/exec-env/freebsd/rte.app.mk delete mode 100644 mk/exec-env/freebsd/rte.vars.mk delete mode 100644 mk/exec-env/linux/rte.app.mk delete mode 100644 mk/exec-env/linux/rte.vars.mk delete mode 120000 mk/exec-env/linuxapp delete mode 100644 mk/internal/rte.build-post.mk delete mode 100644 mk/internal/rte.build-pre.mk delete mode 100644 mk/internal/rte.clean-post.mk delete mode 100644 mk/internal/rte.clean-pre.mk delete mode 100644 mk/internal/rte.compile-post.mk delete mode 100644 mk/internal/rte.compile-pre.mk delete mode 100644 mk/internal/rte.extvars.mk delete mode 100644 mk/internal/rte.install-post.mk delete mode 100644 mk/internal/rte.install-pre.mk delete mode 100644 mk/machine/armv7a/rte.vars.mk delete mode 100644 mk/machine/armv8a/rte.vars.mk delete mode 100644 mk/machine/default/rte.vars.mk delete mode 100644 mk/machine/dpaa/rte.vars.mk delete mode 100644 mk/machine/emag/rte.vars.mk delete mode 100644 mk/machine/hsw/rte.vars.mk delete mode 100644 mk/machine/ivb/rte.vars.mk delete mode 100644 mk/machine/n1sdp/rte.vars.mk delete mode 100644 mk/machine/native/rte.vars.mk delete mode 100644 mk/machine/nhm/rte.vars.mk delete mode 100644 mk/machine/octeontx2/rte.vars.mk delete mode 100644 mk/machine/power8/rte.vars.mk delete mode 100644 mk/machine/silvermont/rte.vars.mk delete mode 100644 mk/machine/snb/rte.vars.mk delete mode 100644 mk/machine/thunderx/rte.vars.mk delete mode 100644 mk/machine/thunderx2/rte.vars.mk delete mode 100644 mk/machine/wsm/rte.vars.mk delete mode 100644 mk/machine/xgene1/rte.vars.mk delete mode 100644 mk/rte.app.mk delete mode 100644 mk/rte.bsdmodule.mk delete mode 100644 mk/rte.combinedlib.mk delete mode 100644 mk/rte.cpuflags.mk delete mode 100644 mk/rte.extapp.mk delete mode 100644 mk/rte.extlib.mk delete mode 100644 mk/rte.extobj.mk delete mode 100644 mk/rte.extshared.mk delete mode 100644 mk/rte.extsubdir.mk delete mode 100644 mk/rte.gnuconfigure.mk delete mode 100644 mk/rte.helper.mk delete mode 100644 mk/rte.hostapp.mk delete mode 100644 mk/rte.hostlib.mk delete mode 100644 mk/rte.install.mk delete mode 100644 mk/rte.lib.mk delete mode 100644 mk/rte.module.mk delete mode 100644 mk/rte.obj.mk delete mode 100644 mk/rte.sdkbuild.mk delete mode 100644 mk/rte.sdkconfig.mk delete mode 100644 mk/rte.sdkdepdirs.mk delete mode 100644 mk/rte.sdkdoc.mk delete mode 100644 mk/rte.sdkexamples.mk delete mode 100644 mk/rte.sdkgcov.mk delete mode 100644 mk/rte.sdkinstall.mk delete mode 100644 mk/rte.sdkroot.mk delete mode 100644 mk/rte.sdktest.mk delete mode 100644 mk/rte.shared.mk delete mode 100644 mk/rte.subdir.mk delete mode 100644 mk/rte.vars.mk delete mode 100644 mk/target/generic/rte.app.mk delete mode 100644 mk/target/generic/rte.vars.mk delete mode 100644 mk/toolchain/clang/rte.toolchain-compat.mk delete mode 100644 mk/toolchain/clang/rte.vars.mk delete mode 100644 mk/toolchain/gcc/rte.toolchain-compat.mk delete mode 100644 mk/toolchain/gcc/rte.vars.mk delete mode 100644 mk/toolchain/icc/rte.toolchain-compat.mk delete mode 100644 mk/toolchain/icc/rte.vars.mk
GNUmakefile deleted +0 -17
@@ -1,17 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2015 Intel Corporation - -# -# Head Makefile for compiling rte SDK -# - -RTE_SDK := $(CURDIR) -export RTE_SDK - -# -# directory list -# - -ROOTDIRS-y := buildtools lib kernel drivers app - -include $(RTE_SDK)/mk/rte.sdkroot.mk
MAINTAINERS +1 -10
@@ -90,8 +90,6 @@ F: devtools/checkpatches.sh F: devtools/get-maintainer.sh F: devtools/git-log-fixes.sh F: devtools/load-devel-config -F: devtools/test-build.sh -F: devtools/test-meson-builds.sh F: devtools/words-case.txt F: license/ F: .editorconfig
@@ -100,18 +98,12 @@ F: .editorconfig Build System ------------ M: Thomas Monjalon <[email protected]> -F: GNUmakefile F: Makefile F: config/ -F: mk/ F: buildtools/auto-config-h.sh F: buildtools/gen-build-mk.sh F: buildtools/gen-config-h.sh F: buildtools/relpath.sh -F: doc/build-sdk-quick.txt -F: doc/guides/prog_guide/build_app.rst -F: doc/guides/prog_guide/dev_kit_* -F: doc/guides/prog_guide/ext_app_lib_make_help.rst Meson build M: Bruce Richardson <[email protected]>
@@ -124,6 +116,7 @@ F: buildtools/gen-pmdinfo-cfile.sh F: buildtools/list-dir-globs.py F: buildtools/pkg-config/ F: buildtools/symlink-drivers-solibs.sh +F: devtools/test-meson-builds.sh Public CI M: Aaron Conole <[email protected]>
@@ -354,7 +347,6 @@ Memory pool M: Olivier Matz <[email protected]> M: Andrew Rybchenko <[email protected]> F: lib/librte_mempool/ -F: drivers/mempool/Makefile F: drivers/mempool/ring/ F: doc/guides/prog_guide/mempool_lib.rst F: app/test/test_mempool*
@@ -1519,7 +1511,6 @@ Test Applications ----------------- Unit tests framework -F: app/test/Makefile F: app/test/autotest* F: app/test/commands.c F: app/test/get-coremask.sh
app/Makefile deleted +0 -34
@@ -1,34 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -DIRS-$(CONFIG_RTE_APP_TEST) += test -DIRS-$(CONFIG_RTE_TEST_PMD) += test-pmd -DIRS-$(CONFIG_RTE_PROC_INFO) += proc-info -DIRS-$(CONFIG_RTE_LIBRTE_PDUMP) += pdump -DIRS-$(CONFIG_RTE_LIBRTE_ACL) += test-acl -DIRS-$(CONFIG_RTE_LIBRTE_CMDLINE) += test-cmdline -DIRS-$(CONFIG_RTE_LIBRTE_FIB) += test-fib -DIRS-$(CONFIG_RTE_TEST_FLOW_PERF) += test-flow-perf -DIRS-$(CONFIG_RTE_LIBRTE_PIPELINE) += test-pipeline -DIRS-$(CONFIG_RTE_LIBRTE_IPSEC) += test-sad -DIRS-$(CONFIG_RTE_LIBRTE_REGEXDEV) += test-regex - -ifeq ($(CONFIG_RTE_LIBRTE_BBDEV),y) -DIRS-$(CONFIG_RTE_TEST_BBDEV) += test-bbdev -endif - -ifeq ($(CONFIG_RTE_LIBRTE_COMPRESSDEV),y) -DIRS-$(CONFIG_RTE_APP_COMPRESS_PERF) += test-compress-perf -endif - -ifeq ($(CONFIG_RTE_LIBRTE_CRYPTODEV),y) -DIRS-$(CONFIG_RTE_APP_CRYPTO_PERF) += test-crypto-perf -endif - -ifeq ($(CONFIG_RTE_LIBRTE_EVENTDEV),y) -DIRS-$(CONFIG_RTE_APP_EVENTDEV) += test-eventdev -endif - -include $(RTE_SDK)/mk/rte.subdir.mk
app/pdump/Makefile deleted +0 -18
@@ -1,18 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2016 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -ifeq ($(CONFIG_RTE_LIBRTE_PDUMP),y) - -APP = dpdk-pdump - -CFLAGS += $(WERROR_FLAGS) - -# all source are stored in SRCS-y - -SRCS-y := main.c - -include $(RTE_SDK)/mk/rte.app.mk - -endif
app/proc-info/Makefile deleted +0 -14
@@ -1,14 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2015 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -APP = dpdk-procinfo - -CFLAGS += $(WERROR_FLAGS) - -# all source are stored in SRCS-y - -SRCS-y := main.c - -include $(RTE_SDK)/mk/rte.app.mk
app/test-acl/Makefile deleted +0 -17
@@ -1,17 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -ifeq ($(CONFIG_RTE_LIBRTE_ACL),y) - -APP = testacl - -CFLAGS += $(WERROR_FLAGS) - -# all source are stored in SRCS-y -SRCS-y := main.c - -include $(RTE_SDK)/mk/rte.app.mk - -endif
app/test-bbdev/Makefile deleted +0 -30
@@ -1,30 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2017 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -# -# library name -# -APP = testbbdev - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) - -# -# all sources are stored in SRCS-y -# -SRCS-$(CONFIG_RTE_TEST_BBDEV) += main.c -SRCS-$(CONFIG_RTE_TEST_BBDEV) += test_bbdev.c -SRCS-$(CONFIG_RTE_TEST_BBDEV) += test_bbdev_perf.c -SRCS-$(CONFIG_RTE_TEST_BBDEV) += test_bbdev_vector.c - -LDLIBS += -lm -ifeq ($(CONFIG_RTE_LIBRTE_PMD_BBDEV_FPGA_LTE_FEC),y) -LDLIBS += -lrte_pmd_bbdev_fpga_lte_fec -endif -ifeq ($(CONFIG_RTE_LIBRTE_PMD_BBDEV_FPGA_5GNR_FEC),y) -LDLIBS += -lrte_pmd_bbdev_fpga_5gnr_fec -endif - -include $(RTE_SDK)/mk/rte.app.mk
app/test-cmdline/Makefile deleted +0 -24
@@ -1,24 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -ifeq ($(CONFIG_RTE_LIBRTE_CMDLINE),y) - -# -# library name -# -APP = cmdline_test - -# -# all sources are stored in SRCS-y -# -SRCS-y += cmdline_test.c -SRCS-y += commands.c - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) - -include $(RTE_SDK)/mk/rte.app.mk - -endif
app/test-compress-perf/Makefile deleted +0 -19
@@ -1,19 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2018 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -APP = dpdk-test-compress-perf - -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -O3 - -# all source are stored in SRCS-y -SRCS-y := main.c -SRCS-y += comp_perf_options_parse.c -SRCS-y += comp_perf_test_verify.c -SRCS-y += comp_perf_test_throughput.c -SRCS-y += comp_perf_test_cyclecount.c -SRCS-y += comp_perf_test_common.c - -include $(RTE_SDK)/mk/rte.app.mk
app/test-crypto-perf/Makefile deleted +0 -28
@@ -1,28 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2016-2017 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - - -APP = dpdk-test-crypto-perf - -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -O3 - -# all source are stored in SRCS-y -SRCS-y := main.c -SRCS-y += cperf_ops.c -SRCS-y += cperf_options_parsing.c -SRCS-y += cperf_test_vectors.c -SRCS-y += cperf_test_throughput.c -SRCS-y += cperf_test_latency.c -SRCS-y += cperf_test_pmd_cyclecount.c -SRCS-y += cperf_test_verify.c -SRCS-y += cperf_test_vector_parsing.c -SRCS-y += cperf_test_common.c - -ifeq ($(CONFIG_RTE_LIBRTE_PMD_CRYPTO_SCHEDULER),y) -LDLIBS += -lrte_pmd_crypto_scheduler -endif - -include $(RTE_SDK)/mk/rte.app.mk
app/test-eventdev/Makefile deleted +0 -32
@@ -1,32 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2017 Cavium, Inc -# - -include $(RTE_SDK)/mk/rte.vars.mk - -APP = dpdk-test-eventdev - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) - -# -# all source are stored in SRCS-y -# -SRCS-y := evt_main.c -SRCS-y += evt_options.c -SRCS-y += evt_test.c -SRCS-y += parser.c - -SRCS-y += test_order_common.c -SRCS-y += test_order_queue.c -SRCS-y += test_order_atq.c - -SRCS-y += test_perf_common.c -SRCS-y += test_perf_queue.c -SRCS-y += test_perf_atq.c - -SRCS-y += test_pipeline_common.c -SRCS-y += test_pipeline_queue.c -SRCS-y += test_pipeline_atq.c - -include $(RTE_SDK)/mk/rte.app.mk
app/test-fib/Makefile deleted +0 -18
@@ -1,18 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -ifeq ($(CONFIG_RTE_LIBRTE_FIB),y) - -APP = testfib - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) - -# all source are stored in SRCS-y -SRCS-y := main.c - -include $(RTE_SDK)/mk/rte.app.mk - -endif
app/test-flow-perf/Makefile deleted +0 -26
@@ -1,26 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright 2020 Mellanox Technologies, Ltd - -include $(RTE_SDK)/mk/rte.vars.mk - -ifeq ($(CONFIG_RTE_TEST_FLOW_PERF),y) - -# -# library name -# -APP = dpdk-test-flow-perf - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) - -# -# all source are stored in SRCS-y -# -SRCS-y += actions_gen.c -SRCS-y += flow_gen.c -SRCS-y += items_gen.c -SRCS-y += main.c - -include $(RTE_SDK)/mk/rte.app.mk - -endif
app/test-pipeline/Makefile deleted +0 -33
@@ -1,33 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2015 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -ifeq ($(CONFIG_RTE_LIBRTE_PIPELINE),y) - -# -# library name -# -APP = testpipeline - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) - -# -# all source are stored in SRCS-y -# -SRCS-y := main.c -SRCS-y += config.c -SRCS-y += init.c -SRCS-y += runtime.c -SRCS-y += pipeline_stub.c -SRCS-y += pipeline_hash.c -SRCS-y += pipeline_lpm.c -SRCS-y += pipeline_lpm_ipv6.c - -# include ACL lib if available -SRCS-$(CONFIG_RTE_LIBRTE_ACL) += pipeline_acl.c - -include $(RTE_SDK)/mk/rte.app.mk - -endif
app/test-pmd/Makefile deleted +0 -73
73 lines not on this page · raw message
app/test-regex/Makefile deleted +0 -13
@@ -1,13 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright 2020 Mellanox Technologies, Ltd - -include $(RTE_SDK)/mk/rte.vars.mk - -APP = dpdk-test-regex - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) - -SRCS-y := main.c - -include $(RTE_SDK)/mk/rte.app.mk
app/test-sad/Makefile deleted +0 -17
@@ -1,17 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -ifeq ($(CONFIG_RTE_LIBRTE_IPSEC),y) - -APP = testsad - -CFLAGS += $(WERROR_FLAGS) - -# all source are stored in SRCS-y -SRCS-y := main.c - -include $(RTE_SDK)/mk/rte.app.mk - -endif
app/test/Makefile deleted +0 -310
310 lines not on this page · raw message
buildtools/Makefile deleted +0 -9
@@ -1,9 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2016 Neil Horman <[email protected]> -# All rights reserved. - -include $(RTE_SDK)/mk/rte.vars.mk - -DIRS-y += pmdinfogen - -include $(RTE_SDK)/mk/rte.subdir.mk
buildtools/pmdinfogen/Makefile deleted +0 -20
@@ -1,20 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2016 Neil Horman <[email protected]> -# All rights reserved. - -include $(RTE_SDK)/mk/rte.vars.mk - -# -# library name -# -HOSTAPP = dpdk-pmdinfogen - -# -# all sources are stored in SRCS-y -# -SRCS-y += pmdinfogen.c - -HOST_CFLAGS += $(HOST_WERROR_FLAGS) -g -HOST_CFLAGS += -I$(RTE_OUTPUT)/include - -include $(RTE_SDK)/mk/rte.hostapp.mk
devtools/git-log-fixes.sh +1 -1
@@ -50,7 +50,7 @@ commit_version () # <hash> head -n1) if [ -z "$tag" ] ; then # before -rc1 tag of release in progress - make showversion | cut -d'.' -f-2 + cat VERSION | cut -d'.' -f-2 else echo $tag | sed 's,^v,,' | sed 's,-rc.*,,' fi
devtools/test-build.sh deleted +0 -315
315 lines not on this page · raw message
doc/build-sdk-quick.txt deleted +0 -34
@@ -1,34 +0,0 @@ -Basic build - make defconfig && make - or - make config T=x86_64-native-linux-gcc && make -Build commands - config get configuration from target template (T=) - defconfig auto-select target template based on arch, OS, etc. - all same as build (default rule) - build build in a configured directory - clean remove files but keep configuration - install T= configure, build and install a target in DESTDIR - install install optionally staged in DESTDIR - examples build examples for given targets (T=) - examples_clean clean examples for given targets (T=) - test compile tests and run basic unit tests - test-* run specific subset of unit tests - tags|etags|gtags generate tags database for given targets (T=) - cscope generate cscope database for given targets (T=) -Build variables - EXTRA_CPPFLAGS preprocessor options - EXTRA_CFLAGS compiler options - EXTRA_LDFLAGS linker options - EXTRA_LDLIBS linker library options - RTE_KERNELDIR linux headers path - RTE_DEVEL_BUILD stricter options (default: y in git tree) - CROSS toolchain prefix - V verbose - D debug dependencies - O build directory (default: build/ - install T= default: ./) - DESTDIR staging install directory (default: empty) - prefix root install directory (default: /usr/local) - T target template - used with config or install - format: <arch-machine-execenv-toolchain> - templates in config/defconfig_*
doc/guides/contributing/coding_style.rst +4 -44
57 lines not on this page · raw message
doc/guides/contributing/patches.rst +0 -49
55 lines not on this page · raw message
doc/guides/freebsd_gsg/intro.rst +2 -2
@@ -39,8 +39,8 @@ The following is a list of DPDK documents in the suggested reading order: specifically in a Linux* application (linux) environment * The content of the DPDK, the build system (including the commands - that can be used in the root DPDK Makefile to build the development - kit and an application) and guidelines for porting an application + that can be used to build the development kit and an application) + and guidelines for porting an application * Optimizations used in the software and those that should be considered for new development
doc/guides/linux_gsg/build_dpdk.rst +1 -67
83 lines not on this page · raw message
doc/guides/linux_gsg/build_sample_apps.rst +1 -50
57 lines not on this page · raw message
doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst +3 -45
63 lines not on this page · raw message
doc/guides/linux_gsg/intro.rst +1 -1
@@ -23,7 +23,7 @@ The following is a list of DPDK documents in the suggested reading order: * The software architecture and how to use it (through examples), specifically in a Linux application (linux) environment - * The content of the DPDK, the build system (including the commands that can be used in the root DPDK Makefile to build the development kit and + * The content of the DPDK, the build system (including the commands that can be used to build the development kit and an application) and guidelines for porting an application * Optimizations used in the software and those that should be considered for new development
doc/guides/linux_gsg/sys_reqs.rst +3 -7
@@ -37,7 +37,7 @@ Compilation of the DPDK The setup commands and installed packages needed on various systems may be different. For details on Linux distributions and the versions tested, please consult the DPDK Release Notes. -* General development tools including ``make``, and a supported C compiler such as ``gcc`` (version 4.9+) or ``clang`` (version 3.4+). +* General development tools including a supported C compiler such as gcc (version 4.9+) or clang (version 3.4+). * For RHEL/Fedora systems these can be installed using ``dnf groupinstall "Development Tools"``
@@ -82,12 +82,8 @@ Compilation of the DPDK **Additional Libraries** A number of DPDK components, such as libraries and poll-mode drivers (PMDs) have additional dependencies. -For DPDK builds using meson, the presence or absence of these dependencies will be -automatically detected enabling or disabling the relevant components appropriately. - -For builds using make, these components are disabled in the default configuration and -need to be enabled manually by changing the relevant setting to "y" in the build configuration file -i.e. the ``.config`` file in the build folder. +For DPDK builds, the presence or absence of these dependencies will be automatically detected +enabling or disabling the relevant components appropriately. In each case, the relevant library development package (``-devel`` or ``-dev``) is needed to build the DPDK components.
doc/guides/prog_guide/build_app.rst +4 -52
89 lines not on this page · raw message
doc/guides/prog_guide/dev_kit_build_system.rst deleted +0 -331
331 lines not on this page · raw message
doc/guides/prog_guide/dev_kit_root_make_help.rst deleted +0 -188
188 lines not on this page · raw message
doc/guides/prog_guide/ext_app_lib_make_help.rst deleted +0 -98
98 lines not on this page · raw message
doc/guides/prog_guide/index.rst +0 -3
@@ -62,12 +62,9 @@ Programmer's Guide ipsec_lib graph_lib source_org - dev_kit_build_system - dev_kit_root_make_help build-sdk-meson meson_ut build_app - ext_app_lib_make_help perf_opt_guidelines writing_efficient_code lto
doc/guides/prog_guide/intro.rst +1 -1
@@ -34,7 +34,7 @@ The following is a list of DPDK documents in the suggested reading order: specifically in a Linux* application (linux) environment * The content of the DPDK, the build system - (including the commands that can be used in the root DPDK Makefile to build the development kit and an application) + (including the commands that can be used in the root DPDK to build the development kit and an application) and guidelines for porting an application * Optimizations used in the software and those that should be considered for new development
doc/guides/prog_guide/overview.rst +2 -10
@@ -18,7 +18,7 @@ The framework creates a set of libraries for specific environments through the creation of an Environment Abstraction Layer (EAL), which may be specific to a mode of the Intel® architecture (32-bit or 64-bit), Linux* user space compilers or a specific platform. -These environments are created through the use of make files and configuration files. +These environments are created through the use of meson files and configuration files. Once the EAL library is created, the user may link with the library to create their own applications. Other libraries, outside of EAL, including the Hash, Longest Prefix Match (LPM) and rings libraries are also provided.
@@ -38,21 +38,13 @@ Development Environment ----------------------- The DPDK project installation requires Linux and the associated toolchain, -such as one or more compilers, assembler, make utility, +such as one or more compilers, assembler, meson utility, editor and various libraries to create the DPDK components and libraries. Once these libraries are created for the specific environment and architecture, they may then be used to create the user's data plane application. When creating applications for the Linux user space, the glibc library is used. -For DPDK applications, two environmental variables (RTE_SDK and RTE_TARGET) -must be configured before compiling the applications. -The following are examples of how the variables can be set: - -.. code-block:: console - - export RTE_SDK=/home/user/DPDK - export RTE_TARGET=x86_64-native-linux-gcc See the *DPDK Getting Started Guide* for information on setting up the development environment.
doc/guides/prog_guide/source_org.rst +2 -21
@@ -8,29 +8,10 @@ Source Organization This section describes the organization of sources in the DPDK framework. -Makefiles and Config --------------------- - -.. note:: - - In the following descriptions, - ``RTE_SDK`` is the environment variable that points to the base directory into which the tarball was extracted. - See - :ref:`Useful_Variables_Provided_by_the_Build_System` - for descriptions of other variables. - -Makefiles that are provided by the DPDK libraries and applications are located in ``$(RTE_SDK)/mk``. - -Config templates are located in ``$(RTE_SDK)/config``. The templates describe the options that are enabled for each target. -The config file also contains items that can be enabled and disabled for many of the DPDK libraries, -including debug options. -The user should look at the config file and become familiar with these options. -The config file is also used to create a header file, which will be located in the new build directory. - Libraries --------- -Libraries are located in subdirectories of ``$(RTE_SDK)/lib``. +Libraries are located in subdirectories of ``dpdk/lib``. By convention a library refers to any code that provides an API to an application. Typically, it generates an archive file (``.a``), but a kernel module would also go in the same directory.
@@ -55,7 +36,7 @@ Applications ------------ Applications are source files that contain a ``main()`` function. -They are located in the ``$(RTE_SDK)/app`` and ``$(RTE_SDK)/examples`` directories. +They are located in the ``dpdk/app`` and ``dpdk/examples`` directories. The app directory contains sample applications that are used to test DPDK (such as autotests) or the Poll Mode Drivers (test-pmd).
doc/guides/rel_notes/deprecation.rst +0 -7
@@ -11,13 +11,6 @@ here. Deprecation Notices ------------------- -* make: Support for building DPDK with "make" has been deprecated and - support will be removed in the 20.11 release. From 20.11 onwards, DPDK - should be built using meson and ninja. For basic instructions see the - `Quick-start Guide <https://core.dpdk.org/doc/quick-start/>`_ on the - website or the `Getting Started Guide - <https://doc.dpdk.org/guides/linux_gsg/build_dpdk.html>`_ document. - * meson: The minimum supported version of meson for configuring and building DPDK will be increased to v0.47.1 (from 0.41) from DPDK 19.05 onwards. For those users with a version earlier than 0.47.1, an updated copy of meson
drivers/Makefile deleted +0 -34
@@ -1,34 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2015 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -DIRS-y += common -DIRS-y += bus -DEPDIRS-bus := common -DIRS-y += mempool -DEPDIRS-mempool := common bus -ifeq ($(findstring y,$(CONFIG_RTE_LIBRTE_MLX5_PMD)$(CONFIG_RTE_LIBRTE_MLX5_VDPA_PMD)$(CONFIG_RTE_LIBRTE_MLX5_REGEX_PMD)),y) -DIRS-y += common/mlx5 -DEPDIRS-common/mlx5 := bus -endif -DIRS-y += net -DEPDIRS-net := common bus mempool common/mlx5 -DIRS-$(CONFIG_RTE_LIBRTE_BBDEV) += baseband -DEPDIRS-baseband := common bus mempool -DIRS-$(CONFIG_RTE_LIBRTE_CRYPTODEV) += crypto -DEPDIRS-crypto := common bus mempool -DIRS-$(CONFIG_RTE_LIBRTE_PMD_QAT) += common/qat -DEPDIRS-common/qat := bus mempool -DIRS-$(CONFIG_RTE_LIBRTE_COMPRESSDEV) += compress -DEPDIRS-compress := bus mempool -DIRS-$(CONFIG_RTE_LIBRTE_REGEXDEV) += regex -DEPDIRS-regex := common bus common/mlx5 -DIRS-$(CONFIG_RTE_LIBRTE_VHOST) += vdpa -DEPDIRS-vdpa := common bus mempool common/mlx5 -DIRS-$(CONFIG_RTE_LIBRTE_EVENTDEV) += event -DEPDIRS-event := common bus mempool net crypto -DIRS-$(CONFIG_RTE_LIBRTE_RAWDEV) += raw -DEPDIRS-raw := common bus mempool net event - -include $(RTE_SDK)/mk/rte.subdir.mk
drivers/baseband/Makefile deleted +0 -18
@@ -1,18 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2017 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -core-libs := librte_eal librte_mbuf librte_mempool librte_ring -core-libs += librte_bbdev librte_kvargs librte_cfgfile - -DIRS-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_NULL) += null -DEPDIRS-null = $(core-libs) -DIRS-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_TURBO_SW) += turbo_sw -DEPDIRS-turbo_sw = $(core-libs) -DIRS-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_FPGA_LTE_FEC) += fpga_lte_fec -DEPDIRS-fpga_lte_fec = $(core-libs) -DIRS-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_FPGA_5GNR_FEC) += fpga_5gnr_fec -DEPDIRS-fpga_5gnr_fec = $(core-libs) - -include $(RTE_SDK)/mk/rte.subdir.mk
drivers/baseband/fpga_5gnr_fec/Makefile deleted +0 -28
@@ -1,28 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2019 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -# library name -LIB = librte_pmd_bbdev_fpga_5gnr_fec.a - -# build flags -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -LDLIBS += -lrte_eal -lrte_mbuf -lrte_mempool -lrte_ring -LDLIBS += -lrte_bbdev -LDLIBS += -lrte_pci -lrte_bus_pci - -# versioning export map -EXPORT_MAP := rte_pmd_bbdev_fpga_5gnr_fec_version.map - -# library version -LIBABIVER := 1 - -# library source files -SRCS-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_FPGA_5GNR_FEC) += rte_fpga_5gnr_fec.c - -# export include files -SYMLINK-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_FPGA_5GNR_FEC)-include += rte_pmd_fpga_5gnr_fec.h - -include $(RTE_SDK)/mk/rte.lib.mk
drivers/baseband/fpga_lte_fec/Makefile deleted +0 -25
@@ -1,25 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2019 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -# library name -LIB = librte_pmd_bbdev_fpga_lte_fec.a - -# build flags -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -LDLIBS += -lrte_eal -lrte_mbuf -lrte_mempool -lrte_ring -LDLIBS += -lrte_bbdev -LDLIBS += -lrte_pci -lrte_bus_pci - -# versioning export map -EXPORT_MAP := rte_pmd_bbdev_fpga_lte_fec_version.map - -# library source files -SRCS-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_FPGA_LTE_FEC) += fpga_lte_fec.c - -# export include files -SYMLINK-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_FPGA_LTE_FEC)-include += fpga_lte_fec.h - -include $(RTE_SDK)/mk/rte.lib.mk
drivers/baseband/null/Makefile deleted +0 -21
@@ -1,21 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2017 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk -# library name -LIB = librte_pmd_bbdev_null.a - -# build flags -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -LDLIBS += -lrte_eal -lrte_mbuf -lrte_mempool -lrte_ring -lrte_kvargs -LDLIBS += -lrte_bbdev -LDLIBS += -lrte_bus_vdev - -# versioning export map -EXPORT_MAP := rte_pmd_bbdev_null_version.map - -# library source files -SRCS-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_NULL) += bbdev_null.c - -include $(RTE_SDK)/mk/rte.lib.mk
drivers/baseband/turbo_sw/Makefile deleted +0 -52
52 lines not on this page · raw message
drivers/bus/Makefile deleted +0 -15
@@ -1,15 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright 2016 NXP - -include $(RTE_SDK)/mk/rte.vars.mk - -DIRS-$(CONFIG_RTE_LIBRTE_DPAA_BUS) += dpaa -ifeq ($(CONFIG_RTE_EAL_VFIO),y) -DIRS-$(CONFIG_RTE_LIBRTE_FSLMC_BUS) += fslmc -endif -DIRS-$(CONFIG_RTE_LIBRTE_IFPGA_BUS) += ifpga -DIRS-$(CONFIG_RTE_LIBRTE_PCI_BUS) += pci -DIRS-$(CONFIG_RTE_LIBRTE_VDEV_BUS) += vdev -DIRS-$(CONFIG_RTE_LIBRTE_VMBUS) += vmbus - -include $(RTE_SDK)/mk/rte.subdir.mk
drivers/bus/dpaa/Makefile deleted +0 -48
48 lines not on this page · raw message
drivers/bus/fslmc/Makefile deleted +0 -47
47 lines not on this page · raw message
drivers/bus/ifpga/Makefile deleted +0 -28
@@ -1,28 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2018 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -# -# library name -# -LIB = librte_bus_ifpga.a - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -LDLIBS += -lrte_eal -LDLIBS += -lrte_rawdev -LDLIBS += -lrte_kvargs - -# versioning export map -EXPORT_MAP := rte_bus_ifpga_version.map - -SRCS-$(CONFIG_RTE_LIBRTE_IFPGA_BUS) += ifpga_bus.c -SRCS-$(CONFIG_RTE_LIBRTE_IFPGA_BUS) += ifpga_common.c - -# -# Export include files -# -SYMLINK-$(CONFIG_RTE_LIBRTE_IFPGA_BUS)-include += rte_bus_ifpga.h - -include $(RTE_SDK)/mk/rte.lib.mk
drivers/bus/pci/Makefile deleted +0 -33
@@ -1,33 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2017 6WIND S.A. - -include $(RTE_SDK)/mk/rte.vars.mk - -LIB = librte_bus_pci.a -EXPORT_MAP := rte_bus_pci_version.map - -CFLAGS := -I$(SRCDIR) $(CFLAGS) -CFLAGS += -O3 $(WERROR_FLAGS) - -ifneq ($(CONFIG_RTE_EXEC_ENV_LINUX),) -SYSTEM := linux -endif -ifneq ($(CONFIG_RTE_EXEC_ENV_FREEBSD),) -SYSTEM := bsd -endif - -CFLAGS += -I$(RTE_SDK)/drivers/bus/pci/$(SYSTEM) -CFLAGS += -I$(RTE_SDK)/lib/librte_eal/common - -LDLIBS += -lrte_eal -lrte_mbuf -lrte_mempool -lrte_ring -LDLIBS += -lrte_pci -lrte_kvargs - -include $(RTE_SDK)/drivers/bus/pci/$(SYSTEM)/Makefile -SRCS-$(CONFIG_RTE_LIBRTE_PCI_BUS) := $(addprefix $(SYSTEM)/,$(SRCS)) -SRCS-$(CONFIG_RTE_LIBRTE_PCI_BUS) += pci_params.c -SRCS-$(CONFIG_RTE_LIBRTE_PCI_BUS) += pci_common.c -SRCS-$(CONFIG_RTE_LIBRTE_PCI_BUS) += pci_common_uio.c - -SYMLINK-$(CONFIG_RTE_LIBRTE_PCI_BUS)-include += rte_bus_pci.h - -include $(RTE_SDK)/mk/rte.lib.mk
drivers/bus/pci/bsd/Makefile deleted +0 -4
@@ -1,4 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2017 6WIND S.A. - -SRCS += pci.c
drivers/bus/pci/linux/Makefile deleted +0 -6
@@ -1,6 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2017 6WIND S.A. - -SRCS += pci.c -SRCS += pci_uio.c -SRCS += pci_vfio.c
drivers/bus/vdev/Makefile deleted +0 -27
@@ -1,27 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2017 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -# -# library name -# -LIB = librte_bus_vdev.a - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) - -# versioning export map -EXPORT_MAP := rte_bus_vdev_version.map - -SRCS-y += vdev.c -SRCS-y += vdev_params.c - -LDLIBS += -lrte_eal -lrte_kvargs - -# -# Export include files -# -SYMLINK-y-include += rte_bus_vdev.h - -include $(RTE_SDK)/mk/rte.lib.mk
drivers/bus/vmbus/Makefile deleted +0 -33
@@ -1,33 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause - -include $(RTE_SDK)/mk/rte.vars.mk - -LIB = librte_bus_vmbus.a -EXPORT_MAP := rte_bus_vmbus_version.map - -CFLAGS += -I$(SRCDIR) -CFLAGS += -O3 $(WERROR_FLAGS) - -ifneq ($(CONFIG_RTE_EXEC_ENV_LINUX),) -SYSTEM := linux -endif -ifneq ($(CONFIG_RTE_EXEC_ENV_FREEBSD),) -$(error "VMBUS not implemented for BSD yet") -endif - -CFLAGS += -I$(RTE_SDK)/drivers/bus/vmbus/$(SYSTEM) -CFLAGS += -I$(RTE_SDK)/lib/librte_eal/common - -LDLIBS += -lrte_eal -lrte_mbuf -lrte_mempool -lrte_ring -LDLIBS += -lrte_ethdev - -include $(RTE_SDK)/drivers/bus/vmbus/$(SYSTEM)/Makefile -SRCS-$(CONFIG_RTE_LIBRTE_VMBUS) := $(addprefix $(SYSTEM)/,$(SRCS)) -SRCS-$(CONFIG_RTE_LIBRTE_VMBUS) += vmbus_common.c -SRCS-$(CONFIG_RTE_LIBRTE_VMBUS) += vmbus_channel.c vmbus_bufring.c -SRCS-$(CONFIG_RTE_LIBRTE_VMBUS) += vmbus_common_uio.c - -SYMLINK-$(CONFIG_RTE_LIBRTE_VMBUS)-include += rte_bus_vmbus.h -SYMLINK-$(CONFIG_RTE_LIBRTE_VMBUS)-include += rte_vmbus_reg.h - -include $(RTE_SDK)/mk/rte.lib.mk
drivers/bus/vmbus/linux/Makefile deleted +0 -3
@@ -1,3 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause - -SRCS += vmbus_bus.c vmbus_uio.c
drivers/common/Makefile deleted +0 -39
@@ -1,39 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2018 Cavium, Inc -# - -include $(RTE_SDK)/mk/rte.vars.mk - -CPT-y := $(CONFIG_RTE_LIBRTE_PMD_OCTEONTX_CRYPTO) -CPT-y += $(CONFIG_RTE_LIBRTE_PMD_OCTEONTX2_CRYPTO) -ifneq (,$(findstring y,$(CPT-y))) -DIRS-y += cpt -endif - -ifeq ($(CONFIG_RTE_LIBRTE_PMD_OCTEONTX_SSOVF)$(CONFIG_RTE_LIBRTE_OCTEONTX_MEMPOOL),yy) -DIRS-y += octeontx -endif -OCTEONTX2-y := $(CONFIG_RTE_LIBRTE_OCTEONTX2_MEMPOOL) -OCTEONTX2-y += $(CONFIG_RTE_LIBRTE_PMD_OCTEONTX2_CRYPTO) -ifeq ($(findstring y,$(OCTEONTX2-y)),y) -DIRS-y += octeontx2 -endif - -MVEP-y := $(CONFIG_RTE_LIBRTE_MVPP2_PMD) -MVEP-y += $(CONFIG_RTE_LIBRTE_MVNETA_PMD) -MVEP-y += $(CONFIG_RTE_LIBRTE_PMD_MVSAM_CRYPTO) -ifneq (,$(findstring y,$(MVEP-y))) -DIRS-y += mvep -endif - -ifeq ($(CONFIG_RTE_LIBRTE_COMMON_DPAAX),y) -DIRS-y += dpaax -endif - -IAVF-y := $(CONFIG_RTE_LIBRTE_IAVF_PMD) -IAVF-y += $(CONFIG_RTE_LIBRTE_ICE_PMD) -ifneq (,$(findstring y,$(IAVF-y))) -DIRS-y += iavf -endif - -include $(RTE_SDK)/mk/rte.subdir.mk
drivers/common/cpt/Makefile deleted +0 -24
@@ -1,24 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2018 Cavium, Inc -# - -include $(RTE_SDK)/mk/rte.vars.mk - -# -# library name -# -LIB = librte_common_cpt.a - -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -I$(RTE_SDK)/drivers/bus/pci -EXPORT_MAP := rte_common_cpt_version.map - -# -# all source are stored in SRCS-y -# -SRCS-y += cpt_fpm_tables.c -SRCS-y += cpt_pmd_ops_helper.c - -LDLIBS += -lrte_eal - -include $(RTE_SDK)/mk/rte.lib.mk
drivers/common/dpaax/Makefile deleted +0 -30
@@ -1,30 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright 2018 NXP -# - -include $(RTE_SDK)/mk/rte.vars.mk - -# -# library name -# -LIB = librte_common_dpaax.a - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -Wno-pointer-arith -CFLAGS += -Wno-cast-qual - -CFLAGS += -I$(RTE_SDK)/drivers/common/dpaax -CFLAGS += -I$(RTE_SDK)/drivers/common/dpaax/caamflib - -# versioning export map -EXPORT_MAP := rte_common_dpaax_version.map - -# -# all source are stored in SRCS-y -# -SRCS-y += dpaax_iova_table.c dpaa_of.c caamflib.c - -LDLIBS += -lrte_eal - -include $(RTE_SDK)/mk/rte.lib.mk
drivers/common/iavf/Makefile deleted +0 -27
@@ -1,27 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2019 Intel Corporation - -include $(RTE_SDK)/mk/rte.vars.mk - -# -# library name -# -LIB = librte_common_iavf.a - -CFLAGS += -O3 -CFLAGS += $(WERROR_FLAGS) -CFLAGS += -Wno-pointer-arith -CFLAGS += -Wno-cast-qual - -EXPORT_MAP := rte_common_iavf_version.map - -# -# all source are stored in SRCS-y -# -SRCS-y += iavf_adminq.c -SRCS-y += iavf_common.c -SRCS-y += iavf_impl.c - -LDLIBS += -lrte_eal - -include $(RTE_SDK)/mk/rte.lib.mk
drivers/common/mlx5/Makefile deleted +0 -404
140 lines not on this page · raw message
drivers/common/octeontx/Makefile deleted +0 -22
Lines of this file are not shown. View the raw message.
drivers/common/octeontx2/Makefile deleted +0 -39
Lines of this file are not shown. View the raw message.
drivers/common/qat/Makefile deleted +0 -74
74 lines not on this page · raw message
drivers/compress/isal/Makefile deleted +0 -27
Lines of this file are not shown. View the raw message.
drivers/compress/octeontx/Makefile deleted +0 -26
Lines of this file are not shown. View the raw message.
drivers/compress/zlib/Makefile deleted +0 -25
Lines of this file are not shown. View the raw message.
drivers/crypto/aesni_gcm/Makefile deleted +0 -43
43 lines not on this page · raw message
drivers/crypto/aesni_mb/Makefile deleted +0 -42
42 lines not on this page · raw message
drivers/crypto/caam_jr/Makefile deleted +0 -39
Lines of this file are not shown. View the raw message.
drivers/crypto/dpaa2_sec/Makefile deleted +0 -45
45 lines not on this page · raw message
drivers/crypto/dpaa_sec/Makefile deleted +0 -38
Lines of this file are not shown. View the raw message.
drivers/crypto/kasumi/Makefile deleted +0 -42
42 lines not on this page · raw message
drivers/crypto/nitrox/Makefile deleted +0 -30
Lines of this file are not shown. View the raw message.
drivers/crypto/octeontx/Makefile deleted +0 -36
Lines of this file are not shown. View the raw message.
drivers/crypto/octeontx2/Makefile deleted +0 -49
49 lines not on this page · raw message
drivers/crypto/openssl/Makefile deleted +0 -26
Lines of this file are not shown. View the raw message.
drivers/crypto/scheduler/Makefile deleted +0 -34
Lines of this file are not shown. View the raw message.
drivers/crypto/snow3g/Makefile deleted +0 -43
43 lines not on this page · raw message
drivers/crypto/virtio/Makefile deleted +0 -33
Lines of this file are not shown. View the raw message.
drivers/crypto/zuc/Makefile deleted +0 -42
42 lines not on this page · raw message
drivers/event/dpaa2/Makefile deleted +0 -41
41 lines not on this page · raw message
drivers/event/octeontx/Makefile deleted +0 -51
51 lines not on this page · raw message
drivers/event/octeontx2/Makefile deleted +0 -47
47 lines not on this page · raw message
drivers/event/skeleton/Makefile deleted +0 -24
Lines of this file are not shown. View the raw message.
drivers/mempool/bucket/Makefile deleted +0 -25
Lines of this file are not shown. View the raw message.
drivers/mempool/dpaa2/Makefile deleted +0 -31
Lines of this file are not shown. View the raw message.
drivers/mempool/octeontx/Makefile deleted +0 -39
Lines of this file are not shown. View the raw message.
drivers/mempool/octeontx2/Makefile deleted +0 -40
Lines of this file are not shown. View the raw message.
drivers/mempool/stack/Makefile deleted +0 -22
Lines of this file are not shown. View the raw message.
drivers/net/Makefile deleted +0 -84
84 lines not on this page · raw message
drivers/net/af_packet/Makefile deleted +0 -27
Lines of this file are not shown. View the raw message.
drivers/net/bnxt/Makefile deleted +0 -63
63 lines not on this page · raw message
drivers/net/bnxt/hcapi/Makefile deleted +0 -5
Lines of this file are not shown. View the raw message.
drivers/net/bnxt/tf_core/Makefile deleted +0 -31
Lines of this file are not shown. View the raw message.
drivers/net/bnxt/tf_ulp/Makefile deleted +0 -20
Lines of this file are not shown. View the raw message.
drivers/net/cxgbe/Makefile deleted +0 -57
57 lines not on this page · raw message
drivers/net/dpaa/Makefile deleted +0 -41
41 lines not on this page · raw message
drivers/net/dpaa2/Makefile deleted +0 -47
47 lines not on this page · raw message
drivers/net/e1000/Makefile deleted +0 -79
79 lines not on this page · raw message
drivers/net/enic/Makefile deleted +0 -68
68 lines not on this page · raw message
drivers/net/failsafe/Makefile deleted +0 -43
43 lines not on this page · raw message
drivers/net/fm10k/Makefile deleted +0 -77
77 lines not on this page · raw message
drivers/net/hinic/Makefile deleted +0 -67
67 lines not on this page · raw message
drivers/net/hns3/Makefile deleted +0 -42
42 lines not on this page · raw message
drivers/net/i40e/Makefile deleted +0 -112
112 lines not on this page · raw message
drivers/net/iavf/Makefile deleted +0 -54
54 lines not on this page · raw message
drivers/net/ice/Makefile deleted +0 -96
96 lines not on this page · raw message
drivers/net/ixgbe/Makefile deleted +0 -110
110 lines not on this page · raw message
drivers/net/mlx4/Makefile deleted +0 -142
142 lines not on this page · raw message
drivers/net/mlx5/Makefile deleted +0 -82
82 lines not on this page · raw message
drivers/net/mvpp2/Makefile deleted +0 -42
42 lines not on this page · raw message
drivers/net/nfp/Makefile deleted +0 -41
41 lines not on this page · raw message
drivers/net/octeontx/Makefile deleted +0 -53
53 lines not on this page · raw message
drivers/net/octeontx2/Makefile deleted +0 -63
63 lines not on this page · raw message
drivers/net/qede/Makefile deleted +0 -109
109 lines not on this page · raw message
drivers/net/sfc/Makefile deleted +0 -133
133 lines not on this page · raw message
drivers/net/softnic/Makefile deleted +0 -54
54 lines not on this page · raw message
drivers/net/tap/Makefile deleted +0 -97
97 lines not on this page · raw message
drivers/net/thunderx/Makefile deleted +0 -41
41 lines not on this page · raw message
drivers/net/vdev_netvsc/Makefile deleted +0 -30
Lines of this file are not shown. View the raw message.
drivers/net/virtio/Makefile deleted +0 -82
82 lines not on this page · raw message
drivers/net/vmxnet3/Makefile deleted +0 -53
53 lines not on this page · raw message
drivers/raw/dpaa2_cmdif/Makefile deleted +0 -35
Lines of this file are not shown. View the raw message.
drivers/raw/dpaa2_qdma/Makefile deleted +0 -36
Lines of this file are not shown. View the raw message.
drivers/raw/ifpga/base/Makefile deleted +0 -32
Lines of this file are not shown. View the raw message.
drivers/raw/octeontx2_dma/Makefile deleted +0 -34
Lines of this file are not shown. View the raw message.
drivers/raw/octeontx2_ep/Makefile deleted +0 -42
42 lines not on this page · raw message
drivers/regex/mlx5/Makefile deleted +0 -41
41 lines not on this page · raw message
drivers/vdpa/mlx5/Makefile deleted +0 -58
58 lines not on this page · raw message
examples/Makefile deleted +0 -90
90 lines not on this page · raw message
kernel/freebsd/contigmem/Makefile deleted +0 -24
Lines of this file are not shown. View the raw message.
kernel/freebsd/nic_uio/Makefile deleted +0 -24
Lines of this file are not shown. View the raw message.
lib/Makefile deleted +0 -138
138 lines not on this page · raw message
lib/librte_acl/Makefile deleted +0 -65
65 lines not on this page · raw message
lib/librte_bitratestats/Makefile deleted +0 -20
Lines of this file are not shown. View the raw message.
lib/librte_compressdev/Makefile deleted +0 -27
Lines of this file are not shown. View the raw message.
lib/librte_distributor/Makefile deleted +0 -28
Lines of this file are not shown. View the raw message.
lib/librte_eal/freebsd/Makefile deleted +0 -104
104 lines not on this page · raw message
lib/librte_eal/include/Makefile deleted +0 -19
Lines of this file are not shown. View the raw message.
lib/librte_eal/linux/Makefile deleted +0 -112
112 lines not on this page · raw message
lib/librte_ethdev/Makefile deleted +0 -46
46 lines not on this page · raw message
lib/librte_eventdev/Makefile deleted +0 -47
47 lines not on this page · raw message
lib/librte_flow_classify/Makefile deleted +0 -23
Lines of this file are not shown. View the raw message.
lib/librte_latencystats/Makefile deleted +0 -22
Lines of this file are not shown. View the raw message.
lib/librte_port/Makefile deleted +0 -59
59 lines not on this page · raw message
lib/librte_table/Makefile deleted +0 -59
59 lines not on this page · raw message
lib/librte_vhost/Makefile deleted +0 -54
54 lines not on this page · raw message
mk/exec-env/freebsd/rte.vars.mk deleted +0 -36
Lines of this file are not shown. View the raw message.
mk/exec-env/linux/rte.vars.mk deleted +0 -44
44 lines not on this page · raw message
mk/internal/rte.compile-post.mk deleted +0 -5
Lines of this file are not shown. View the raw message.
mk/internal/rte.compile-pre.mk deleted +0 -164
164 lines not on this page · raw message
mk/internal/rte.extvars.mk deleted +0 -55
55 lines not on this page · raw message
mk/internal/rte.install-post.mk deleted +0 -71
71 lines not on this page · raw message
mk/internal/rte.install-pre.mk deleted +0 -32
Lines of this file are not shown. View the raw message.
mk/machine/default/rte.vars.mk deleted +0 -30
Lines of this file are not shown. View the raw message.
mk/machine/octeontx2/rte.vars.mk deleted +0 -34
Lines of this file are not shown. View the raw message.
mk/machine/silvermont/rte.vars.mk deleted +0 -30
Lines of this file are not shown. View the raw message.
mk/machine/thunderx/rte.vars.mk deleted +0 -31
Lines of this file are not shown. View the raw message.
mk/machine/thunderx2/rte.vars.mk deleted +0 -34
Lines of this file are not shown. View the raw message.
mk/rte.app.mk deleted +0 -509
509 lines not on this page · raw message
mk/rte.bsdmodule.mk deleted +0 -89
89 lines not on this page · raw message
mk/rte.cpuflags.mk deleted +0 -124
124 lines not on this page · raw message
mk/rte.gnuconfigure.mk deleted +0 -44
44 lines not on this page · raw message
mk/rte.hostapp.mk deleted +0 -93
93 lines not on this page · raw message
mk/rte.hostlib.mk deleted +0 -86
86 lines not on this page · raw message
mk/rte.lib.mk deleted +0 -156
156 lines not on this page · raw message
mk/rte.module.mk deleted +0 -86
86 lines not on this page · raw message
mk/rte.obj.mk deleted +0 -82
82 lines not on this page · raw message
mk/rte.sdkbuild.mk deleted +0 -77
77 lines not on this page · raw message
mk/rte.sdkconfig.mk deleted +0 -142
142 lines not on this page · raw message
mk/rte.sdkdoc.mk deleted +0 -104
104 lines not on this page · raw message
mk/rte.sdkexamples.mk deleted +0 -50
50 lines not on this page · raw message
mk/rte.sdkinstall.mk deleted +0 -152
152 lines not on this page · raw message
mk/rte.sdkroot.mk deleted +0 -115
115 lines not on this page · raw message
mk/rte.sdktest.mk deleted +0 -76
76 lines not on this page · raw message
mk/rte.shared.mk deleted +0 -108
108 lines not on this page · raw message
mk/rte.subdir.mk deleted +0 -65
65 lines not on this page · raw message
mk/rte.vars.mk deleted +0 -102
102 lines not on this page · raw message
mk/target/generic/rte.vars.mk deleted +0 -132
132 lines not on this page · raw message
mk/toolchain/clang/rte.toolchain-compat.mk deleted +0 -22
Lines of this file are not shown. View the raw message.
mk/toolchain/clang/rte.vars.mk deleted +0 -60
60 lines not on this page · raw message
mk/toolchain/gcc/rte.toolchain-compat.mk deleted +0 -120
120 lines not on this page · raw message
mk/toolchain/gcc/rte.vars.mk deleted +0 -109
109 lines not on this page · raw message
mk/toolchain/icc/rte.toolchain-compat.mk deleted +0 -58
58 lines not on this page · raw message
mk/toolchain/icc/rte.vars.mk deleted +0 -62
62 lines not on this page · raw message
The rest of this diff is not shown. View the raw message.
Signature · 1 line
2.28.0
Part of the diff is not shown here. View the raw message.
PATCH v4 12/31 buildtools: remove scripts used only with make
In reply to Thomas MonjalonFrom: Ciara Power <[email protected]>
Make is no longer supported for compiling DPDK, scripts used with make are no longer needed.
--- MAINTAINERS | 4 -- buildtools/auto-config-h.sh | 108 ------------------------------------ buildtools/gen-build-mk.sh | 23 -------- buildtools/gen-config-h.sh | 15 ----- buildtools/relpath.sh | 76 ------------------------- 5 files changed, 226 deletions(-) delete mode 100755 buildtools/auto-config-h.sh delete mode 100755 buildtools/gen-build-mk.sh delete mode 100755 buildtools/gen-config-h.sh delete mode 100755 buildtools/relpath.sh
MAINTAINERS +0 -4
@@ -100,10 +100,6 @@ Build System M: Thomas Monjalon <[email protected]> F: Makefile F: config/ -F: buildtools/auto-config-h.sh -F: buildtools/gen-build-mk.sh -F: buildtools/gen-config-h.sh -F: buildtools/relpath.sh Meson build M: Bruce Richardson <[email protected]>
buildtools/auto-config-h.sh deleted +0 -108
108 lines not on this page · raw message
buildtools/gen-build-mk.sh deleted +0 -23
@@ -1,23 +0,0 @@ -#!/bin/sh -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014 Intel Corporation - -# Auto-generate a Makefile in build directory -# Args: -# $1: path of project src root - -echo "# Automatically generated by gen-build-mk.sh" -echo -echo "ifdef O" -echo "ifeq (\"\$(origin O)\", \"command line\")" -echo "\$(error \"Cannot specify O= as you are already in a build directory\")" -echo "endif" -echo "endif" -echo -echo "MAKEFLAGS += --no-print-directory" -echo -echo "all:" -echo " @\$(MAKE) -C $1 O=\$(CURDIR)" -echo -echo "%::" -echo " @\$(MAKE) -C $1 O=\$(CURDIR) \$@"
buildtools/gen-config-h.sh deleted +0 -15
@@ -1,15 +0,0 @@ -#!/bin/sh -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014 Intel Corporation - -echo "#ifndef __RTE_CONFIG_H" -echo "#define __RTE_CONFIG_H" -grep CONFIG_ $1 | -grep -v '^[ \t]*#' | -sed 's,CONFIG_\(.*\)=y.*$,#undef \1\ -#define \1 1,' | -sed 's,CONFIG_\(.*\)=n.*$,#undef \1,' | -sed 's,CONFIG_\(.*\)=\(.*\)$,#undef \1\ -#define \1 \2,' | -sed 's,\# CONFIG_\(.*\) is not set$,#undef \1,' -echo "#endif /* __RTE_CONFIG_H */"
buildtools/relpath.sh deleted +0 -76
76 lines not on this page · raw message
Signature · 1 line
2.28.0
PATCH v4 13/31 config: remove default configs used with make
In reply to Thomas MonjalonFrom: Ciara Power <[email protected]>
Make is not supported for compiling DPDK, the config files are no longer needed.
--- MAINTAINERS | 10 +- config/common_armv8a_linux | 43 - config/common_base | 1154 ----------------- config/common_freebsd | 15 - config/common_linux | 68 - config/defconfig_arm-armv7a-linux-gcc | 1 - config/defconfig_arm-armv7a-linuxapp-gcc | 49 - config/defconfig_arm64-armada-linux-gcc | 1 - config/defconfig_arm64-armada-linuxapp-gcc | 41 - config/defconfig_arm64-armv8a-linux-clang | 1 - config/defconfig_arm64-armv8a-linux-gcc | 1 - config/defconfig_arm64-armv8a-linuxapp-clang | 8 - config/defconfig_arm64-armv8a-linuxapp-gcc | 9 - config/defconfig_arm64-bluefield-linux-gcc | 1 - config/defconfig_arm64-bluefield-linuxapp-gcc | 18 - config/defconfig_arm64-dpaa-linux-gcc | 1 - config/defconfig_arm64-dpaa-linuxapp-gcc | 31 - config/defconfig_arm64-emag-linux-gcc | 1 - config/defconfig_arm64-emag-linuxapp-gcc | 11 - config/defconfig_arm64-n1sdp-linux-gcc | 1 - config/defconfig_arm64-n1sdp-linuxapp-gcc | 14 - config/defconfig_arm64-octeontx2-linux-gcc | 1 - config/defconfig_arm64-octeontx2-linuxapp-gcc | 18 - config/defconfig_arm64-stingray-linux-gcc | 1 - config/defconfig_arm64-stingray-linuxapp-gcc | 14 - config/defconfig_arm64-thunderx-linux-gcc | 1 - config/defconfig_arm64-thunderx-linuxapp-gcc | 17 - config/defconfig_arm64-thunderx2-linux-gcc | 1 - config/defconfig_arm64-thunderx2-linuxapp-gcc | 12 - config/defconfig_arm64-xgene1-linux-gcc | 1 - config/defconfig_arm64-xgene1-linuxapp-gcc | 8 - config/defconfig_i686-native-linux-gcc | 1 - config/defconfig_i686-native-linux-icc | 1 - config/defconfig_i686-native-linuxapp-gcc | 66 - config/defconfig_i686-native-linuxapp-icc | 66 - config/defconfig_ppc_64-power8-linux-gcc | 1 - config/defconfig_ppc_64-power8-linuxapp-gcc | 35 - config/defconfig_x86_64-native-bsdapp-clang | 14 - config/defconfig_x86_64-native-bsdapp-gcc | 14 - config/defconfig_x86_64-native-freebsd-clang | 1 - config/defconfig_x86_64-native-freebsd-gcc | 1 - config/defconfig_x86_64-native-linux-clang | 1 - config/defconfig_x86_64-native-linux-gcc | 1 - config/defconfig_x86_64-native-linux-icc | 1 - config/defconfig_x86_64-native-linuxapp-clang | 14 - config/defconfig_x86_64-native-linuxapp-gcc | 14 - config/defconfig_x86_64-native-linuxapp-icc | 29 - config/defconfig_x86_x32-native-linux-gcc | 1 - config/defconfig_x86_x32-native-linuxapp-gcc | 46 - config/rte_config.h | 4 - devtools/build-tags.sh | 15 +- drivers/bus/pci/linux/pci_vfio.c | 1 - drivers/net/i40e/i40e_rxtx.c | 1 - lib/librte_mempool/rte_mempool.h | 2 +- lib/librte_ring/rte_ring_elem.h | 3 +- 55 files changed, 6 insertions(+), 1880 deletions(-) delete mode 100644 config/common_armv8a_linux delete mode 100644 config/common_base delete mode 100644 config/common_freebsd delete mode 100644 config/common_linux delete mode 120000 config/defconfig_arm-armv7a-linux-gcc delete mode 100644 config/defconfig_arm-armv7a-linuxapp-gcc delete mode 120000 config/defconfig_arm64-armada-linux-gcc delete mode 100644 config/defconfig_arm64-armada-linuxapp-gcc delete mode 120000 config/defconfig_arm64-armv8a-linux-clang delete mode 120000 config/defconfig_arm64-armv8a-linux-gcc delete mode 100644 config/defconfig_arm64-armv8a-linuxapp-clang delete mode 100644 config/defconfig_arm64-armv8a-linuxapp-gcc delete mode 120000 config/defconfig_arm64-bluefield-linux-gcc delete mode 100644 config/defconfig_arm64-bluefield-linuxapp-gcc delete mode 120000 config/defconfig_arm64-dpaa-linux-gcc delete mode 100644 config/defconfig_arm64-dpaa-linuxapp-gcc delete mode 120000 config/defconfig_arm64-emag-linux-gcc delete mode 100644 config/defconfig_arm64-emag-linuxapp-gcc delete mode 120000 config/defconfig_arm64-n1sdp-linux-gcc delete mode 100644 config/defconfig_arm64-n1sdp-linuxapp-gcc delete mode 120000 config/defconfig_arm64-octeontx2-linux-gcc delete mode 100644 config/defconfig_arm64-octeontx2-linuxapp-gcc delete mode 120000 config/defconfig_arm64-stingray-linux-gcc delete mode 100644 config/defconfig_arm64-stingray-linuxapp-gcc delete mode 120000 config/defconfig_arm64-thunderx-linux-gcc delete mode 100644 config/defconfig_arm64-thunderx-linuxapp-gcc delete mode 120000 config/defconfig_arm64-thunderx2-linux-gcc delete mode 100644 config/defconfig_arm64-thunderx2-linuxapp-gcc delete mode 120000 config/defconfig_arm64-xgene1-linux-gcc delete mode 100644 config/defconfig_arm64-xgene1-linuxapp-gcc delete mode 120000 config/defconfig_i686-native-linux-gcc delete mode 120000 config/defconfig_i686-native-linux-icc delete mode 100644 config/defconfig_i686-native-linuxapp-gcc delete mode 100644 config/defconfig_i686-native-linuxapp-icc delete mode 120000 config/defconfig_ppc_64-power8-linux-gcc delete mode 100644 config/defconfig_ppc_64-power8-linuxapp-gcc delete mode 100644 config/defconfig_x86_64-native-bsdapp-clang delete mode 100644 config/defconfig_x86_64-native-bsdapp-gcc delete mode 120000 config/defconfig_x86_64-native-freebsd-clang delete mode 120000 config/defconfig_x86_64-native-freebsd-gcc delete mode 120000 config/defconfig_x86_64-native-linux-clang delete mode 120000 config/defconfig_x86_64-native-linux-gcc delete mode 120000 config/defconfig_x86_64-native-linux-icc delete mode 100644 config/defconfig_x86_64-native-linuxapp-clang delete mode 100644 config/defconfig_x86_64-native-linuxapp-gcc delete mode 100644 config/defconfig_x86_64-native-linuxapp-icc delete mode 120000 config/defconfig_x86_x32-native-linux-gcc delete mode 100644 config/defconfig_x86_x32-native-linuxapp-gcc
MAINTAINERS +2 -8
@@ -94,18 +94,12 @@ F: devtools/words-case.txt F: license/ F: .editorconfig - Build System ------------- -M: Thomas Monjalon <[email protected]> +M: Bruce Richardson <[email protected]> F: Makefile -F: config/ - -Meson build -M: Bruce Richardson <[email protected]> F: meson.build F: meson_options.txt -F: config/rte_config.h +F: config/ F: buildtools/binutils-avx512-check.sh F: buildtools/call-sphinx-build.py F: buildtools/gen-pmdinfo-cfile.sh
config/common_armv8a_linux deleted +0 -43
43 lines not on this page · raw message
config/common_base deleted +0 -1154
1,154 lines not on this page · raw message
config/common_freebsd deleted +0 -15
@@ -1,15 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2016 Intel Corporation - -#include "common_base" - -CONFIG_RTE_EXEC_ENV="bsdapp" -CONFIG_RTE_EXEC_ENV_BSDAPP=y -CONFIG_RTE_EXEC_ENV_FREEBSD=y - -# -# FreeBSD contiguous memory driver settings -# -CONFIG_RTE_CONTIGMEM_MAX_NUM_BUFS=64 -CONFIG_RTE_CONTIGMEM_DEFAULT_NUM_BUFS=2 -CONFIG_RTE_CONTIGMEM_DEFAULT_BUF_SIZE=1024*1024*1024
config/common_linux deleted +0 -68
68 lines not on this page · raw message
config/defconfig_arm-armv7a-linux-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_arm-armv7a-linuxapp-gcc
config/defconfig_arm-armv7a-linuxapp-gcc deleted +0 -49
49 lines not on this page · raw message
config/defconfig_arm64-armada-linux-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_arm64-armada-linuxapp-gcc
config/defconfig_arm64-armada-linuxapp-gcc deleted +0 -41
41 lines not on this page · raw message
config/defconfig_arm64-armv8a-linux-clang deleted +0 -1
@@ -1 +0,0 @@ -defconfig_arm64-armv8a-linuxapp-clang
config/defconfig_arm64-armv8a-linux-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_arm64-armv8a-linuxapp-gcc
config/defconfig_arm64-armv8a-linuxapp-clang deleted +0 -8
@@ -1,8 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2017 Cavium, Inc -# - -#include "common_armv8a_linux" - -CONFIG_RTE_TOOLCHAIN="clang" -CONFIG_RTE_TOOLCHAIN_CLANG=y
config/defconfig_arm64-armv8a-linuxapp-gcc deleted +0 -9
@@ -1,9 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2015 Cavium, Inc -# - -#include "common_armv8a_linux" - -CONFIG_RTE_TOOLCHAIN="gcc" -CONFIG_RTE_TOOLCHAIN_GCC=y -CONFIG_RTE_MAX_LCORE=256
config/defconfig_arm64-bluefield-linux-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_arm64-bluefield-linuxapp-gcc
config/defconfig_arm64-bluefield-linuxapp-gcc deleted +0 -18
@@ -1,18 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright 2019 Mellanox Technologies, Ltd -# - -#include "defconfig_arm64-armv8a-linux-gcc" - -# Mellanox BlueField -CONFIG_RTE_ARCH_ARM_TUNE="cortex-a72" - -CONFIG_RTE_MAX_NUMA_NODES=1 -CONFIG_RTE_CACHE_LINE_SIZE=64 - -# UMA architecture -CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=n -CONFIG_RTE_LIBRTE_VHOST_NUMA=n - -# PMD for ConnectX-5 -CONFIG_RTE_LIBRTE_MLX5_PMD=y
config/defconfig_arm64-dpaa-linux-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_arm64-dpaa-linuxapp-gcc
config/defconfig_arm64-dpaa-linuxapp-gcc deleted +0 -31
@@ -1,31 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright 2016 Freescale Semiconductor, Inc. -# Copyright 2017-2019 NXP - -#include "defconfig_arm64-armv8a-linux-gcc" - -# NXP (Freescale) - Soc Architecture for DPAA or DPAA2 support -# DPAA - FMAN, QMAN & BMAN support (e.g. LS1043, LS1046) -# DPAA2 - WRIOP and QBMAN (e.g. LS1088, LS2088, LX2160 etc) -# -CONFIG_RTE_MACHINE="dpaa" -CONFIG_RTE_ARCH_ARM_TUNE="cortex-a72" - -# -# Compile Environment Abstraction Layer -# -CONFIG_RTE_MAX_LCORE=16 -CONFIG_RTE_MAX_NUMA_NODES=1 -CONFIG_RTE_CACHE_LINE_SIZE=64 -CONFIG_RTE_PKTMBUF_HEADROOM=128 - -# Doesn't support NUMA -CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=n -CONFIG_RTE_LIBRTE_VHOST_NUMA=n - -# Enable PHY mode when using VM-VFIO target -CONFIG_RTE_LIBRTE_DPAA2_USE_PHYS_IOVA=n - -# NXP DPAA Bus -CONFIG_RTE_LIBRTE_DPAA_DEBUG_DRIVER=n -CONFIG_RTE_LIBRTE_DPAA_HWDEBUG=n
config/defconfig_arm64-emag-linux-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_arm64-emag-linuxapp-gcc
config/defconfig_arm64-emag-linuxapp-gcc deleted +0 -11
@@ -1,11 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2019 Ampere Computing -# - -#include "defconfig_arm64-armv8a-linux-gcc" - -CONFIG_RTE_MACHINE="emag" - -CONFIG_RTE_CACHE_LINE_SIZE=64 -CONFIG_RTE_MAX_NUMA_NODES=1 -CONFIG_RTE_MAX_LCORE=32
config/defconfig_arm64-n1sdp-linux-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_arm64-n1sdp-linuxapp-gcc
config/defconfig_arm64-n1sdp-linuxapp-gcc deleted +0 -14
@@ -1,14 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2019 Arm Ltd. -# - -#include "defconfig_arm64-armv8a-linux-gcc" - -CONFIG_RTE_MACHINE="n1sdp" -CONFIG_RTE_MAX_LCORE=4 -CONFIG_RTE_MAX_NUMA_NODES=1 -CONFIG_RTE_CACHE_LINE_SIZE=64 - -# Doesn't support NUMA -CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=n -CONFIG_RTE_LIBRTE_VHOST_NUMA=n
config/defconfig_arm64-octeontx2-linux-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_arm64-octeontx2-linuxapp-gcc
config/defconfig_arm64-octeontx2-linuxapp-gcc deleted +0 -18
@@ -1,18 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2018 Marvell International Ltd -# - -#include "defconfig_arm64-armv8a-linux-gcc" - -CONFIG_RTE_MACHINE="octeontx2" - -CONFIG_RTE_MAX_NUMA_NODES=1 -CONFIG_RTE_MAX_LCORE=36 -CONFIG_RTE_ARM_FEATURE_ATOMICS=y - -# Doesn't support NUMA -CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=n -CONFIG_RTE_LIBRTE_VHOST_NUMA=n - -# Max supported NIX LFs -CONFIG_RTE_MAX_VFIO_GROUPS=128
config/defconfig_arm64-stingray-linux-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_arm64-stingray-linuxapp-gcc
config/defconfig_arm64-stingray-linuxapp-gcc deleted +0 -14
@@ -1,14 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright (C) Broadcom 2017-2018. All rights reserved. -# - -#include "defconfig_arm64-armv8a-linux-gcc" - -# Broadcom - Stingray -CONFIG_RTE_ARCH_ARM_TUNE="cortex-a72" - -# Doesn't support NUMA -CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=n -CONFIG_RTE_LIBRTE_VHOST_NUMA=n - -CONFIG_RTE_EAL_IGB_UIO=y
config/defconfig_arm64-thunderx-linux-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_arm64-thunderx-linuxapp-gcc
config/defconfig_arm64-thunderx-linuxapp-gcc deleted +0 -17
@@ -1,17 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2015 Cavium, Inc -# - -#include "defconfig_arm64-armv8a-linux-gcc" - -CONFIG_RTE_MACHINE="thunderx" - -CONFIG_RTE_USE_C11_MEM_MODEL=n -CONFIG_RTE_MAX_NUMA_NODES=2 -CONFIG_RTE_MAX_LCORE=96 -CONFIG_RTE_MAX_VFIO_GROUPS=128 - -# -# Compile PMD for octeontx sso event device -# -CONFIG_RTE_LIBRTE_PMD_OCTEONTX_SSOVF=y
config/defconfig_arm64-thunderx2-linux-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_arm64-thunderx2-linuxapp-gcc
config/defconfig_arm64-thunderx2-linuxapp-gcc deleted +0 -12
@@ -1,12 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2018 Marvell International Ltd -# - -#include "defconfig_arm64-armv8a-linux-gcc" - -CONFIG_RTE_MACHINE="thunderx2" - -CONFIG_RTE_CACHE_LINE_SIZE=64 -CONFIG_RTE_MAX_NUMA_NODES=2 -CONFIG_RTE_MAX_LCORE=256 -CONFIG_RTE_ARM_FEATURE_ATOMICS=y
config/defconfig_arm64-xgene1-linux-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_arm64-xgene1-linuxapp-gcc
config/defconfig_arm64-xgene1-linuxapp-gcc deleted +0 -8
@@ -1,8 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2015 Cavium, Inc -# - -#include "defconfig_arm64-armv8a-linux-gcc" - -CONFIG_RTE_MACHINE="xgene1" -CONFIG_RTE_CACHE_LINE_SIZE=64
config/defconfig_i686-native-linux-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_i686-native-linuxapp-gcc
config/defconfig_i686-native-linux-icc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_i686-native-linuxapp-icc
config/defconfig_i686-native-linuxapp-gcc deleted +0 -66
66 lines not on this page · raw message
config/defconfig_i686-native-linuxapp-icc deleted +0 -66
66 lines not on this page · raw message
config/defconfig_ppc_64-power8-linux-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_ppc_64-power8-linuxapp-gcc
config/defconfig_ppc_64-power8-linuxapp-gcc deleted +0 -35
@@ -1,35 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright (C) IBM Corporation 2014. - -#include "common_linux" - -CONFIG_RTE_MACHINE="power8" - -CONFIG_RTE_ARCH="ppc_64" -CONFIG_RTE_ARCH_PPC_64=y -CONFIG_RTE_ARCH_64=y - -CONFIG_RTE_MAX_LCORE=1536 -CONFIG_RTE_MAX_NUMA_NODES=32 -CONFIG_RTE_CACHE_LINE_SIZE=128 - -CONFIG_RTE_TOOLCHAIN="gcc" -CONFIG_RTE_TOOLCHAIN_GCC=y - -# Note: Power doesn't have this support -CONFIG_RTE_LIBRTE_EAL_VMWARE_TSC_MAP_SUPPORT=n - -# Note: Initially, all of the PMD drivers compilation are turned off on Power -# Will turn on them only after the successful testing on Power -CONFIG_RTE_LIBRTE_ATLANTIC_PMD=n -CONFIG_RTE_LIBRTE_IXGBE_PMD=n -CONFIG_RTE_LIBRTE_VIRTIO_PMD=y -CONFIG_RTE_LIBRTE_VMXNET3_PMD=n -CONFIG_RTE_LIBRTE_ENIC_PMD=n -CONFIG_RTE_LIBRTE_FM10K_PMD=n -CONFIG_RTE_LIBRTE_SFC_EFX_PMD=n -CONFIG_RTE_LIBRTE_AVP_PMD=n -CONFIG_RTE_LIBRTE_HINIC_PMD=n -CONFIG_RTE_LIBRTE_HNS3_PMD=n -CONFIG_RTE_LIBRTE_PMD_IOAT_RAWDEV=n -CONFIG_RTE_LIBRTE_IONIC_PMD=n
config/defconfig_x86_64-native-bsdapp-clang deleted +0 -14
@@ -1,14 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014 Intel Corporation - -#include "common_freebsd" - -CONFIG_RTE_MACHINE="native" - -CONFIG_RTE_ARCH="x86_64" -CONFIG_RTE_ARCH_X86_64=y -CONFIG_RTE_ARCH_X86=y -CONFIG_RTE_ARCH_64=y - -CONFIG_RTE_TOOLCHAIN="clang" -CONFIG_RTE_TOOLCHAIN_CLANG=y
config/defconfig_x86_64-native-bsdapp-gcc deleted +0 -14
@@ -1,14 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014 Intel Corporation - -#include "common_freebsd" - -CONFIG_RTE_MACHINE="native" - -CONFIG_RTE_ARCH="x86_64" -CONFIG_RTE_ARCH_X86_64=y -CONFIG_RTE_ARCH_X86=y -CONFIG_RTE_ARCH_64=y - -CONFIG_RTE_TOOLCHAIN="gcc" -CONFIG_RTE_TOOLCHAIN_GCC=y
config/defconfig_x86_64-native-freebsd-clang deleted +0 -1
@@ -1 +0,0 @@ -defconfig_x86_64-native-bsdapp-clang
config/defconfig_x86_64-native-freebsd-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_x86_64-native-bsdapp-gcc
config/defconfig_x86_64-native-linux-clang deleted +0 -1
@@ -1 +0,0 @@ -defconfig_x86_64-native-linuxapp-clang
config/defconfig_x86_64-native-linux-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_x86_64-native-linuxapp-gcc
config/defconfig_x86_64-native-linux-icc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_x86_64-native-linuxapp-icc
config/defconfig_x86_64-native-linuxapp-clang deleted +0 -14
@@ -1,14 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014 Intel Corporation - -#include "common_linux" - -CONFIG_RTE_MACHINE="native" - -CONFIG_RTE_ARCH="x86_64" -CONFIG_RTE_ARCH_X86_64=y -CONFIG_RTE_ARCH_X86=y -CONFIG_RTE_ARCH_64=y - -CONFIG_RTE_TOOLCHAIN="clang" -CONFIG_RTE_TOOLCHAIN_CLANG=y
config/defconfig_x86_64-native-linuxapp-gcc deleted +0 -14
@@ -1,14 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014 Intel Corporation - -#include "common_linux" - -CONFIG_RTE_MACHINE="native" - -CONFIG_RTE_ARCH="x86_64" -CONFIG_RTE_ARCH_X86_64=y -CONFIG_RTE_ARCH_X86=y -CONFIG_RTE_ARCH_64=y - -CONFIG_RTE_TOOLCHAIN="gcc" -CONFIG_RTE_TOOLCHAIN_GCC=y
config/defconfig_x86_64-native-linuxapp-icc deleted +0 -29
@@ -1,29 +0,0 @@ -# SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014 Intel Corporation - -#include "common_linux" - -CONFIG_RTE_MACHINE="native" - -CONFIG_RTE_ARCH="x86_64" -CONFIG_RTE_ARCH_X86_64=y -CONFIG_RTE_ARCH_X86=y -CONFIG_RTE_ARCH_64=y - -CONFIG_RTE_TOOLCHAIN="icc" -CONFIG_RTE_TOOLCHAIN_ICC=y - -# -# Solarflare PMD build is not supported using icc toolchain -# -CONFIG_RTE_LIBRTE_SFC_EFX_PMD=n - -# -# HINIC PMD build is not supported using icc toolchain -# -CONFIG_RTE_LIBRTE_HINIC_PMD=n - -# -# HNS3 PMD build is not supported using icc toolchain -# -CONFIG_RTE_LIBRTE_HNS3_PMD=n
config/defconfig_x86_x32-native-linux-gcc deleted +0 -1
@@ -1 +0,0 @@ -defconfig_x86_x32-native-linuxapp-gcc
config/defconfig_x86_x32-native-linuxapp-gcc deleted +0 -46
46 lines not on this page · raw message
config/rte_config.h +0 -4
@@ -8,10 +8,6 @@* Header file containing DPDK compilation parameters. Also include the * meson-generated header file containing the detected parameters that * are variable across builds or build environments. -* -* NOTE: This file is only used for meson+ninja builds. For builds done -* using make/gmake, the rte_config.h file is autogenerated from the -* defconfig_* files in the config directory. */ #ifndef _RTE_CONFIG_H_#define _RTE_CONFIG_H_
devtools/build-tags.sh +2 -13
@@ -19,8 +19,8 @@ arm_64=true print_usage() { echo "Usage: $(basename $0) [-h] [-v] tags|cscope|gtags|etags [config]" - echo "Valid configs are:" - make showconfigs | sed 's,^,\t,' + echo "Examples of valid configs are: " + echo "x86_64-bsd, arm64-linux, ppc_64-linux" } # Move to the root of the git tree
@@ -125,18 +125,7 @@ ppc_64_sources() find_sources "$source_dirs" '*altivec*.[chS]' } -check_valid_target() -{ - if [ ! -f "config/defconfig_$1" ] ; then - echo "Invalid config: $1" - print_usage - exit 0 - fi -} - if [ -n "$2" ]; then - check_valid_target $2 - echo $2 | grep -q "linux" || linux=false echo $2 | grep -q "bsd" || bsd=false echo $2 | grep -q "x86_64-" || x86_64=false
drivers/bus/pci/linux/pci_vfio.c +0 -1
@@ -34,7 +34,6 @@* This code tries to determine if the PCI device is bound to VFIO driver, * and initialize it (map BARs, set up interrupts) if that's the case. * -* This file is only compiled if CONFIG_RTE_EAL_VFIO is set to "y". */ #ifdef VFIO_PRESENT
drivers/net/i40e/i40e_rxtx.c +0 -1
@@ -3438,7 +3438,6 @@ i40e_set_default_pctype_table(struct rte_eth_dev *dev) }#ifndef RTE_LIBRTE_I40E_INC_VECTOR -/* Stubs needed for linkage when CONFIG_RTE_LIBRTE_I40E_INC_VECTOR is set to 'n' */ int i40e_rx_vec_dev_conf_condition_check(struct rte_eth_dev __rte_unused *dev) {
lib/librte_mempool/rte_mempool.h +1 -1
@@ -970,7 +970,7 @@ typedef void (rte_mempool_ctor_t)(struct rte_mempool *, void *);* If cache_size is non-zero, the rte_mempool library will try to * limit the accesses to the common lockless pool, by maintaining a * per-lcore object cache. This argument must be lower or equal to -* CONFIG_RTE_MEMPOOL_CACHE_MAX_SIZE and n / 1.5. It is advised to choose +* RTE_MEMPOOL_CACHE_MAX_SIZE and n / 1.5. It is advised to choose * cache_size to have "n modulo cache_size == 0": if this is * not the case, some elements will always stay in the pool and will * never be used. The access to the per-lcore table is of course
lib/librte_ring/rte_ring_elem.h +1 -2
@@ -373,8 +373,7 @@ __rte_ring_dequeue_elems(struct rte_ring *r, uint32_t cons_head,* (powerpc/arm). * There are 2 choices for the users * 1.use rmb() memory barrier -* 2.use one-direction load_acquire/store_release barrier,defined by -* CONFIG_RTE_USE_C11_MEM_MODEL=y +* 2.use one-direction load_acquire/store_release barrier * It depends on performance test results. * By default, move common functions to rte_ring_generic.h */
Signature · 1 line
2.28.0
PATCH v4 14/31 devtools: remove legacy flags from includes check
In reply to Thomas MonjalonFrom: Ciara Power <[email protected]>
Make is no longer supported, the test script for make builds is no longer required. Uses of make in other tool scripts are replaced.
--- devtools/check-includes.sh | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-)
devtools/check-includes.sh +5 -6
@@ -17,8 +17,7 @@ # # SUMMARY=1 is the same as -s. # -# CC, CPPFLAGS, CFLAGS, EXTRA_CPPFLAGS, EXTRA_CFLAGS, CXX, CXXFLAGS and -# EXTRA_CXXFLAGS are taken into account. +# CC, CPPFLAGS, CFLAGS, CXX, CXXFLAGS are taken into account. # # PEDANTIC_CFLAGS, PEDANTIC_CXXFLAGS and PEDANTIC_CPPFLAGS provide strict # C/C++ compilation flags.
@@ -130,16 +129,16 @@ trap 'rm -f "$temp_cc" "$temp_cxx"' EXIT compile_cc () { ${CC} -I"$include_dir" \ - ${PEDANTIC_CPPFLAGS} ${CPPFLAGS} ${EXTRA_CPPFLAGS} \ - ${PEDANTIC_CFLAGS} ${CFLAGS} ${EXTRA_CFLAGS} \ + ${PEDANTIC_CPPFLAGS} ${CPPFLAGS} \ + ${PEDANTIC_CFLAGS} ${CFLAGS} \ -c -o /dev/null "${temp_cc}" } compile_cxx () { ${CXX} -I"$include_dir" \ - ${PEDANTIC_CPPFLAGS} ${CPPFLAGS} ${EXTRA_CPPFLAGS} \ - ${PEDANTIC_CXXFLAGS} ${CXXFLAGS} ${EXTRA_CXXFLAGS} \ + ${PEDANTIC_CPPFLAGS} ${CPPFLAGS} \ + ${PEDANTIC_CXXFLAGS} ${CXXFLAGS} \ -c -o /dev/null "${temp_cxx}" }
Signature · 1 line
2.28.0
PATCH v4 15/31 app: remove references to make-based config
In reply to Thomas MonjalonFrom: Ciara Power <[email protected]>
Make is no longer supported, RTE_SDK, RTE_TARGET and CONFIG options are no longer in use.
--- app/test-bbdev/test-bbdev.py | 11 +---- app/test/test_cryptodev.c | 89 +++++++++------------------------- app/test/test_cryptodev_asym.c | 18 ++----- 3 files changed, 28 insertions(+), 90 deletions(-)
app/test-bbdev/test-bbdev.py +2 -9
@@ -20,15 +20,8 @@ def kill(process): print("WARNING: Python 2 is deprecated for use in DPDK, and will not work in future releases.", file=sys.stderr) print("Please use Python 3 instead", file=sys.stderr) -if "RTE_SDK" in os.environ: - dpdk_path = os.environ["RTE_SDK"] -else: - dpdk_path = "../.." - -if "RTE_TARGET" in os.environ: - dpdk_target = os.environ["RTE_TARGET"] -else: - dpdk_target = "x86_64-native-linux-gcc" +dpdk_path = "../.." +dpdk_target = "build" parser = argparse.ArgumentParser( description='BBdev Unit Test Application',
app/test/test_cryptodev.c +22 -67
220 lines not on this page · raw message
app/test/test_cryptodev_asym.c +4 -14
@@ -2336,9 +2336,7 @@ test_cryptodev_openssl_asym(void) RTE_STR(CRYPTODEV_NAME_OPENSSL_PMD));if (gbl_driver_id ==-1 ) { -RTE_LOG (ERR ,USER1 ,"OPENSSL PMD must be loaded. Check if " -"CONFIG_RTE_LIBRTE_PMD_OPENSSL is enabled " -"in config file to run this testsuite.\n" ); +RTE_LOG (ERR ,USER1 ,"OPENSSL PMD must be loaded.\n" );return TEST_FAILED ; }
@@ -2352,9 +2350,7 @@ test_cryptodev_qat_asym(void) RTE_STR(CRYPTODEV_NAME_QAT_ASYM_PMD));if (gbl_driver_id ==-1 ) { -RTE_LOG (ERR ,USER1 ,"QAT PMD must be loaded. Check if " -"CONFIG_RTE_LIBRTE_PMD_QAT_ASYM is enabled " -"in config file to run this testsuite.\n" ); +RTE_LOG (ERR ,USER1 ,"QAT PMD must be loaded.\n" );return TEST_FAILED ; }
@@ -2367,10 +2363,7 @@ test_cryptodev_octeontx_asym(void) gbl_driver_id =rte_cryptodev_driver_id_get (RTE_STR (CRYPTODEV_NAME_OCTEONTX_SYM_PMD ));if (gbl_driver_id ==-1 ) { -RTE_LOG (ERR ,USER1 ,"OCTEONTX PMD must be loaded. Check if " -"CONFIG_RTE_LIBRTE_PMD_OCTEONTX_CRYPTO is " -"enabled in config file to run this " -"testsuite.\n" ); +RTE_LOG (ERR ,USER1 ,"OCTEONTX PMD must be loaded.\n" );return TEST_FAILED ; }return unit_test_suite_runner (&cryptodev_octeontx_asym_testsuite);
@@ -2382,10 +2375,7 @@ test_cryptodev_octeontx2_asym(void) gbl_driver_id =rte_cryptodev_driver_id_get (RTE_STR (CRYPTODEV_NAME_OCTEONTX2_PMD ));if (gbl_driver_id ==-1 ) { -RTE_LOG (ERR ,USER1 ,"OCTEONTX2 PMD must be loaded. Check if " -"CONFIG_RTE_LIBRTE_PMD_OCTEONTX2_CRYPTO is " -"enabled in config file to run this " -"testsuite.\n" ); +RTE_LOG (ERR ,USER1 ,"OCTEONTX2 PMD must be loaded.\n" );return TEST_FAILED ; }
Signature · 1 line
2.28.0
Re: [dpdk-dev] [PATCH v4 15/31] app: remove references to make-based config
Quoted 11 lines · Thomas Monjalon
From: Ciara Power <[email protected]>
Make is no longer supported,
RTE_SDK,RTE_TARGETand CONFIG options are no longer in use.Signed-off-by Ciara Power <[email protected]>--- app/test-bbdev/test-bbdev.py | 11 +---- app/test/test_cryptodev.c | 89 +++++++++------------------------- app/test/test_cryptodev_asym.c | 18 ++----- 3 files changed, 28 insertions(+), 90 deletions(-)
[...]
PATCH v4 16/31 doc: remove references to make from Linux guide
In reply to Thomas MonjalonFrom: Ciara Power <[email protected]>
Make is no longer supported for compiling DPDK, references are now removed in the documentation.
--- doc/guides/linux_gsg/build_dpdk.rst | 16 +++++++++++----- doc/guides/linux_gsg/build_sample_apps.rst | 18 +++--------------- doc/guides/linux_gsg/enable_func.rst | 13 +++++-------- doc/guides/linux_gsg/linux_drivers.rst | 18 +++++++++++------- doc/guides/linux_gsg/sys_reqs.rst | 6 +----- 5 files changed, 31 insertions(+), 40 deletions(-)
doc/guides/linux_gsg/build_dpdk.rst +11 -5
@@ -76,6 +76,8 @@ and the last step causing the dynamic loader `ld.so` to update its cache to take distributions, `/usr/local/lib` and `/usr/local/lib64` should be added to a file in `/etc/ld.so.conf.d/` before running `ldconfig`. +.. _adjusting_build_options: + Adjusting Build Options ~~~~~~~~~~~~~~~~~~~~~~~
@@ -112,6 +114,9 @@ dependencies are met on the current system are built. When `-Dexamples=all` is set as a meson option, meson will check each example application to see if it can be built, and add all which can be built to the list of tasks in the ninja build configuration file. +.. _building_app_using_installed_dpdk: + + Building Applications Using Installed DPDK ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -135,11 +140,12 @@ and the sources for that build are stored in ``$(SRCS-y)``. .. note:: - Unlike with the older make build system, the meson system is not - designed to be used directly from a build directory. Instead it is - recommended that it be installed either system-wide or to a known - location in the user's home directory. The install location can be set - using the `--prefix` meson option (default: `/usr/local`). + Unlike with the make build system present used in older DPDK releases, + the meson system is not designed to be used directly from a build + directory. Instead it is recommended that it be installed either + system-wide or to a known location in the user's home directory. + The install location can be set using the `--prefix` meson option + (default: `/usr/local`). an equivalent build recipe for a simple DPDK application using meson as a build system is shown below:
doc/guides/linux_gsg/build_sample_apps.rst +3 -15
@@ -1,7 +1,7 @@ .. SPDX-License-Identifier: BSD-3-Clause Copyright(c) 2010-2014 Intel Corporation. -Compiling and Running Sample Applications +Running Sample Applications ========================================= The chapter describes how to compile and run applications in an DPDK environment.
@@ -119,7 +119,7 @@ Copy the DPDK application binary to your target, then run the application as fol (assuming the platform has four memory channels per processor socket, and that cores 0-3 are present and are to be used for running the application):: - ./helloworld -l 0-3 -n 4 + ./dpdk-helloworld -l 0-3 -n 4 .. note::
@@ -183,19 +183,7 @@ If the DPDK cannot allocate enough memory on each socket, the EAL initialization Additional Sample Applications ------------------------------ -Additional sample applications are included in the ${RTE_SDK}/examples directory. +Additional sample applications are included in the DPDK examples directory. These sample applications may be built and run in a manner similar to that described in earlier sections in this manual. In addition, see the *DPDK Sample Applications User Guide* for a description of the application, specific instructions on compilation and execution and some explanation of the code. - -Additional Test Applications ----------------------------- - -In addition, there are two other applications that are built when the libraries are created. -The source files for these are in the DPDK/app directory and are called test and testpmd. -Once the libraries are created, they can be found in the build/app directory. - -* The test application provides a variety of specific tests for the various functions in the DPDK. - -* The testpmd application provides a number of different packet throughput tests and - examples of features such as how to use the Flow Director found in the Intel® 82599 10 Gigabit Ethernet Controller.
doc/guides/linux_gsg/enable_func.rst +5 -8
@@ -41,7 +41,9 @@ Enabling HPET in the DPDK ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ By default, HPET support is disabled in the DPDK build configuration files. -To use HPET, the ``CONFIG_RTE_LIBEAL_USE_HPET`` setting should be changed to ``y``, which will enable the HPET settings at compile time. +To use HPET, use the following meson build option which will enable the HPET settings at compile time:: + + meson configure -Duse_hpet=true For an application to use the ``rte_get_hpet_cycles()`` and ``rte_get_hpet_hz()`` API calls, and optionally to make the HPET the default time source for the rte_timer library,
@@ -128,13 +130,8 @@ Loading the DPDK KNI Kernel Module ---------------------------------- To run the DPDK Kernel NIC Interface (KNI) sample application, an extra kernel module (the kni module) must be loaded into the running kernel. -The module is found in the kmod sub-directory of the DPDK target directory. -Similar to the loading of the ``igb_uio`` module, this module should be loaded using the insmod command as shown below -(assuming that the current directory is the DPDK target directory): - -.. code-block:: console - - insmod kmod/rte_kni.ko +The module is found in the kernel/linux sub-directory of the DPDK build directory. +This can be enabled in the same way as the ``igb_uio`` module, please see :ref:`load_uio` for details. .. note::
doc/guides/linux_gsg/linux_drivers.rst +11 -7
@@ -12,6 +12,9 @@ Different PMDs may require different kernel drivers in order to work properly. Depends on the PMD being used, a corresponding kernel driver should be load and bind to the network ports. +.. _load_uio: + + UIO ---
@@ -28,19 +31,20 @@ can provide the uio capability. This module can be loaded using the command: ``uio_pci_generic`` module doesn't support the creation of virtual functions. As an alternative to the ``uio_pci_generic``, the DPDK also includes the igb_uio -module which can be found in the kmod subdirectory referred to above. It can +module which can be found in the kernel/linux subdirectory referred to above. It can be loaded as shown below: .. code-block:: console sudo modprobe uio - sudo insmod kmod/igb_uio.ko + sudo insmod <build_dir>/kernel/linux/igb_uio/igb_uio.ko .. note:: - ``igb_uio`` module is disabled by default starting from ``DPDK v20.02``. - To build it, the config option ``CONFIG_RTE_EAL_IGB_UIO`` should be enabled. - It is planned to move ``igb_uio`` module to a different git repository. + Building DPDK Linux kernel modules is disabled by default starting from DPDK v20.02. + To enable them again, the config option "enable_kmods" needs to be set in the meson + build configuration. See :ref:`adjusting_build_options` for details on how to set/clear + build options. It is planned to move ``igb_uio`` module to a different git repository. .. note::
@@ -104,11 +108,11 @@ parameter ``--vfio-vf-token``. 3. echo 2 > /sys/bus/pci/devices/0000:86:00.0/sriov_numvfs 4. Start the PF: - ./x86_64-native-linux-gcc/app/testpmd -l 22-25 -n 4 -w 86:00.0 \ + ./<build_dir>/app/dpdk-testpmd -l 22-25 -n 4 -w 86:00.0 \ --vfio-vf-token=14d63f20-8445-11ea-8900-1f9ce7d5650d --file-prefix=pf -- -i 5. Start the VF: - ./x86_64-native-linux-gcc/app/testpmd -l 26-29 -n 4 -w 86:02.0 \ + ./<build_dir>/app/dpdk-testpmd -l 26-29 -n 4 -w 86:02.0 \ --vfio-vf-token=14d63f20-8445-11ea-8900-1f9ce7d5650d --file-prefix=vf0 -- -i Also, to use VFIO, both kernel and BIOS must support and be configured to use IO virtualization (such as Intel® VT-d).
doc/guides/linux_gsg/sys_reqs.rst +1 -5
@@ -43,11 +43,7 @@ Compilation of the DPDK * For Ubuntu/Debian systems these can be installed using ``apt install build-essential`` -* Python, recommended version 3.5+. - - * Python v3.5+ is needed to build DPDK using meson and ninja - - * Python 2.7+ or 3.2+, to use various helper scripts included in the DPDK package. +* Python, v3.5 or later. * Meson (version 0.47.1+) and ninja
Signature · 1 line
2.28.0
PATCH v4 17/31 doc: remove references to make from FreeBSD guide
In reply to Thomas MonjalonFrom: Ciara Power <[email protected]>
Make is no longer supported for compiling DPDK, references are now removed in the documentation.
--- doc/guides/freebsd_gsg/build_dpdk.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
doc/guides/freebsd_gsg/build_dpdk.rst +1 -1
@@ -122,7 +122,7 @@ up time. This can be achieved by placing lines similar to the following into An error such as:: - kldload: can't load ./x86_64-native-freebsd-gcc/kmod/contigmem.ko: + kldload: can't load ./<build_dir>/kernel/freebsd/contigmem.ko: Exec format error is generally attributed to not having enough contiguous memory
Signature · 1 line
2.28.0
PATCH v4 18/31 doc: remove references to make from howto guides
In reply to Thomas MonjalonFrom: Ciara Power <[email protected]>
Make is no longer supported for compiling DPDK, references are now removed in the documentation.
--- doc/guides/howto/lm_bond_virtio_sriov.rst | 4 +-- doc/guides/howto/lm_virtio_vhost_user.rst | 4 +-- doc/guides/howto/packet_capture_framework.rst | 21 +++------------ doc/guides/howto/pvp_reference_benchmark.rst | 27 +++++-------------- doc/guides/howto/vfd.rst | 4 +-- .../virtio_user_for_container_networking.rst | 2 +- 6 files changed, 16 insertions(+), 46 deletions(-)
doc/guides/howto/lm_bond_virtio_sriov.rst +2 -2
@@ -591,7 +591,7 @@ Set up DPDK in the Virtual Machine rmmod virtio-pci ixgbevf modprobe uio - insmod /root/dpdk/x86_64-default-linux-gcc/kmod/igb_uio.ko + insmod /root/dpdk/<build_dir>/kernel/linux/igb_uio/igb_uio.ko /root/dpdk/usertools/dpdk-devbind.py -b igb_uio 0000:00:03.0 /root/dpdk/usertools/dpdk-devbind.py -b igb_uio 0000:00:04.0
@@ -613,7 +613,7 @@ Run testpmd in the Virtual Machine. # use for bonding of virtio and vf tests in VM - /root/dpdk/x86_64-default-linux-gcc/app/testpmd \ + /root/dpdk/<build_dir>/app/dpdk-testpmd \ -l 0-3 -n 4 --socket-mem 350 -- --i --port-topology=chained .. _lm_bond_virtio_sriov_switch_conf:
doc/guides/howto/lm_virtio_vhost_user.rst +2 -2
@@ -421,7 +421,7 @@ setup_dpdk_virtio_in_vm.sh rmmod virtio-pci modprobe uio - insmod /root/dpdk/x86_64-default-linux-gcc/kmod/igb_uio.ko + insmod /root/dpdk/<build_dir>/kernel/linux/igb_uio/igb_uio.ko /root/dpdk/usertools/dpdk-devbind.py -b igb_uio 0000:00:03.0 /root/dpdk/usertools/dpdk-devbind.py -b igb_uio 0000:00:04.0
@@ -437,5 +437,5 @@ run_testpmd_in_vm.sh # Run testpmd for use with vhost_user sample app. # test system has 8 cpus (0-7), use cpus 2-7 for VM - /root/dpdk/x86_64-default-linux-gcc/app/testpmd \ + /root/dpdk/<build_dir>/app/dpdk-testpmd \ -l 0-5 -n 4 --socket-mem 350 -- --burst=64 --i
doc/guides/howto/packet_capture_framework.rst +3 -18
@@ -52,11 +52,7 @@ Some things to note: initialization code. Refer to the ``app/test-pmd/testpmd.c`` code and look for ``pdump`` keyword to see how this is done. -* The ``dpdk-pdump`` tool depends on the libpcap based PMD which is disabled - by default in the build configuration files, owing to an external dependency - on the libpcap development files. Once the libpcap development files are - installed, the libpcap based PMD can be enabled by setting - ``CONFIG_RTE_LIBRTE_PMD_PCAP=y`` and recompiling the DPDK. +* The ``dpdk-pdump`` tool depends on the libpcap based PMD. Test Environment
@@ -73,17 +69,6 @@ for packet capturing on the DPDK port in Packet capturing on a DPDK port using the dpdk-pdump tool. -Configuration -------------- - -Modify the DPDK primary application to initialize the packet capture framework -as mentioned in the above notes and enable the following config options and -build DPDK:: - - CONFIG_RTE_LIBRTE_PMD_PCAP=y - CONFIG_RTE_LIBRTE_PDUMP=y - - Running the Application -----------------------
@@ -93,11 +78,11 @@ inspect them using ``tcpdump``. #. Launch testpmd as the primary application:: - sudo ./app/testpmd -c 0xf0 -n 4 -- -i --port-topology=chained + sudo ./<build_dir>/app/dpdk-testpmd -c 0xf0 -n 4 -- -i --port-topology=chained #. Launch the pdump tool as follows:: - sudo ./build/app/dpdk-pdump -- \ + sudo ./<build_dir>/app/dpdk-pdump -- \ --pdump 'port=0,queue=*,rx-dev=/tmp/capture.pcap' #. Send traffic to dpdk_port0 from traffic generator.
doc/guides/howto/pvp_reference_benchmark.rst +6 -21
@@ -99,14 +99,7 @@ Build Qemu: DPDK build ~~~~~~~~~~ -Build DPDK: - - .. code-block:: console - - git clone git://dpdk.org/dpdk - cd dpdk - export RTE_SDK=$PWD - make install T=x86_64-native-linux-gcc DESTDIR=install +See :doc:`../linux_gsg/build_dpdk` for details. Testpmd launch
@@ -117,7 +110,7 @@ Testpmd launch .. code-block:: console modprobe vfio-pci - $RTE_SDK/install/sbin/dpdk-devbind -b vfio-pci 0000:11:00.0 0000:11:00.1 + ./dpdk/usertools/dpdk-devbind -b vfio-pci 0000:11:00.0 0000:11:00.1 .. Note::
@@ -129,7 +122,7 @@ Testpmd launch .. code-block:: console - $RTE_SDK/install/bin/testpmd -l 0,2,3,4,5 --socket-mem=1024 -n 4 \ + ./dpdk/<build_dir>/app/dpdk-testpmd -l 0,2,3,4,5 --socket-mem=1024 -n 4 \ --vdev 'net_vhost0,iface=/tmp/vhost-user1' \ --vdev 'net_vhost1,iface=/tmp/vhost-user2' -- \ --portmask=f -i --rxq=1 --txq=1 \
@@ -309,18 +302,10 @@ Guest tuning echo "obase=16;$(( 0x$(cat $i) & ~$clear_mask ))" | bc > $i done - DPDK build ~~~~~~~~~~ -Build DPDK: - - .. code-block:: console - - git clone git://dpdk.org/dpdk - cd dpdk - export RTE_SDK=$PWD - make install T=x86_64-native-linux-gcc DESTDIR=install +See :doc:`../linux_gsg/build_dpdk` for details. Testpmd launch
@@ -340,13 +325,13 @@ Bind the virtio-net devices to DPDK: .. code-block:: console - $RTE_SDK/usertools/dpdk-devbind.py -b vfio-pci 0000:00:10.0 0000:00:11.0 + ./dpdk/usertools/dpdk-devbind.py -b vfio-pci 0000:00:10.0 0000:00:11.0 Start testpmd: .. code-block:: console - $RTE_SDK/install/bin/testpmd -l 0,1,2 --socket-mem 1024 -n 4 \ + ./dpdk/<build_dir>/app/dpdk-testpmd -l 0,1,2 --socket-mem 1024 -n 4 \ --proc-type auto --file-prefix pg -- \ --portmask=3 --forward-mode=macswap --port-topology=chained \ --disable-rss -i --rxq=1 --txq=1 \
doc/guides/howto/vfd.rst +2 -2
@@ -83,7 +83,7 @@ The typical procedure to achieve this is as follows: #. Run a DPDK application on the PF in the host:: - testpmd -l 0-7 -n 4 -- -i --txqflags=0 + dpdk-testpmd -l 0-7 -n 4 -- -i --txqflags=0 #. Bind the VF port to ``igb_uio`` in the VM::
@@ -91,7 +91,7 @@ The typical procedure to achieve this is as follows: #. Run a DPDK application on the VF in the VM:: - testpmd -l 0-7 -n 4 -- -i --txqflags=0 + dpdk-testpmd -l 0-7 -n 4 -- -i --txqflags=0 Common functions of IXGBE and I40E
doc/guides/howto/virtio_user_for_container_networking.rst +1 -1
@@ -64,7 +64,7 @@ some minor changes. FROM ubuntu:latest WORKDIR /usr/src/dpdk COPY . /usr/src/dpdk - ENV PATH "$PATH:/usr/src/dpdk/x86_64-native-linux-gcc/app/" + ENV PATH "$PATH:/usr/src/dpdk/<build_dir>/app/" EOT #. Build a Docker image.
Signature · 1 line
2.28.0
Re: [dpdk-dev] [PATCH v4 18/31] doc: remove references to make from howto guides
Quoted 15 lines · Thomas Monjalon
From: Ciara Power <[email protected]>
Make is no longer supported for compiling DPDK, references are now removed in the documentation.
Signed-off-by Ciara Power <[email protected]>--- doc/guides/howto/lm_bond_virtio_sriov.rst | 4 +-- doc/guides/howto/lm_virtio_vhost_user.rst | 4 +-- doc/guides/howto/packet_capture_framework.rst | 21 +++------------ doc/guides/howto/pvp_reference_benchmark.rst | 27 +++++-------------- doc/guides/howto/vfd.rst | 4 +-- .../virtio_user_for_container_networking.rst | 2 +- 6 files changed, 16 insertions(+), 46 deletions(-)
[...]