Patch Detail
get:
Show a patch.
patch:
Update a patch.
put:
Update a patch.
GET /api/patches/76443/?format=api
{ "id": 76443, "url": "http://patches.dpdk.org/api/patches/76443/?format=api", "web_url": "http://patches.dpdk.org/project/dpdk/patch/20200903152717.42095-34-ciara.power@intel.com/", "project": { "id": 1, "url": "http://patches.dpdk.org/api/projects/1/?format=api", "name": "DPDK", "link_name": "dpdk", "list_id": "dev.dpdk.org", "list_email": "dev@dpdk.org", "web_url": "http://core.dpdk.org", "scm_url": "git://dpdk.org/dpdk", "webscm_url": "http://git.dpdk.org/dpdk", "list_archive_url": "https://inbox.dpdk.org/dev", "list_archive_url_format": "https://inbox.dpdk.org/dev/{}", "commit_url_format": "" }, "msgid": "<20200903152717.42095-34-ciara.power@intel.com>", "list_archive_url": "https://inbox.dpdk.org/dev/20200903152717.42095-34-ciara.power@intel.com", "date": "2020-09-03T15:27:13", "name": "[v3,33/37] doc: remove references to make in sample app guides", "commit_ref": null, "pull_url": null, "state": "superseded", "archived": true, "hash": "22b7d46e18f11e6bc5de8de416c1c88f28758877", "submitter": { "id": 978, "url": "http://patches.dpdk.org/api/people/978/?format=api", "name": "Power, Ciara", "email": "ciara.power@intel.com" }, "delegate": { "id": 1, "url": "http://patches.dpdk.org/api/users/1/?format=api", "username": "tmonjalo", "first_name": "Thomas", "last_name": "Monjalon", "email": "thomas@monjalon.net" }, "mbox": "http://patches.dpdk.org/project/dpdk/patch/20200903152717.42095-34-ciara.power@intel.com/mbox/", "series": [ { "id": 11929, "url": "http://patches.dpdk.org/api/series/11929/?format=api", "web_url": "http://patches.dpdk.org/project/dpdk/list/?series=11929", "date": "2020-09-03T15:26:40", "name": "remove make support in DPDK", "version": 3, "mbox": "http://patches.dpdk.org/series/11929/mbox/" } ], "comments": "http://patches.dpdk.org/api/patches/76443/comments/", "check": "success", "checks": "http://patches.dpdk.org/api/patches/76443/checks/", "tags": {}, "related": [], "headers": { "Return-Path": "<dev-bounces@dpdk.org>", "X-Original-To": "patchwork@inbox.dpdk.org", "Delivered-To": "patchwork@inbox.dpdk.org", "Received": [ "from dpdk.org (dpdk.org [92.243.14.124])\n\tby inbox.dpdk.org (Postfix) with ESMTP id 30EB6A04BF;\n\tThu, 3 Sep 2020 17:36:56 +0200 (CEST)", "from [92.243.14.124] (localhost [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id 5144D1C10C;\n\tThu, 3 Sep 2020 17:29:50 +0200 (CEST)", "from mga07.intel.com (mga07.intel.com [134.134.136.100])\n by dpdk.org (Postfix) with ESMTP id D25841C0DB\n for <dev@dpdk.org>; Thu, 3 Sep 2020 17:29:47 +0200 (CEST)", "from orsmga006.jf.intel.com ([10.7.209.51])\n by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;\n 03 Sep 2020 08:29:46 -0700", "from silpixa00399953.ir.intel.com (HELO\n silpixa00399953.ger.corp.intel.com) ([10.237.222.53])\n by orsmga006.jf.intel.com with ESMTP; 03 Sep 2020 08:29:38 -0700" ], "IronPort-SDR": [ "\n hFuxkuz1jtFsqJim6ynB2hX5ytbX5kIOk+e7PqHZJCzgogpiEG1dAStkmh6uGMGnZUgOGBp4ES\n GVZSlG7rqDNw==", "\n 6YtNqQWi6/aVNc1DKhSSPAszFkFGnTqzMiVhihddk/y/pxmUCAbq6NuFk23XGV4mc08DRb0Ila\n F7Qiv+PKgtlA==" ], "X-IronPort-AV": [ "E=McAfee;i=\"6000,8403,9733\"; a=\"221808786\"", "E=Sophos;i=\"5.76,387,1592895600\"; d=\"scan'208\";a=\"221808786\"", "E=Sophos;i=\"5.76,387,1592895600\"; d=\"scan'208\";a=\"302244261\"" ], "X-Amp-Result": "SKIPPED(no attachment in message)", "X-Amp-File-Uploaded": "False", "X-ExtLoop1": "1", "From": "Ciara Power <ciara.power@intel.com>", "To": "dev@dpdk.org", "Cc": "Ciara Power <ciara.power@intel.com>,\n Nicolas Chautru <nicolas.chautru@intel.com>,\n John McNamara <john.mcnamara@intel.com>,\n Marko Kovacevic <marko.kovacevic@intel.com>,\n Olivier Matz <olivier.matz@6wind.com>, David Hunt <david.hunt@intel.com>,\n Ori Kam <orika@mellanox.com>,\n Bruce Richardson <bruce.richardson@intel.com>,\n Radu Nicolau <radu.nicolau@intel.com>, Akhil Goyal <akhil.goyal@nxp.com>,\n Tomasz Kantecki <tomasz.kantecki@intel.com>,\n Sunil Kumar Kori <skori@marvell.com>,\n Pavan Nikhilesh <pbhagavatula@marvell.com>,\n Harry van Haaren <harry.van.haaren@intel.com>,\n Bernard Iremonger <bernard.iremonger@intel.com>,\n Konstantin Ananyev <konstantin.ananyev@intel.com>,\n Cristian Dumitrescu <cristian.dumitrescu@intel.com>,\n Ferruh Yigit <ferruh.yigit@intel.com>, Jerin Jacob <jerinj@marvell.com>,\n Kiran Kumar K <kirankumark@marvell.com>,\n Nithin Dabilpuram <ndabilpuram@marvell.com>,\n Anatoly Burakov <anatoly.burakov@intel.com>,\n Xiaoyun Li <xiaoyun.li@intel.com>, Jingjing Wu <jingjing.wu@intel.com>,\n Reshma Pattan <reshma.pattan@intel.com>,\n Kirill Rybalchenko <kirill.rybalchenko@intel.com>,\n Jasvinder Singh <jasvinder.singh@intel.com>,\n Byron Marohn <byron.marohn@intel.com>,\n Yipeng Wang <yipeng1.wang@intel.com>, Robert Sanford <rsanford@akamai.com>,\n Erik Gabriel Carrillo <erik.g.carrillo@intel.com>,\n Maxime Coquelin <maxime.coquelin@redhat.com>,\n Chenbo Xia <chenbo.xia@intel.com>, Zhihong Wang <zhihong.wang@intel.com>", "Date": "Thu, 3 Sep 2020 16:27:13 +0100", "Message-Id": "<20200903152717.42095-34-ciara.power@intel.com>", "X-Mailer": "git-send-email 2.17.1", "In-Reply-To": "<20200903152717.42095-1-ciara.power@intel.com>", "References": "<20200807123009.21266-1-ciara.power@intel.com>\n <20200903152717.42095-1-ciara.power@intel.com>", "MIME-Version": "1.0", "Content-Type": "text/plain; charset=UTF-8", "Content-Transfer-Encoding": "8bit", "Subject": "[dpdk-dev] [PATCH v3 33/37] doc: remove references to make in\n\tsample app guides", "X-BeenThere": "dev@dpdk.org", "X-Mailman-Version": "2.1.15", "Precedence": "list", "List-Id": "DPDK patches and discussions <dev.dpdk.org>", "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n <mailto:dev-request@dpdk.org?subject=unsubscribe>", "List-Archive": "<http://mails.dpdk.org/archives/dev/>", "List-Post": "<mailto:dev@dpdk.org>", "List-Help": "<mailto:dev-request@dpdk.org?subject=help>", "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n <mailto:dev-request@dpdk.org?subject=subscribe>", "Errors-To": "dev-bounces@dpdk.org", "Sender": "\"dev\" <dev-bounces@dpdk.org>" }, "content": "Make is no longer supported for compiling DPDK, references are now\nremoved in the documentation.\n\nSigned-off-by: Ciara Power <ciara.power@intel.com>\n---\n doc/guides/sample_app_ug/bbdev_app.rst | 34 ++------\n doc/guides/sample_app_ug/cmd_line.rst | 2 +-\n doc/guides/sample_app_ug/compiling.rst | 83 +++++++------------\n doc/guides/sample_app_ug/dist_app.rst | 4 +-\n doc/guides/sample_app_ug/ethtool.rst | 2 +-\n .../sample_app_ug/eventdev_pipeline.rst | 3 +-\n doc/guides/sample_app_ug/fips_validation.rst | 10 +--\n doc/guides/sample_app_ug/flow_classify.rst | 4 +-\n doc/guides/sample_app_ug/flow_filtering.rst | 25 +-----\n doc/guides/sample_app_ug/hello_world.rst | 2 +-\n doc/guides/sample_app_ug/ioat.rst | 6 +-\n doc/guides/sample_app_ug/ip_frag.rst | 6 +-\n doc/guides/sample_app_ug/ip_pipeline.rst | 4 +-\n doc/guides/sample_app_ug/ip_reassembly.rst | 9 +-\n doc/guides/sample_app_ug/ipsec_secgw.rst | 14 +---\n doc/guides/sample_app_ug/ipv4_multicast.rst | 4 +-\n doc/guides/sample_app_ug/keep_alive.rst | 4 +-\n .../sample_app_ug/kernel_nic_interface.rst | 14 ++--\n doc/guides/sample_app_ug/l2_forward_cat.rst | 4 +-\n .../sample_app_ug/l2_forward_crypto.rst | 4 +-\n doc/guides/sample_app_ug/l2_forward_event.rst | 10 +--\n .../sample_app_ug/l2_forward_job_stats.rst | 4 +-\n .../sample_app_ug/l2_forward_real_virtual.rst | 6 +-\n doc/guides/sample_app_ug/l3_forward.rst | 10 +--\n .../sample_app_ug/l3_forward_access_ctrl.rst | 6 +-\n doc/guides/sample_app_ug/l3_forward_graph.rst | 4 +-\n .../sample_app_ug/l3_forward_power_man.rst | 14 ++--\n doc/guides/sample_app_ug/link_status_intr.rst | 4 +-\n doc/guides/sample_app_ug/multi_process.rst | 20 ++---\n doc/guides/sample_app_ug/ntb.rst | 2 +-\n doc/guides/sample_app_ug/packet_ordering.rst | 3 +-\n .../sample_app_ug/performance_thread.rst | 44 +++-------\n doc/guides/sample_app_ug/ptpclient.rst | 9 +-\n doc/guides/sample_app_ug/qos_metering.rst | 2 +-\n doc/guides/sample_app_ug/qos_scheduler.rst | 10 +--\n doc/guides/sample_app_ug/rxtx_callbacks.rst | 9 +-\n doc/guides/sample_app_ug/server_node_efd.rst | 2 +-\n doc/guides/sample_app_ug/service_cores.rst | 23 +----\n doc/guides/sample_app_ug/skeleton.rst | 2 +-\n doc/guides/sample_app_ug/tep_termination.rst | 43 +++-------\n doc/guides/sample_app_ug/test_pipeline.rst | 4 +-\n doc/guides/sample_app_ug/timer.rst | 2 +-\n doc/guides/sample_app_ug/vdpa.rst | 4 +-\n doc/guides/sample_app_ug/vhost.rst | 11 +--\n doc/guides/sample_app_ug/vhost_blk.rst | 2 +-\n doc/guides/sample_app_ug/vhost_crypto.rst | 2 +-\n .../sample_app_ug/vm_power_management.rst | 34 ++++----\n .../sample_app_ug/vmdq_dcb_forwarding.rst | 8 +-\n doc/guides/sample_app_ug/vmdq_forwarding.rst | 8 +-\n 49 files changed, 194 insertions(+), 346 deletions(-)", "diff": "diff --git a/doc/guides/sample_app_ug/bbdev_app.rst b/doc/guides/sample_app_ug/bbdev_app.rst\nindex 405e706a46..764155f983 100644\n--- a/doc/guides/sample_app_ug/bbdev_app.rst\n+++ b/doc/guides/sample_app_ug/bbdev_app.rst\n@@ -31,30 +31,12 @@ Limitations\n Compiling the Application\n -------------------------\n \n-#. DPDK needs to be built with ``baseband_turbo_sw`` PMD driver enabled along\n- with ``FLEXRAN SDK`` Libraries. Refer to *SW Turbo Poll Mode Driver*\n- documentation for more details on this.\n+DPDK needs to be built with ``baseband_turbo_sw`` PMD driver enabled along\n+with ``FLEXRAN SDK`` Libraries. Refer to *SW Turbo Poll Mode Driver*\n+documentation for more details on this.\n \n-#. Go to the example directory:\n+To compile the sample application see :doc:`compiling`.\n \n- .. code-block:: console\n-\n- export RTE_SDK=/path/to/rte_sdk\n- cd ${RTE_SDK}/examples/bbdev_app\n-\n-#. Set the target (a default target is used if not specified). For example:\n-\n- .. code-block:: console\n-\n- export RTE_TARGET=x86_64-native-linux-gcc\n-\n- See the *DPDK Getting Started Guide* for possible RTE_TARGET values.\n-\n-#. Build the application:\n-\n- .. code-block:: console\n-\n- make\n \n Running the Application\n -----------------------\n@@ -63,8 +45,8 @@ The application accepts a number of command line options:\n \n .. code-block:: console\n \n- $ ./build/bbdev [EAL options] -- [-e ENCODING_CORES] [-d DECODING_CORES] /\n- [-p ETH_PORT_ID] [-b BBDEV_ID]\n+ $ ./<build_dir>/examples/dpdk-bbdev [EAL options] -- [-e ENCODING_CORES] /\n+ [-d DECODING_CORES] [-p ETH_PORT_ID] [-b BBDEV_ID]\n \n where:\n \n@@ -84,8 +66,8 @@ issue the command:\n \n .. code-block:: console\n \n- $ ./build/bbdev --vdev='baseband_turbo_sw' -w <NIC0PCIADDR> -c 0x38 --socket-mem=2,2 \\\n- --file-prefix=bbdev -- -e 0x10 -d 0x20\n+ $ ./<build_dir>/examples/dpdk-bbdev --vdev='baseband_turbo_sw' -w <NIC0PCIADDR> \\\n+ -c 0x38 --socket-mem=2,2 --file-prefix=bbdev -- -e 0x10 -d 0x20\n \n where, NIC0PCIADDR is the PCI address of the Rx port\n \ndiff --git a/doc/guides/sample_app_ug/cmd_line.rst b/doc/guides/sample_app_ug/cmd_line.rst\nindex 6deb6c8112..5e3a25a317 100644\n--- a/doc/guides/sample_app_ug/cmd_line.rst\n+++ b/doc/guides/sample_app_ug/cmd_line.rst\n@@ -52,7 +52,7 @@ To run the application in linux environment, issue the following command:\n \n .. code-block:: console\n \n- $ ./build/cmdline -l 0-3 -n 4\n+ $ ./<build_dir>/examples/dpdk-cmdline -l 0-3 -n 4\n \n Refer to the *DPDK Getting Started Guide* for general information on running applications\n and the Environment Abstraction Layer (EAL) options.\ndiff --git a/doc/guides/sample_app_ug/compiling.rst b/doc/guides/sample_app_ug/compiling.rst\nindex 6f04743c82..adde775d4e 100644\n--- a/doc/guides/sample_app_ug/compiling.rst\n+++ b/doc/guides/sample_app_ug/compiling.rst\n@@ -9,100 +9,75 @@ This section explains how to compile the DPDK sample applications.\n To compile all the sample applications\n --------------------------------------\n \n-Set the path to DPDK source code if its not set:\n+Go to DPDK build directory:\n \n .. code-block:: console\n \n- export RTE_SDK=/path/to/rte_sdk\n+ cd dpdk/<build_dir>\n \n-Go to DPDK source:\n-\n- .. code-block:: console\n-\n- cd $RTE_SDK\n-\n-Build DPDK:\n+Enable examples compilation:\n \n .. code-block:: console\n \n- make defconfig\n- make\n+ meson configure -Dexamples=all\n \n-Build the sample applications:\n+Build:\n \n .. code-block:: console\n \n- export RTE_TARGET=build\n- make -C examples\n+ ninja\n \n-For other possible ``RTE_TARGET`` values and additional information on\n-compiling see\n+For additional information on compiling see\n :ref:`Compiling DPDK on Linux <linux_gsg_compiling_dpdk>` or\n :ref:`Compiling DPDK on FreeBSD <building_from_source>`.\n-Applications are output to: ``$RTE_SDK/examples/app-dir/build`` or\n-``$RTE_SDK/examples/app-dir/$RTE_TARGET``.\n+Applications are output to: ``dpdk/<build_dir>/examples``.\n \n \n-In the example above the compiled application is written to the ``build`` subdirectory.\n-To have the applications written to a different location,\n-the ``O=/path/to/build/directory`` option may be specified in the make command.\n+To compile a single application\n+-------------------------------\n \n- .. code-block:: console\n \n- make O=/tmp\n+Using meson\n+~~~~~~~~~~~\n \n-To build the applications for debugging use the ``DEBUG`` option.\n-This option adds some extra flags, disables compiler optimizations and\n-sets verbose output.\n+Go to DPDK build directory:\n \n .. code-block:: console\n \n- make DEBUG=1\n-\n-\n-To compile a single application\n--------------------------------\n+ cd dpdk/<build_dir>\n \n-Set the path to DPDK source code:\n+Enable example app compilation:\n \n- .. code-block:: console\n+ .. code-block:: console\n \n- export RTE_SDK=/path/to/rte_sdk\n+ meson configure -Dexamples=helloworld\n \n-Go to DPDK source:\n+Build:\n \n- .. code-block:: console\n+ .. code-block:: console\n \n- cd $RTE_SDK\n+ ninja\n \n-Build DPDK:\n \n- .. code-block:: console\n+Using Make\n+~~~~~~~~~~\n \n- make defconfig\n- make\n+Pkg-config is used when building an example app standalone using make, please\n+see :ref:`building_app_using_installed_dpdk` for more information.\n \n Go to the sample application directory. Unless otherwise specified the sample\n-applications are located in ``$RTE_SDK/examples/``.\n-\n+applications are located in ``dpdk/examples/``.\n \n Build the application:\n \n .. code-block:: console\n \n- export RTE_TARGET=build\n make\n \n-To cross compile the sample application(s)\n-------------------------------------------\n-\n-For cross compiling the sample application(s), please append 'CROSS=$(CROSS_COMPILER_PREFIX)' to the 'make' command.\n-In example of AARCH64 cross compiling:\n+To build the application for debugging use the ``DEBUG`` option.\n+This option adds some extra flags, disables compiler optimizations and\n+sets verbose output.\n \n .. code-block:: console\n \n- export RTE_TARGET=build\n- export RTE_SDK=/path/to/rte_sdk\n- make -C examples CROSS=aarch64-linux-gnu-\n- or\n- make CROSS=aarch64-linux-gnu-\n+ make DEBUG=1\ndiff --git a/doc/guides/sample_app_ug/dist_app.rst b/doc/guides/sample_app_ug/dist_app.rst\nindex 90270e3a58..3bd03905c3 100644\n--- a/doc/guides/sample_app_ug/dist_app.rst\n+++ b/doc/guides/sample_app_ug/dist_app.rst\n@@ -42,7 +42,7 @@ Running the Application\n \n .. code-block:: console\n \n- ./build/distributor_app [EAL options] -- -p PORTMASK\n+ ./<build-dir>/examples/dpdk-distributor [EAL options] -- -p PORTMASK\n \n where,\n \n@@ -53,7 +53,7 @@ Running the Application\n \n .. code-block:: console\n \n- $ ./build/distributor_app -l 1-9,22 -n 4 -- -p f\n+ $ ./<build-dir>/examples/dpdk-distributor -l 1-9,22 -n 4 -- -p f\n \n #. Refer to the DPDK Getting Started Guide for general information on running\n applications and the Environment Abstraction Layer (EAL) options.\ndiff --git a/doc/guides/sample_app_ug/ethtool.rst b/doc/guides/sample_app_ug/ethtool.rst\nindex 253004dd00..7819871917 100644\n--- a/doc/guides/sample_app_ug/ethtool.rst\n+++ b/doc/guides/sample_app_ug/ethtool.rst\n@@ -24,7 +24,7 @@ The only available options are the standard ones for the EAL:\n \n .. code-block:: console\n \n- ./ethtool-app/${RTE_TARGET}/ethtool [EAL options]\n+ ./<build_dir>/examples/dpdk-ethtool [EAL options]\n \n Refer to the *DPDK Getting Started Guide* for general information on\n running applications and the Environment Abstraction Layer (EAL)\ndiff --git a/doc/guides/sample_app_ug/eventdev_pipeline.rst b/doc/guides/sample_app_ug/eventdev_pipeline.rst\nindex dc7972aa9a..b4fc587a09 100644\n--- a/doc/guides/sample_app_ug/eventdev_pipeline.rst\n+++ b/doc/guides/sample_app_ug/eventdev_pipeline.rst\n@@ -46,7 +46,8 @@ these settings is shown below:\n \n .. code-block:: console\n \n- ./build/eventdev_pipeline --vdev event_sw0 -- -r1 -t1 -e4 -w FF00 -s4 -n0 -c32 -W1000 -D\n+ ./<build_dir>/examples/dpdk-eventdev_pipeline --vdev event_sw0 -- -r1 -t1 /\n+ -e4 -w FF00 -s4 -n0 -c32 -W1000 -D\n \n The application has some sanity checking built-in, so if there is a function\n (e.g.; the RX core) which doesn't have a cpu core mask assigned, the application\ndiff --git a/doc/guides/sample_app_ug/fips_validation.rst b/doc/guides/sample_app_ug/fips_validation.rst\nindex 2953fddeb9..8b009244b8 100644\n--- a/doc/guides/sample_app_ug/fips_validation.rst\n+++ b/doc/guides/sample_app_ug/fips_validation.rst\n@@ -70,9 +70,7 @@ Compiling the Application\n \n * Compile Application\n \n- .. code-block:: console\n-\n- make -C examples/fips_validation\n+ To compile the sample application see :doc:`compiling`.\n \n * Run ``dos2unix`` on the request files\n \n@@ -92,7 +90,7 @@ The application requires a number of command line options:\n \n .. code-block:: console\n \n- ./fips_validation [EAL options]\n+ ./dpdk-fips_validation [EAL options]\n -- --req-file FILE_PATH/FOLDER_PATH\n --rsp-file FILE_PATH/FOLDER_PATH\n [--cryptodev DEVICE_NAME] [--cryptodev-id ID] [--path-is-folder]\n@@ -117,7 +115,7 @@ file for crypto_aesni_mb PMD, issue the command:\n \n .. code-block:: console\n \n- $ ./fips_validation --vdev crypto_aesni_mb --\n+ $ ./dpdk-fips_validation --vdev crypto_aesni_mb --\n --req-file /PATH/TO/REQUEST/FILE.req --rsp-file ./PATH/TO/RESPONSE/FILE.rsp\n --cryptodev crypto_aesni_mb\n \n@@ -126,7 +124,7 @@ data files in one folder for crypto_aesni_gcm PMD, issue the command:\n \n .. code-block:: console\n \n- $ ./fips_validation --vdev crypto_aesni_gcm0 --\n+ $ ./dpdk-fips_validation --vdev crypto_aesni_gcm0 --\n --req-file /PATH/TO/REQUEST/FILE/FOLDER/\n --rsp-file ./PATH/TO/RESPONSE/FILE/FOLDER/\n --cryptodev-id 0 --path-is-folder\ndiff --git a/doc/guides/sample_app_ug/flow_classify.rst b/doc/guides/sample_app_ug/flow_classify.rst\nindex dc40b4d6f9..2ae22739c0 100644\n--- a/doc/guides/sample_app_ug/flow_classify.rst\n+++ b/doc/guides/sample_app_ug/flow_classify.rst\n@@ -28,8 +28,8 @@ To run the example in a ``linux`` environment:\n \n .. code-block:: console\n \n- cd ~/dpdk/examples/flow_classify\n- ./build/flow_classify -c 4 -n 4 -- --rule_ipv4=\"../ipv4_rules_file.txt\"\n+ ./<build_dir>/examples/dpdk-flow_classify -c 4 -n 4 -- /\n+ --rule_ipv4=\"../ipv4_rules_file.txt\"\n \n Please refer to the *DPDK Getting Started Guide*, section\n :doc:`../linux_gsg/build_sample_apps`\ndiff --git a/doc/guides/sample_app_ug/flow_filtering.rst b/doc/guides/sample_app_ug/flow_filtering.rst\nindex 5e5a6cd8a0..4a4006dc8e 100644\n--- a/doc/guides/sample_app_ug/flow_filtering.rst\n+++ b/doc/guides/sample_app_ug/flow_filtering.rst\n@@ -13,28 +13,7 @@ It is intended as a demonstration of the basic components RTE flow rules.\n Compiling the Application\n -------------------------\n \n-To compile the application export the path to the DPDK source tree and go to\n-the example directory:\n-\n-.. code-block:: console\n-\n- export RTE_SDK=/path/to/rte_sdk\n-\n- cd ${RTE_SDK}/examples/flow_filtering\n-\n-Set the target, for example:\n-\n-.. code-block:: console\n-\n- export RTE_TARGET=x86_64-native-linux-gcc\n-\n-See the *DPDK Getting Started* Guide for possible ``RTE_TARGET`` values.\n-\n-Build the application as follows:\n-\n-.. code-block:: console\n-\n- make\n+To compile the sample application see :doc:`compiling`.\n \n \n Running the Application\n@@ -44,7 +23,7 @@ To run the example in a ``linux`` environment:\n \n .. code-block:: console\n \n- ./build/flow -l 1 -n 1\n+ ./<build_dir>/examples/dpdk-flow_filtering -l 1 -n 1\n \n Refer to *DPDK Getting Started Guide* for general information on running\n applications and the Environment Abstraction Layer (EAL) options.\ndiff --git a/doc/guides/sample_app_ug/hello_world.rst b/doc/guides/sample_app_ug/hello_world.rst\nindex 46f997a7dc..8f48533873 100644\n--- a/doc/guides/sample_app_ug/hello_world.rst\n+++ b/doc/guides/sample_app_ug/hello_world.rst\n@@ -21,7 +21,7 @@ To run the example in a linux environment:\n \n .. code-block:: console\n \n- $ ./build/helloworld -l 0-3 -n 4\n+ $ ./<build_dir>/examples/dpdk-helloworld -l 0-3 -n 4\n \n Refer to *DPDK Getting Started Guide* for general information on running applications\n and the Environment Abstraction Layer (EAL) options.\ndiff --git a/doc/guides/sample_app_ug/ioat.rst b/doc/guides/sample_app_ug/ioat.rst\nindex bab7654b8d..f35bee9d86 100644\n--- a/doc/guides/sample_app_ug/ioat.rst\n+++ b/doc/guides/sample_app_ug/ioat.rst\n@@ -45,7 +45,7 @@ The application requires a number of command line options:\n \n .. code-block:: console\n \n- ./build/ioatfwd [EAL options] -- [-p MASK] [-q NQ] [-s RS] [-c <sw|hw>]\n+ ./<build_dir>/examples/dpdk-ioat [EAL options] -- [-p MASK] [-q NQ] [-s RS] [-c <sw|hw>]\n [--[no-]mac-updating]\n \n where,\n@@ -81,7 +81,7 @@ updating issue the command:\n \n .. code-block:: console\n \n- $ ./build/ioatfwd -l 0-2 -n 2 -- -p 0x1 --mac-updating -c sw\n+ $ ./<build_dir>/examples/dpdk-ioat -l 0-2 -n 2 -- -p 0x1 --mac-updating -c sw\n \n To run the application in a Linux environment with 2 lcores (the master lcore,\n plus one forwarding core), 2 ports (ports 0 and 1), hardware copying and no MAC\n@@ -89,7 +89,7 @@ updating issue the command:\n \n .. code-block:: console\n \n- $ ./build/ioatfwd -l 0-1 -n 1 -- -p 0x3 --no-mac-updating -c hw\n+ $ ./<build_dir>/examples/dpdk-ioat -l 0-1 -n 1 -- -p 0x3 --no-mac-updating -c hw\n \n Refer to the *DPDK Getting Started Guide* for general information on\n running applications and the Environment Abstraction Layer (EAL) options.\ndiff --git a/doc/guides/sample_app_ug/ip_frag.rst b/doc/guides/sample_app_ug/ip_frag.rst\nindex afeaff3639..92d5e4aeae 100644\n--- a/doc/guides/sample_app_ug/ip_frag.rst\n+++ b/doc/guides/sample_app_ug/ip_frag.rst\n@@ -53,7 +53,7 @@ Application usage:\n \n .. code-block:: console\n \n- ./build/ip_fragmentation [EAL options] -- -p PORTMASK [-q NQ]\n+ ./<build_dir>/examples/dpdk-ip_fragmentation [EAL options] -- -p PORTMASK [-q NQ]\n \n where:\n \n@@ -65,7 +65,7 @@ To run the example in linux environment with 2 lcores (2,4) over 2 ports(0,2) wi\n \n .. code-block:: console\n \n- ./build/ip_fragmentation -l 2,4 -n 3 -- -p 5\n+ ./<build_dir>/examples/dpdk-ip_fragmentation -l 2,4 -n 3 -- -p 5\n EAL: coremask set to 14\n EAL: Detected lcore 0 on socket 0\n EAL: Detected lcore 1 on socket 1\n@@ -94,7 +94,7 @@ To run the example in linux environment with 1 lcore (4) over 2 ports(0,2) with\n \n .. code-block:: console\n \n- ./build/ip_fragmentation -l 4 -n 3 -- -p 5 -q 2\n+ ./<build_dir>/examples/dpdk-ip_fragmentation -l 4 -n 3 -- -p 5 -q 2\n \n To test the application, flows should be set up in the flow generator that match the values in the\n l3fwd_ipv4_route_array and/or l3fwd_ipv6_route_array table.\ndiff --git a/doc/guides/sample_app_ug/ip_pipeline.rst b/doc/guides/sample_app_ug/ip_pipeline.rst\nindex 56014be174..1d8656c637 100644\n--- a/doc/guides/sample_app_ug/ip_pipeline.rst\n+++ b/doc/guides/sample_app_ug/ip_pipeline.rst\n@@ -34,7 +34,7 @@ Running the application\n \n The application startup command line is::\n \n- ip_pipeline [EAL_ARGS] -- [-s SCRIPT_FILE] [-h HOST] [-p PORT]\n+ dpdk-ip_pipeline [EAL_ARGS] -- [-s SCRIPT_FILE] [-h HOST] [-p PORT]\n \n The application startup arguments are:\n \n@@ -71,7 +71,7 @@ The following is an example command to run ip pipeline application configured fo\n \n .. code-block:: console\n \n- $ ./build/ip_pipeline -c 0x3 -- -s examples/route_ecmp.cli\n+ $ ./<build_dir>/examples/dpdk-ip_pipeline -c 0x3 -- -s examples/route_ecmp.cli\n \n The application should start successfully and display as follows:\n \ndiff --git a/doc/guides/sample_app_ug/ip_reassembly.rst b/doc/guides/sample_app_ug/ip_reassembly.rst\nindex f34b9d0055..e72c8492e9 100644\n--- a/doc/guides/sample_app_ug/ip_reassembly.rst\n+++ b/doc/guides/sample_app_ug/ip_reassembly.rst\n@@ -42,7 +42,7 @@ The application has a number of command line options:\n \n .. code-block:: console\n \n- ./build/ip_reassembly [EAL options] -- -p PORTMASK [-q NQ] [--maxflows=FLOWS>] [--flowttl=TTL[(s|ms)]]\n+ ./<build_dir>/examples/dpdk-ip_reassembly [EAL options] -- -p PORTMASK [-q NQ] [--maxflows=FLOWS>] [--flowttl=TTL[(s|ms)]]\n \n where:\n \n@@ -61,7 +61,7 @@ To run the example in linux environment with 2 lcores (2,4) over 2 ports(0,2) wi\n \n .. code-block:: console\n \n- ./build/ip_reassembly -l 2,4 -n 3 -- -p 5\n+ ./<build_dir>/examples/dpdk-ip_reassembly -l 2,4 -n 3 -- -p 5\n EAL: coremask set to 14\n EAL: Detected lcore 0 on socket 0\n EAL: Detected lcore 1 on socket 1\n@@ -92,7 +92,7 @@ To run the example in linux environment with 1 lcore (4) over 2 ports(0,2) with\n \n .. code-block:: console\n \n- ./build/ip_reassembly -l 4 -n 3 -- -p 5 -q 2\n+ ./<build_dir>/examples/dpdk-ip_reassembly -l 4 -n 3 -- -p 5 -q 2\n \n To test the application, flows should be set up in the flow generator that match the values in the\n l3fwd_ipv4_route_array and/or l3fwd_ipv6_route_array table.\n@@ -231,7 +231,8 @@ Debug logging and Statistics Collection\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n \n The RTE_LIBRTE_IP_FRAG_TBL_STAT controls statistics collection for the IP Fragment Table.\n-This macro is disabled by default.\n+This macro is disabled by default, but it can be enabled by modifying the appropriate line\n+in ``config/rte_config.h``.\n To make ip_reassembly print the statistics to the standard output,\n the user must send either an USR1, INT or TERM signal to the process.\n For all of these signals, the ip_reassembly process prints Fragment table statistics for each RX queue,\ndiff --git a/doc/guides/sample_app_ug/ipsec_secgw.rst b/doc/guides/sample_app_ug/ipsec_secgw.rst\nindex 434f484138..1f37dccf8b 100644\n--- a/doc/guides/sample_app_ug/ipsec_secgw.rst\n+++ b/doc/guides/sample_app_ug/ipsec_secgw.rst\n@@ -116,12 +116,6 @@ To compile the sample application see :doc:`compiling`.\n \n The application is located in the ``ipsec-secgw`` sub-directory.\n \n-#. [Optional] Build the application for debugging:\n- This option adds some extra flags, disables compiler optimizations and\n- is verbose::\n-\n- make DEBUG=1\n-\n \n Running the Application\n -----------------------\n@@ -129,7 +123,7 @@ Running the Application\n The application has a number of command line options::\n \n \n- ./build/ipsec-secgw [EAL options] --\n+ ./<build_dir>/examples/dpdk-ipsec-secgw [EAL options] --\n -p PORTMASK -P -u PORTMASK -j FRAMESIZE\n -l -w REPLAY_WINOW_SIZE -e -a\n -c SAD_CACHE_SIZE\n@@ -245,7 +239,7 @@ The mapping of lcores to port/queues is similar to other l3fwd applications.\n \n For example, given the following command line to run application in poll mode::\n \n- ./build/ipsec-secgw -l 20,21 -n 4 --socket-mem 0,2048 \\\n+ ./<build_dir>/examples/dpdk-ipsec-secgw -l 20,21 -n 4 --socket-mem 0,2048 \\\n --vdev \"crypto_null\" -- -p 0xf -P -u 0x3 \\\n --config=\"(0,0,20),(1,0,20),(2,0,21),(3,0,21)\" \\\n -f /path/to/config_file --transfer-mode poll \\\n@@ -297,7 +291,7 @@ where each option means:\n Similarly for example, given the following command line to run application in\n event app mode::\n \n- ./build/ipsec-secgw -c 0x3 -- -P -p 0x3 -u 0x1 \\\n+ ./<build_dir>/examples/dpdk-ipsec-secgw -c 0x3 -- -P -p 0x3 -u 0x1 \\\n -f /path/to/config_file --transfer-mode event \\\n --event-schedule-type parallel \\\n \n@@ -336,7 +330,7 @@ For example, something like the following command line:\n \n .. code-block:: console\n \n- ./build/ipsec-secgw -l 20,21 -n 4 --socket-mem 0,2048 \\\n+ ./<build_dir>/examples/dpdk-ipsec-secgw -l 20,21 -n 4 --socket-mem 0,2048 \\\n -w 81:00.0 -w 81:00.1 -w 81:00.2 -w 81:00.3 \\\n --vdev \"crypto_aesni_mb\" --vdev \"crypto_null\" \\\n \t -- \\\ndiff --git a/doc/guides/sample_app_ug/ipv4_multicast.rst b/doc/guides/sample_app_ug/ipv4_multicast.rst\nindex 8923a7f548..7c6e8b15cc 100644\n--- a/doc/guides/sample_app_ug/ipv4_multicast.rst\n+++ b/doc/guides/sample_app_ug/ipv4_multicast.rst\n@@ -50,7 +50,7 @@ The application has a number of command line options:\n \n .. code-block:: console\n \n- ./build/ipv4_multicast [EAL options] -- -p PORTMASK [-q NQ]\n+ ./<build_dir>/examples/dpdk-ipv4_multicast [EAL options] -- -p PORTMASK [-q NQ]\n \n where,\n \n@@ -67,7 +67,7 @@ Typically, to run the IPv4 Multicast sample application, issue the following com\n \n .. code-block:: console\n \n- ./build/ipv4_multicast -l 0-3 -n 3 -- -p 0x3 -q 1\n+ ./<build_dir>/examples/dpdk-ipv4_multicast -l 0-3 -n 3 -- -p 0x3 -q 1\n \n In this command:\n \ndiff --git a/doc/guides/sample_app_ug/keep_alive.rst b/doc/guides/sample_app_ug/keep_alive.rst\nindex 865ba69e5c..ef7936f80f 100644\n--- a/doc/guides/sample_app_ug/keep_alive.rst\n+++ b/doc/guides/sample_app_ug/keep_alive.rst\n@@ -49,7 +49,7 @@ The application has a number of command line options:\n \n .. code-block:: console\n \n- ./build/l2fwd-keepalive [EAL options] \\\n+ ./<build_dir>/examples/dpdk-l2fwd-keepalive [EAL options] \\\n -- -p PORTMASK [-q NQ] [-K PERIOD] [-T PERIOD]\n \n where,\n@@ -68,7 +68,7 @@ To run the application in linux environment with 4 lcores, 16 ports\n \n .. code-block:: console\n \n- ./build/l2fwd-keepalive -l 0-3 -n 4 -- -q 8 -p ffff -K 10\n+ ./<build_dir>/examples/dpdk-l2fwd-keepalive -l 0-3 -n 4 -- -q 8 -p ffff -K 10\n \n Refer to the *DPDK Getting Started Guide* for general information on\n running applications and the Environment Abstraction Layer (EAL)\ndiff --git a/doc/guides/sample_app_ug/kernel_nic_interface.rst b/doc/guides/sample_app_ug/kernel_nic_interface.rst\nindex aac4ebd8d4..ef441cc1e5 100644\n--- a/doc/guides/sample_app_ug/kernel_nic_interface.rst\n+++ b/doc/guides/sample_app_ug/kernel_nic_interface.rst\n@@ -96,7 +96,7 @@ The ``kni`` example application requires a number of command line options:\n \n .. code-block:: console\n \n- kni [EAL options] -- -p PORTMASK --config=\"(port,lcore_rx,lcore_tx[,lcore_kthread,...])[,(port,lcore_rx,lcore_tx[,lcore_kthread,...])]\" [-P] [-m]\n+ dpdk-kni [EAL options] -- -p PORTMASK --config=\"(port,lcore_rx,lcore_tx[,lcore_kthread,...])[,(port,lcore_rx,lcore_tx[,lcore_kthread,...])]\" [-P] [-m]\n \n Where:\n \n@@ -168,8 +168,8 @@ interface ``vEth1_0`` with the kernel thread bound to lcore 9.\n .. code-block:: console\n \n # rmmod rte_kni\n- # insmod kmod/rte_kni.ko kthread_mode=multiple\n- # ./build/kni -l 4-7 -n 4 -- -P -p 0x3 -m --config=\"(0,4,6,8),(1,5,7,9)\"\n+ # insmod <build_dir>/kernel/linux/kni/rte_kni.ko kthread_mode=multiple\n+ # ./<build-dir>/examples/dpdk-kni -l 4-7 -n 4 -- -P -p 0x3 -m --config=\"(0,4,6,8),(1,5,7,9)\"\n \n The following example is identical, except an additional ``lcore_kthread``\n core is specified per physical port. In this case, ``kni`` will create\n@@ -186,8 +186,8 @@ The kernel thread for each interface will be bound as follows:\n .. code-block:: console\n \n # rmmod rte_kni\n- # insmod kmod/rte_kni.ko kthread_mode=multiple\n- # ./build/kni -l 4-7 -n 4 -- -P -p 0x3 -m --config=\"(0,4,6,8,10),(1,5,7,9,11)\"\n+ # insmod <build_dir>/kernel/linux/kni/rte_kni.ko kthread_mode=multiple\n+ # ./<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)\"\n \n The following example can be used to test the interface between the ``kni``\n test application and the ``rte_kni`` kernel module. In this example,\n@@ -206,8 +206,8 @@ disabled by **not** specifying the ``-m`` flag to ``kni``:\n .. code-block:: console\n \n # rmmod rte_kni\n- # insmod kmod/rte_kni.ko lo_mode=lo_mode_fifo carrier=on\n- # ./build/kni -l 4-7 -n 4 -- -P -p 0x3 --config=\"(0,4,6,8),(1,5,7,9)\"\n+ # insmod <build_dir>/kernel/linux/kni/rte_kni.ko lo_mode=lo_mode_fifo carrier=on\n+ # ./<build-dir>/examples/dpdk-kni -l 4-7 -n 4 -- -P -p 0x3 --config=\"(0,4,6,8),(1,5,7,9)\"\n \n KNI Operations\n --------------\ndiff --git a/doc/guides/sample_app_ug/l2_forward_cat.rst b/doc/guides/sample_app_ug/l2_forward_cat.rst\nindex 0a813200ba..c1be2d7dff 100644\n--- a/doc/guides/sample_app_ug/l2_forward_cat.rst\n+++ b/doc/guides/sample_app_ug/l2_forward_cat.rst\n@@ -70,13 +70,13 @@ To run the example in a ``linux`` environment and enable CAT on cpus 0-2:\n \n .. code-block:: console\n \n- ./build/l2fwd-cat -l 1 -n 4 -- --l3ca=\"0x3@(0-2)\"\n+ ./<build_dir>/examples/dpdk-l2fwd-cat -l 1 -n 4 -- --l3ca=\"0x3@(0-2)\"\n \n or to enable CAT and CDP on cpus 1,3:\n \n .. code-block:: console\n \n- ./build/l2fwd-cat -l 1 -n 4 -- --l3ca=\"(0x00C00,0x00300)@(1,3)\"\n+ ./<build_dir>/examples/dpdk-l2fwd-cat -l 1 -n 4 -- --l3ca=\"(0x00C00,0x00300)@(1,3)\"\n \n If CDP is not supported it will fail with following error message:\n \ndiff --git a/doc/guides/sample_app_ug/l2_forward_crypto.rst b/doc/guides/sample_app_ug/l2_forward_crypto.rst\nindex 962752f21c..e2c0f9f1ec 100644\n--- a/doc/guides/sample_app_ug/l2_forward_crypto.rst\n+++ b/doc/guides/sample_app_ug/l2_forward_crypto.rst\n@@ -39,7 +39,7 @@ The application requires a number of command line options:\n \n .. code-block:: console\n \n- ./build/l2fwd-crypto [EAL options] -- [-p PORTMASK] [-q NQ] [-s] [-T PERIOD] /\n+ ./<build_dir>/examples/dpdk-l2fwd-crypto [EAL options] -- [-p PORTMASK] [-q NQ] [-s] [-T PERIOD] /\n [--cdev_type HW/SW/ANY] [--chain HASH_CIPHER/CIPHER_HASH/CIPHER_ONLY/HASH_ONLY/AEAD] /\n [--cipher_algo ALGO] [--cipher_op ENCRYPT/DECRYPT] [--cipher_key KEY] /\n [--cipher_key_random_size SIZE] [--cipher_iv IV] [--cipher_iv_random_size SIZE] /\n@@ -162,7 +162,7 @@ To run the application in linux environment with 2 lcores, 2 ports and 2 crypto\n \n .. code-block:: console\n \n- $ ./build/l2fwd-crypto -l 0-1 -n 4 --vdev \"crypto_aesni_mb0\" \\\n+ $ ./<build_dir>/examples/dpdk-l2fwd-crypto -l 0-1 -n 4 --vdev \"crypto_aesni_mb0\" \\\n --vdev \"crypto_aesni_mb1\" -- -p 0x3 --chain CIPHER_HASH \\\n --cipher_op ENCRYPT --cipher_algo aes-cbc \\\n --cipher_key 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f \\\ndiff --git a/doc/guides/sample_app_ug/l2_forward_event.rst b/doc/guides/sample_app_ug/l2_forward_event.rst\nindex d536eee819..11c9d4b2ee 100644\n--- a/doc/guides/sample_app_ug/l2_forward_event.rst\n+++ b/doc/guides/sample_app_ug/l2_forward_event.rst\n@@ -52,7 +52,7 @@ The application requires a number of command line options:\n \n .. code-block:: console\n \n- ./build/l2fwd-event [EAL options] -- -p PORTMASK [-q NQ] --[no-]mac-updating --mode=MODE --eventq-sched=SCHED_MODE\n+ ./<build_dir>/examples/dpdk-l2fwd-event [EAL options] -- -p PORTMASK [-q NQ] --[no-]mac-updating --mode=MODE --eventq-sched=SCHED_MODE\n \n where,\n \n@@ -75,20 +75,20 @@ issue the command:\n \n .. code-block:: console\n \n- ./build/l2fwd-event -l 0-3 -n 4 -- -q 8 -p ffff --mode=poll\n+ ./<build_dir>/examples/dpdk-l2fwd-event -l 0-3 -n 4 -- -q 8 -p ffff --mode=poll\n \n Eventdev mode with 4 lcores, 16 ports , sched method ordered and MAC address updating enabled,\n issue the command:\n \n .. code-block:: console\n \n- ./build/l2fwd-event -l 0-3 -n 4 -- -p ffff --eventq-sched=ordered\n+ ./<build_dir>/examples/dpdk-l2fwd-event -l 0-3 -n 4 -- -p ffff --eventq-sched=ordered\n \n or\n \n .. code-block:: console\n \n- ./build/l2fwd-event -l 0-3 -n 4 -- -q 8 -p ffff --mode=eventdev --eventq-sched=ordered\n+ ./<build_dir>/examples/dpdk-l2fwd-event -l 0-3 -n 4 -- -q 8 -p ffff --mode=eventdev --eventq-sched=ordered\n \n Refer to the *DPDK Getting Started Guide* for general information on running\n applications and the Environment Abstraction Layer (EAL) options.\n@@ -105,7 +105,7 @@ scheduler. Following is the sample command:\n \n .. code-block:: console\n \n- ./build/l2fwd-event -l 0-7 -s 0-3 -n 4 --vdev event_sw0 -- -q 8 -p ffff --mode=eventdev --eventq-sched=ordered\n+ ./<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\n \n Explanation\n -----------\ndiff --git a/doc/guides/sample_app_ug/l2_forward_job_stats.rst b/doc/guides/sample_app_ug/l2_forward_job_stats.rst\nindex 8d0c38721f..1a854abb23 100644\n--- a/doc/guides/sample_app_ug/l2_forward_job_stats.rst\n+++ b/doc/guides/sample_app_ug/l2_forward_job_stats.rst\n@@ -81,7 +81,7 @@ The application requires a number of command line options:\n \n .. code-block:: console\n \n- ./build/l2fwd-jobstats [EAL options] -- -p PORTMASK [-q NQ] [-l]\n+ ./<build_dir>/examples/dpdk-l2fwd-jobstats [EAL options] -- -p PORTMASK [-q NQ] [-l]\n \n where,\n \n@@ -96,7 +96,7 @@ thousands separator printing, issue the command:\n \n .. code-block:: console\n \n- $ ./build/l2fwd-jobstats -l 0-3 -n 4 -- -q 8 -p ffff -l\n+ $ ./<build_dir>/examples/dpdk-l2fwd-jobstats -l 0-3 -n 4 -- -q 8 -p ffff -l\n \n Refer to the *DPDK Getting Started Guide* for general information on running applications\n and the Environment Abstraction Layer (EAL) options.\ndiff --git a/doc/guides/sample_app_ug/l2_forward_real_virtual.rst b/doc/guides/sample_app_ug/l2_forward_real_virtual.rst\nindex c0e8488e79..5a13de215e 100644\n--- a/doc/guides/sample_app_ug/l2_forward_real_virtual.rst\n+++ b/doc/guides/sample_app_ug/l2_forward_real_virtual.rst\n@@ -91,7 +91,7 @@ The application requires a number of command line options:\n \n .. code-block:: console\n \n- ./build/l2fwd [EAL options] -- -p PORTMASK\n+ ./<build_dir>/examples/dpdk-l2fwd [EAL options] -- -p PORTMASK\n [-q NQ]\n --[no-]mac-updating\n [--portmap=\"(port, port)[,(port, port)]\"]\n@@ -111,7 +111,7 @@ updating enabled, issue the command:\n \n .. code-block:: console\n \n- $ ./build/l2fwd -l 0-3 -n 4 -- -q 8 -p ffff\n+ $ ./<build_dir>/examples/dpdk-l2fwd -l 0-3 -n 4 -- -q 8 -p ffff\n \n To run the application in linux environment with 4 lcores, 4 ports, 8 RX queues\n per lcore, to forward RX traffic of ports 0 & 1 on ports 2 & 3 respectively and\n@@ -119,7 +119,7 @@ vice versa, issue the command:\n \n .. code-block:: console\n \n- $ ./build/l2fwd -l 0-3 -n 4 -- -q 8 -p f --portmap=\"(0,2)(1,3)\"\n+ $ ./<build_dir>/examples/dpdk-l2fwd -l 0-3 -n 4 -- -q 8 -p f --portmap=\"(0,2)(1,3)\"\n \n Refer to the *DPDK Getting Started Guide* for general information on running applications\n and the Environment Abstraction Layer (EAL) options.\ndiff --git a/doc/guides/sample_app_ug/l3_forward.rst b/doc/guides/sample_app_ug/l3_forward.rst\nindex 07c8d44936..7acbd7404e 100644\n--- a/doc/guides/sample_app_ug/l3_forward.rst\n+++ b/doc/guides/sample_app_ug/l3_forward.rst\n@@ -51,7 +51,7 @@ Running the Application\n \n The application has a number of command line options::\n \n- ./l3fwd [EAL options] -- -p PORTMASK\n+ ./dpdk-l3fwd [EAL options] -- -p PORTMASK\n [-P]\n [-E]\n [-L]\n@@ -111,7 +111,7 @@ To enable L3 forwarding between two ports, assuming that both ports are in the s\n \n .. code-block:: console\n \n- ./build/l3fwd -l 1,2 -n 4 -- -p 0x3 --config=\"(0,0,1),(1,0,2)\"\n+ ./<build_dir>/examples/dpdk-l3fwd -l 1,2 -n 4 -- -p 0x3 --config=\"(0,0,1),(1,0,2)\"\n \n In this command:\n \n@@ -138,13 +138,13 @@ Following is the sample command:\n \n .. code-block:: console\n \n- ./build/l3fwd -l 0-3 -n 4 -w <event device> -- -p 0x3 --eventq-sched=ordered\n+ ./<build_dir>/examples/dpdk-l3fwd -l 0-3 -n 4 -w <event device> -- -p 0x3 --eventq-sched=ordered\n \n or\n \n .. code-block:: console\n \n- ./build/l3fwd -l 0-3 -n 4 -w <event device> -- -p 0x03 --mode=eventdev --eventq-sched=ordered\n+ ./<build_dir>/examples/dpdk-l3fwd -l 0-3 -n 4 -w <event device> -- -p 0x03 --mode=eventdev --eventq-sched=ordered\n \n In this command:\n \n@@ -166,7 +166,7 @@ scheduler. Following is the sample command:\n \n .. code-block:: console\n \n- ./build/l3fwd -l 0-7 -s 0xf0000 -n 4 --vdev event_sw0 -- -p 0x3 --mode=eventdev --eventq-sched=ordered\n+ ./<build_dir>/examples/dpdk-l3fwd -l 0-7 -s 0xf0000 -n 4 --vdev event_sw0 -- -p 0x3 --mode=eventdev --eventq-sched=ordered\n \n In case of eventdev mode, *--config* option is not used for ethernet port\n configuration. Instead each ethernet port will be configured with mentioned\ndiff --git a/doc/guides/sample_app_ug/l3_forward_access_ctrl.rst b/doc/guides/sample_app_ug/l3_forward_access_ctrl.rst\nindex a44fbcd52c..d3c901f8d8 100644\n--- a/doc/guides/sample_app_ug/l3_forward_access_ctrl.rst\n+++ b/doc/guides/sample_app_ug/l3_forward_access_ctrl.rst\n@@ -184,7 +184,7 @@ Packet 2 matches Rule 2 and is forwarded to port 1.\n Packet 3 matches Rule 3 and is forwarded to port 0.\n \n For more details on the rule file format,\n-please refer to rule_ipv4.db and rule_ipv6.db files (inside <RTE_SDK>/examples/l3fwd-acl/).\n+please refer to rule_ipv4.db and rule_ipv6.db files (inside dpdk/examples/l3fwd-acl/).\n \n Application Phases\n ~~~~~~~~~~~~~~~~~~\n@@ -236,7 +236,7 @@ The application has a number of command line options:\n \n .. code-block:: console\n \n- ./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]\n+ ./<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]\n \n \n where,\n@@ -268,7 +268,7 @@ To enable L3 forwarding between two ports, assuming that both ports are in the s\n \n .. code-block:: console\n \n- ./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\n+ ./<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\n \n In this command:\n \ndiff --git a/doc/guides/sample_app_ug/l3_forward_graph.rst b/doc/guides/sample_app_ug/l3_forward_graph.rst\nindex df50827bab..75617e3af1 100644\n--- a/doc/guides/sample_app_ug/l3_forward_graph.rst\n+++ b/doc/guides/sample_app_ug/l3_forward_graph.rst\n@@ -44,7 +44,7 @@ Running the Application\n \n The application has a number of command line options similar to l3fwd::\n \n- ./l3fwd-graph [EAL options] -- -p PORTMASK\n+ ./dpdk-l3fwd-graph [EAL options] -- -p PORTMASK\n [-P]\n --config(port,queue,lcore)[,(port,queue,lcore)]\n [--eth-dest=X,MM:MM:MM:MM:MM:MM]\n@@ -79,7 +79,7 @@ To enable L3 forwarding between two ports, assuming that both ports are in the s\n \n .. code-block:: console\n \n- ./build/l3fwd-graph -l 1,2 -n 4 -- -p 0x3 --config=\"(0,0,1),(1,0,2)\"\n+ ./<build_dir>/examples/dpdk-l3fwd-graph -l 1,2 -n 4 -- -p 0x3 --config=\"(0,0,1),(1,0,2)\"\n \n In this command:\n \ndiff --git a/doc/guides/sample_app_ug/l3_forward_power_man.rst b/doc/guides/sample_app_ug/l3_forward_power_man.rst\nindex 0cc6f2e62e..4f997108ba 100644\n--- a/doc/guides/sample_app_ug/l3_forward_power_man.rst\n+++ b/doc/guides/sample_app_ug/l3_forward_power_man.rst\n@@ -88,7 +88,7 @@ The application has a number of command line options:\n \n .. code-block:: console\n \n- ./build/l3fwd_power [EAL options] -- -p PORTMASK [-P] --config(port,queue,lcore)[,(port,queue,lcore)] [--enable-jumbo [--max-pkt-len PKTLEN]] [--no-numa]\n+ ./<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]\n \n where,\n \n@@ -378,7 +378,7 @@ See :doc:`Power Management<../prog_guide/power_man>` chapter in the DPDK Program\n \n .. code-block:: console\n \n- ./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\n+ ./<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\n \n Where,\n \n@@ -407,7 +407,7 @@ app with the training flag set to “1”, and the other parameters set to\n \n .. code-block:: console\n \n- ./examples/l3fwd-power/build/l3fwd-power -l 1-3 -- -p 0x0f --config=\"(0,0,2),(0,1,3)\" --empty-poll \"1,0,0\" –P\n+ ./<build_dir>/examples/dpdk-l3fwd-power -l 1-3 -- -p 0x0f --config=\"(0,0,2),(0,1,3)\" --empty-poll \"1,0,0\" –P\n \n This will run the training algorithm for x seconds on each core (cores 2\n and 3), and then print out the recommended threshold values for those\n@@ -432,7 +432,7 @@ then be started without the training mode so traffic can start immediately.\n \n .. code-block:: console\n \n- ./examples/l3fwd-power/build/l3fwd-power -l 1-3 -- -p 0x0f --config=\"(0,0,2),(0,1,3)\" --empty-poll \"0,340000,540000\" –P\n+ ./<build_dir>/examples/dpdk-l3fwd-power -l 1-3 -- -p 0x0f --config=\"(0,0,2),(0,1,3)\" --empty-poll \"0,340000,540000\" –P\n \n Telemetry Mode\n --------------\n@@ -449,13 +449,9 @@ cycles it took is measured and compared with minimum and maximum\n reference cycles and accordingly busy rate is set to either 0% or\n 50% or 100%.\n \n- .. Note::\n-\n- * The CONFIG_RTE_LIBRTE_TELEMETRY should be set in order to get the stats in DPDK telemetry.\n-\n .. code-block:: console\n \n- ./examples/l3fwd-power/build/l3fwd-power --telemetry -l 1-3 -- -p 0x0f --config=\"(0,0,2),(0,1,3)\" --telemetry\n+ ./<build_dir>/examples/dpdk-l3fwd-power --telemetry -l 1-3 -- -p 0x0f --config=\"(0,0,2),(0,1,3)\" --telemetry\n \n The new stats ``empty_poll`` , ``full_poll`` and ``busy_percent`` can be viewed by running the script\n ``/usertools/dpdk-telemetry-client.py`` and selecting the menu option ``Send for global Metrics``.\ndiff --git a/doc/guides/sample_app_ug/link_status_intr.rst b/doc/guides/sample_app_ug/link_status_intr.rst\nindex 04c40f2854..75bfd78505 100644\n--- a/doc/guides/sample_app_ug/link_status_intr.rst\n+++ b/doc/guides/sample_app_ug/link_status_intr.rst\n@@ -39,7 +39,7 @@ The application requires a number of command line options:\n \n .. code-block:: console\n \n- ./build/link_status_interrupt [EAL options] -- -p PORTMASK [-q NQ][-T PERIOD]\n+ ./<build_dir>/examples/dpdk-link_status_interrupt [EAL options] -- -p PORTMASK [-q NQ][-T PERIOD]\n \n where,\n \n@@ -54,7 +54,7 @@ issue the command:\n \n .. code-block:: console\n \n- $ ./build/link_status_interrupt -l 0-3 -n 4-- -q 8 -p ffff\n+ $ ./<build_dir>/examples/dpdk-link_status_interrupt -l 0-3 -n 4-- -q 8 -p ffff\n \n Refer to the *DPDK Getting Started Guide* for general information on running applications\n and the Environment Abstraction Layer (EAL) options.\ndiff --git a/doc/guides/sample_app_ug/multi_process.rst b/doc/guides/sample_app_ug/multi_process.rst\nindex f2a79a6397..8b2858b971 100644\n--- a/doc/guides/sample_app_ug/multi_process.rst\n+++ b/doc/guides/sample_app_ug/multi_process.rst\n@@ -41,7 +41,7 @@ passing at least two cores in the coremask/corelist, as follows:\n \n .. code-block:: console\n \n- ./build/simple_mp -l 0-1 -n 4 --proc-type=primary\n+ ./<build_dir>/examples/dpdk-simple_mp -l 0-1 -n 4 --proc-type=primary\n \n For the first DPDK process run, the proc-type flag can be omitted or set to auto,\n since all DPDK processes will default to being a primary instance,\n@@ -50,7 +50,7 @@ The process should start successfully and display a command prompt as follows:\n \n .. code-block:: console\n \n- $ ./build/simple_mp -l 0-1 -n 4 --proc-type=primary\n+ $ ./<build_dir>/examples/dpdk-simple_mp -l 0-1 -n 4 --proc-type=primary\n EAL: coremask set to 3\n EAL: Detected lcore 0 on socket 0\n EAL: Detected lcore 1 on socket 0\n@@ -78,7 +78,7 @@ again run the same binary setting at least two cores in the coremask/corelist:\n \n .. code-block:: console\n \n- ./build/simple_mp -l 2-3 -n 4 --proc-type=secondary\n+ ./<build_dir>/examples/dpdk-simple_mp -l 2-3 -n 4 --proc-type=secondary\n \n When running a secondary process such as that shown above, the proc-type parameter can again be specified as auto.\n However, omitting the parameter altogether will cause the process to try and start as a primary rather than secondary process.\n@@ -184,10 +184,10 @@ the following commands can be used (assuming run as root):\n \n .. code-block:: console\n \n- # ./build/symmetric_mp -l 1 -n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=0\n- # ./build/symmetric_mp -l 2 -n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=1\n- # ./build/symmetric_mp -l 3 -n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=2\n- # ./build/symmetric_mp -l 4 -n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=3\n+ # ./<build_dir>/examples/dpdk-symmetric_mp -l 1 -n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=0\n+ # ./<build_dir>/examples/dpdk-symmetric_mp -l 2 -n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=1\n+ # ./<build_dir>/examples/dpdk-symmetric_mp -l 3 -n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=2\n+ # ./<build_dir>/examples/dpdk-symmetric_mp -l 4 -n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=3\n \n .. note::\n \n@@ -284,9 +284,9 @@ the following commands could be used:\n \n .. code-block:: console\n \n- # ./mp_server/build/mp_server -l 1-2 -n 4 -- -p 3 -n 2\n- # ./mp_client/build/mp_client -l 3 -n 4 --proc-type=auto -- -n 0\n- # ./mp_client/build/mp_client -l 4 -n 4 --proc-type=auto -- -n 1\n+ # ./<build_dir>/examples/dpdk-mp_server -l 1-2 -n 4 -- -p 3 -n 2\n+ # ./<build_dir>/examples/dpdk-mp_client -l 3 -n 4 --proc-type=auto -- -n 0\n+ # ./<build_dir>/examples/dpdk-mp_client -l 4 -n 4 --proc-type=auto -- -n 1\n \n .. note::\n \ndiff --git a/doc/guides/sample_app_ug/ntb.rst b/doc/guides/sample_app_ug/ntb.rst\nindex 93fb752f25..f80b221db7 100644\n--- a/doc/guides/sample_app_ug/ntb.rst\n+++ b/doc/guides/sample_app_ug/ntb.rst\n@@ -32,7 +32,7 @@ The only available options are the standard ones for the EAL:\n \n .. code-block:: console\n \n- ./build/ntb_fwd -c 0xf -n 6 -- -i\n+ ./<build_dir>/examples/dpdk-ntb -c 0xf -n 6 -- -i\n \n Refer to the *DPDK Getting Started Guide* for general information on\n running applications and the Environment Abstraction Layer (EAL)\ndiff --git a/doc/guides/sample_app_ug/packet_ordering.rst b/doc/guides/sample_app_ug/packet_ordering.rst\nindex 1c8ee5d040..5a4e0a9d28 100644\n--- a/doc/guides/sample_app_ug/packet_ordering.rst\n+++ b/doc/guides/sample_app_ug/packet_ordering.rst\n@@ -43,7 +43,8 @@ The application execution command line is:\n \n .. code-block:: console\n \n- ./packet_ordering [EAL options] -- -p PORTMASK [--disable-reorder] [--insight-worker]\n+ ./<build_dir>/examples/dpdk-packet_ordering [EAL options] -- -p PORTMASK /\n+ [--disable-reorder] [--insight-worker]\n \n The -c EAL CPU_COREMASK option has to contain at least 3 CPU cores.\n The first CPU core in the core mask is the master core and would be assigned to\ndiff --git a/doc/guides/sample_app_ug/performance_thread.rst b/doc/guides/sample_app_ug/performance_thread.rst\nindex b04d0ba444..2a50eb4270 100644\n--- a/doc/guides/sample_app_ug/performance_thread.rst\n+++ b/doc/guides/sample_app_ug/performance_thread.rst\n@@ -55,7 +55,7 @@ Running the Application\n \n The application has a number of command line options::\n \n- ./build/l3fwd-thread [EAL options] --\n+ ./<build_dir>/examples/dpdk-l3fwd-thread [EAL options] --\n -p PORTMASK [-P]\n --rx(port,queue,lcore,thread)[,(port,queue,lcore,thread)]\n --tx(lcore,thread)[,(lcore,thread)]\n@@ -141,14 +141,14 @@ in ``--rx/--tx`` are used to affinitize threads to the selected scheduler.\n \n For example, the following places every l-thread on different lcores::\n \n- l3fwd-thread -l 0-7 -n 2 -- -P -p 3 \\\n+ dpdk-l3fwd-thread -l 0-7 -n 2 -- -P -p 3 \\\n --rx=\"(0,0,0,0)(1,0,1,1)\" \\\n --tx=\"(2,0)(3,1)\"\n \n The following places RX l-threads on lcore 0 and TX l-threads on lcore 1 and 2\n and so on::\n \n- l3fwd-thread -l 0-7 -n 2 -- -P -p 3 \\\n+ dpdk-l3fwd-thread -l 0-7 -n 2 -- -P -p 3 \\\n --rx=\"(0,0,0,0)(1,0,0,1)\" \\\n --tx=\"(1,0)(2,1)\"\n \n@@ -164,7 +164,7 @@ place every RX and TX thread on different lcores.\n \n For example, the following places every EAL thread on different lcores::\n \n- l3fwd-thread -l 0-7 -n 2 -- -P -p 3 \\\n+ dpdk-l3fwd-thread -l 0-7 -n 2 -- -P -p 3 \\\n --rx=\"(0,0,0,0)(1,0,1,1)\" \\\n --tx=\"(2,0)(3,1)\" \\\n --no-lthreads\n@@ -176,7 +176,7 @@ parameter is used.\n The following places RX EAL threads on lcore 0 and TX EAL threads on lcore 1\n and 2 and so on::\n \n- l3fwd-thread -l 0-7 -n 2 --lcores=\"(0,1)@0,(2,3)@1\" -- -P -p 3 \\\n+ dpdk-l3fwd-thread -l 0-7 -n 2 --lcores=\"(0,1)@0,(2,3)@1\" -- -P -p 3 \\\n --rx=\"(0,0,0,0)(1,0,1,1)\" \\\n --tx=\"(2,0)(3,1)\" \\\n --no-lthreads\n@@ -190,13 +190,13 @@ and its corresponding EAL threads command line can be realized as follows:\n \n a) Start every thread on different scheduler (1:1)::\n \n- l3fwd-thread -l 0-7 -n 2 -- -P -p 3 \\\n+ dpdk-l3fwd-thread -l 0-7 -n 2 -- -P -p 3 \\\n --rx=\"(0,0,0,0)(1,0,1,1)\" \\\n --tx=\"(2,0)(3,1)\"\n \n EAL thread equivalent::\n \n- l3fwd-thread -l 0-7 -n 2 -- -P -p 3 \\\n+ dpdk-l3fwd-thread -l 0-7 -n 2 -- -P -p 3 \\\n --rx=\"(0,0,0,0)(1,0,1,1)\" \\\n --tx=\"(2,0)(3,1)\" \\\n --no-lthreads\n@@ -205,13 +205,13 @@ b) Start all threads on one core (N:1).\n \n Start 4 L-threads on lcore 0::\n \n- l3fwd-thread -l 0-7 -n 2 -- -P -p 3 \\\n+ dpdk-l3fwd-thread -l 0-7 -n 2 -- -P -p 3 \\\n --rx=\"(0,0,0,0)(1,0,0,1)\" \\\n --tx=\"(0,0)(0,1)\"\n \n Start 4 EAL threads on cpu-set 0::\n \n- l3fwd-thread -l 0-7 -n 2 --lcores=\"(0-3)@0\" -- -P -p 3 \\\n+ dpdk-l3fwd-thread -l 0-7 -n 2 --lcores=\"(0-3)@0\" -- -P -p 3 \\\n --rx=\"(0,0,0,0)(1,0,0,1)\" \\\n --tx=\"(2,0)(3,1)\" \\\n --no-lthreads\n@@ -220,14 +220,14 @@ c) Start threads on different cores (N:M).\n \n Start 2 L-threads for RX on lcore 0, and 2 L-threads for TX on lcore 1::\n \n- l3fwd-thread -l 0-7 -n 2 -- -P -p 3 \\\n+ dpdk-l3fwd-thread -l 0-7 -n 2 -- -P -p 3 \\\n --rx=\"(0,0,0,0)(1,0,0,1)\" \\\n --tx=\"(1,0)(1,1)\"\n \n Start 2 EAL threads for RX on cpu-set 0, and 2 EAL threads for TX on\n cpu-set 1::\n \n- l3fwd-thread -l 0-7 -n 2 --lcores=\"(0-1)@0,(2-3)@1\" -- -P -p 3 \\\n+ dpdk-l3fwd-thread -l 0-7 -n 2 --lcores=\"(0-1)@0,(2-3)@1\" -- -P -p 3 \\\n --rx=\"(0,0,0,0)(1,0,1,1)\" \\\n --tx=\"(2,0)(3,1)\" \\\n --no-lthreads\n@@ -1146,33 +1146,15 @@ in the performance-thread folder\n \n To build and run the pthread shim example\n \n-#. Go to the example applications folder\n-\n- .. code-block:: console\n-\n- export RTE_SDK=/path/to/rte_sdk\n- cd ${RTE_SDK}/examples/performance-thread/pthread_shim\n-\n-\n-#. Set the target (a default target is used if not specified). For example:\n-\n- .. code-block:: console\n-\n- export RTE_TARGET=x86_64-native-linux-gcc\n-\n- See the DPDK Getting Started Guide for possible RTE_TARGET values.\n-\n #. Build the application:\n \n- .. code-block:: console\n-\n- make\n+ To compile the sample application see :doc:`compiling`.\n \n #. To run the pthread_shim example\n \n .. code-block:: console\n \n- lthread-pthread-shim -c core_mask -n number_of_channels\n+ dpdk-pthread-shim -c core_mask -n number_of_channels\n \n .. _lthread_diagnostics:\n \ndiff --git a/doc/guides/sample_app_ug/ptpclient.rst b/doc/guides/sample_app_ug/ptpclient.rst\nindex 12b4f13d5b..a58b6f35bf 100644\n--- a/doc/guides/sample_app_ug/ptpclient.rst\n+++ b/doc/guides/sample_app_ug/ptpclient.rst\n@@ -57,13 +57,6 @@ To compile the sample application see :doc:`compiling`.\n \n The application is located in the ``ptpclient`` sub-directory.\n \n-.. note::\n- To compile the application edit the ``config/common_linux`` configuration file to enable IEEE1588\n- and then recompile DPDK:\n-\n- .. code-block:: console\n-\n- CONFIG_RTE_LIBRTE_IEEE1588=y\n \n Running the Application\n -----------------------\n@@ -72,7 +65,7 @@ To run the example in a ``linux`` environment:\n \n .. code-block:: console\n \n- ./build/ptpclient -l 1 -n 4 -- -p 0x1 -T 0\n+ ./<build_dir>/examples/dpdk-ptpclient -l 1 -n 4 -- -p 0x1 -T 0\n \n Refer to *DPDK Getting Started Guide* for general information on running\n applications and the Environment Abstraction Layer (EAL) options.\ndiff --git a/doc/guides/sample_app_ug/qos_metering.rst b/doc/guides/sample_app_ug/qos_metering.rst\nindex d75f7da52c..6b6853a0e9 100644\n--- a/doc/guides/sample_app_ug/qos_metering.rst\n+++ b/doc/guides/sample_app_ug/qos_metering.rst\n@@ -48,7 +48,7 @@ The application execution command line is as below:\n \n .. code-block:: console\n \n- ./qos_meter [EAL options] -- -p PORTMASK\n+ ./dpdk-qos_meter [EAL options] -- -p PORTMASK\n \n The application is constrained to use a single core in the EAL core mask and 2 ports only in the application port mask\n (first port from the port mask is used for RX and the other port in the core mask is used for TX).\ndiff --git a/doc/guides/sample_app_ug/qos_scheduler.rst b/doc/guides/sample_app_ug/qos_scheduler.rst\nindex b5010657a7..801f5e1286 100644\n--- a/doc/guides/sample_app_ug/qos_scheduler.rst\n+++ b/doc/guides/sample_app_ug/qos_scheduler.rst\n@@ -42,8 +42,8 @@ The application is located in the ``qos_sched`` sub-directory.\n .. note::\n \n To get statistics on the sample app using the command line interface as described in the next section,\n- DPDK must be compiled defining *CONFIG_RTE_SCHED_COLLECT_STATS*,\n- which can be done by changing the configuration file for the specific target to be compiled.\n+ DPDK must be compiled defining *RTE_SCHED_COLLECT_STATS*, which can be done by changing the relevant\n+ entry in the ``config/rte_config.h`` file.\n \n Running the Application\n -----------------------\n@@ -57,7 +57,7 @@ The application has a number of command line options:\n \n .. code-block:: console\n \n- ./qos_sched [EAL options] -- <APP PARAMS>\n+ ./<build_dir>/examples/dpdk-qos_sched [EAL options] -- <APP PARAMS>\n \n Mandatory application parameters include:\n \n@@ -315,7 +315,7 @@ The following is an example command with a single packet flow configuration:\n \n .. code-block:: console\n \n- ./qos_sched -l 1,5,7 -n 4 -- --pfc \"3,2,5,7\" --cfg ./profile.cfg\n+ ./<build_dir>/examples/dpdk-qos_sched -l 1,5,7 -n 4 -- --pfc \"3,2,5,7\" --cfg ./profile.cfg\n \n This example uses a single packet flow configuration which creates one RX thread on lcore 5 reading\n from port 3 and a worker thread on lcore 7 writing to port 2.\n@@ -324,7 +324,7 @@ Another example with 2 packet flow configurations using different ports but shar\n \n .. code-block:: console\n \n- ./qos_sched -l 1,2,6,7 -n 4 -- --pfc \"3,2,2,6,7\" --pfc \"1,0,2,6,7\" --cfg ./profile.cfg\n+ ./<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\n \n Note that independent cores for the packet flow configurations for each of the RX, WT and TX thread are also supported,\n providing flexibility to balance the work.\ndiff --git a/doc/guides/sample_app_ug/rxtx_callbacks.rst b/doc/guides/sample_app_ug/rxtx_callbacks.rst\nindex 0a69ec71ab..62d1f39d7e 100644\n--- a/doc/guides/sample_app_ug/rxtx_callbacks.rst\n+++ b/doc/guides/sample_app_ug/rxtx_callbacks.rst\n@@ -25,13 +25,6 @@ To compile the sample application see :doc:`compiling`.\n \n The application is located in the ``rxtx_callbacks`` sub-directory.\n \n-The callbacks feature requires that the ``CONFIG_RTE_ETHDEV_RXTX_CALLBACKS``\n-setting is on in the ``config/common_`` config file that applies to the\n-target. This is generally on by default:\n-\n-.. code-block:: console\n-\n- CONFIG_RTE_ETHDEV_RXTX_CALLBACKS=y\n \n Running the Application\n -----------------------\n@@ -40,7 +33,7 @@ To run the example in a ``linux`` environment:\n \n .. code-block:: console\n \n- ./build/rxtx_callbacks -l 1 -n 4 -- [-t]\n+ ./<build_dir>/examples/dpdk-rxtx_callbacks -l 1 -n 4 -- [-t]\n \n Use -t to enable hardware timestamping. If not supported by the NIC, an error\n will be displayed.\ndiff --git a/doc/guides/sample_app_ug/server_node_efd.rst b/doc/guides/sample_app_ug/server_node_efd.rst\nindex 12208f4258..f27d1ccfce 100644\n--- a/doc/guides/sample_app_ug/server_node_efd.rst\n+++ b/doc/guides/sample_app_ug/server_node_efd.rst\n@@ -93,7 +93,7 @@ and the back-end node.\n \n The frontend server (server) has the following command line options::\n \n- ./server [EAL options] -- -p PORTMASK -n NUM_NODES -f NUM_FLOWS\n+ ./<build_dir>/examples/dpdk-server [EAL options] -- -p PORTMASK -n NUM_NODES -f NUM_FLOWS\n \n Where,\n \ndiff --git a/doc/guides/sample_app_ug/service_cores.rst b/doc/guides/sample_app_ug/service_cores.rst\nindex cd0f4717aa..9202be6ea9 100644\n--- a/doc/guides/sample_app_ug/service_cores.rst\n+++ b/doc/guides/sample_app_ug/service_cores.rst\n@@ -20,26 +20,9 @@ is application specific, and not a part of the service cores API.\n Compiling the Application\n -------------------------\n \n-#. Go to the example directory:\n+To compile the sample application see :doc:`compiling`.\n \n- .. code-block:: console\n-\n- export RTE_SDK=/path/to/rte_sdk\n- cd ${RTE_SDK}/examples/service_cores\n-\n-#. Set the target (a default target is used if not specified). For example:\n-\n- .. code-block:: console\n-\n- export RTE_TARGET=x86_64-native-linux-gcc\n-\n- See the *DPDK Getting Started* Guide for possible RTE_TARGET values.\n-\n-#. Build the application:\n-\n- .. code-block:: console\n-\n- make\n+The application is located in the ``service_cores`` sub-directory.\n \n Running the Application\n -----------------------\n@@ -50,7 +33,7 @@ pass a service core-mask as an EAL argument at startup time.\n \n .. code-block:: console\n \n- $ ./build/service_cores\n+ $ ./<build_dir>/examples/dpdk-service_cores\n \n \n Explanation\ndiff --git a/doc/guides/sample_app_ug/skeleton.rst b/doc/guides/sample_app_ug/skeleton.rst\nindex 34f6f9aea7..263d8debc8 100644\n--- a/doc/guides/sample_app_ug/skeleton.rst\n+++ b/doc/guides/sample_app_ug/skeleton.rst\n@@ -25,7 +25,7 @@ To run the example in a ``linux`` environment:\n \n .. code-block:: console\n \n- ./build/basicfwd -l 1 -n 4\n+ ./<build_dir>/examples/dpdk-skeleton -l 1 -n 4\n \n Refer to *DPDK Getting Started Guide* for general information on running\n applications and the Environment Abstraction Layer (EAL) options.\ndiff --git a/doc/guides/sample_app_ug/tep_termination.rst b/doc/guides/sample_app_ug/tep_termination.rst\nindex df159355d6..86ced036ce 100644\n--- a/doc/guides/sample_app_ug/tep_termination.rst\n+++ b/doc/guides/sample_app_ug/tep_termination.rst\n@@ -90,36 +90,17 @@ The example in this section have been validated with the following distributions\n \n * Fedora* 20\n \n-Compiling the Sample Code\n--------------------------\n-\n-To enable vhost, turn on vhost library in the configure file\n-``config/common_linux``.\n-\n- .. code-block:: console\n-\n- CONFIG_RTE_LIBRTE_VHOST=y\n-\n-Then following the to compile the sample application shown in\n-:doc:`compiling`.\n \n Running the Sample Code\n -----------------------\n \n-#. Go to the examples directory:\n+Run the tep_termination sample code:\n \n- .. code-block:: console\n-\n- export RTE_SDK=/path/to/rte_sdk\n- cd ${RTE_SDK}/examples/tep_termination\n-\n-#. Run the tep_termination sample code:\n-\n- .. code-block:: console\n+.. code-block:: console\n \n- user@target:~$ ./build/app/tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge --\n- -p 0x1 --dev-basename tep-termination --nb-devices 4\n- --udp-port 4789 --filter-type 1\n+ user@target:~$ ./<build_dir>/examples/dpdk-tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge --\n+ -p 0x1 --dev-basename tep-termination --nb-devices 4\n+ --udp-port 4789 --filter-type 1\n \n .. note::\n \n@@ -139,7 +120,7 @@ The default value is 2.\n \n .. code-block:: console\n \n- user@target:~$ ./build/app/tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge --\n+ user@target:~$ ./<build_dir>/examples/dpdk-tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge --\n --nb-devices 2\n \n **Tunneling UDP port.**\n@@ -149,7 +130,7 @@ The default value is 4789.\n \n .. code-block:: console\n \n- user@target:~$ ./build/app/tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge --\n+ user@target:~$ ./<build_dir>/examples/dpdk-tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge --\n --nb-devices 2 --udp-port 4789\n \n **Filter Type.**\n@@ -160,7 +141,7 @@ The default value is 1, which means the filter type of inner MAC and tenant ID i\n \n .. code-block:: console\n \n- user@target:~$ ./build/app/tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge --\n+ user@target:~$ ./<build_dir>/examples/dpdk-tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge --\n --nb-devices 2 --udp-port 4789 --filter-type 1\n \n **TX Checksum.**\n@@ -170,7 +151,7 @@ The default value is 0, which means the checksum offload is disabled.\n \n .. code-block:: console\n \n- user@target:~$ ./build/app/tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge --\n+ user@target:~$ ./<build_dir>/examples/dpdk-tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge --\n --nb-devices 2 --tx-checksum\n \n **TCP segment size.**\n@@ -180,7 +161,7 @@ The default value is 0, which means TSO offload is disabled.\n \n .. code-block:: console\n \n- user@target:~$ ./build/app/tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge --\n+ user@target:~$ ./<build_dir>/examples/dpdk-tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge --\n --tx-checksum --tso-segsz 800\n \n **Decapsulation option.**\n@@ -190,7 +171,7 @@ The default value is 1.\n \n .. code-block:: console\n \n- user@target:~$ ./build/app/tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge --\n+ user@target:~$ ./<build_dir>/examples/dpdk-tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge --\n --nb-devices 4 --udp-port 4789 --decap 1\n \n **Encapsulation option.**\n@@ -200,7 +181,7 @@ The default value is 1.\n \n .. code-block:: console\n \n- user@target:~$ ./build/app/tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge --\n+ user@target:~$ ./<build_dir>/examples/dpdk-tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge --\n --nb-devices 4 --udp-port 4789 --encap 1\n \n \ndiff --git a/doc/guides/sample_app_ug/test_pipeline.rst b/doc/guides/sample_app_ug/test_pipeline.rst\nindex 5aefd8d89f..d57d08fb2c 100644\n--- a/doc/guides/sample_app_ug/test_pipeline.rst\n+++ b/doc/guides/sample_app_ug/test_pipeline.rst\n@@ -32,7 +32,7 @@ Compiling the Application\n -------------------------\n To compile the sample application see :doc:`compiling`\n \n-The application is located in the ``$RTE_SDK/app/test-pipeline`` directory.\n+The application is located in the ``dpdk/<build_dir>/app`` directory.\n \n \n Running the Application\n@@ -45,7 +45,7 @@ The application execution command line is:\n \n .. code-block:: console\n \n- ./test-pipeline [EAL options] -- -p PORTMASK --TABLE_TYPE\n+ ./dpdk-test-pipeline [EAL options] -- -p PORTMASK --TABLE_TYPE\n \n The -c or -l EAL CPU coremask/corelist option has to contain exactly 3 CPU cores.\n The first CPU core in the core mask is assigned for core A, the second for core B and the third for core C.\ndiff --git a/doc/guides/sample_app_ug/timer.rst b/doc/guides/sample_app_ug/timer.rst\nindex 98d762d238..94cee9819d 100644\n--- a/doc/guides/sample_app_ug/timer.rst\n+++ b/doc/guides/sample_app_ug/timer.rst\n@@ -21,7 +21,7 @@ To run the example in linux environment:\n \n .. code-block:: console\n \n- $ ./build/timer -l 0-3 -n 4\n+ $ ./<build_dir>/examples/dpdk-timer -l 0-3 -n 4\n \n Refer to the *DPDK Getting Started Guide* for general information on running applications and\n the Environment Abstraction Layer (EAL) options.\ndiff --git a/doc/guides/sample_app_ug/vdpa.rst b/doc/guides/sample_app_ug/vdpa.rst\nindex d66a724827..a8bedbab53 100644\n--- a/doc/guides/sample_app_ug/vdpa.rst\n+++ b/doc/guides/sample_app_ug/vdpa.rst\n@@ -29,7 +29,7 @@ Start the vdpa example\n \n .. code-block:: console\n \n- ./vdpa [EAL options] -- [--client] [--interactive|-i] or [--iface SOCKET_PATH]\n+ ./dpdk-vdpa [EAL options] -- [--client] [--interactive|-i] or [--iface SOCKET_PATH]\n \n where\n \n@@ -51,7 +51,7 @@ Take IFCVF driver for example:\n \n .. code-block:: console\n \n- ./vdpa -c 0x2 -n 4 --socket-mem 1024,1024 \\\n+ ./dpdk-vdpa -c 0x2 -n 4 --socket-mem 1024,1024 \\\n -w 0000:06:00.3,vdpa=1 -w 0000:06:00.4,vdpa=1 \\\n -- --interactive\n \ndiff --git a/doc/guides/sample_app_ug/vhost.rst b/doc/guides/sample_app_ug/vhost.rst\nindex b7ed4f8bdf..bacf7898f9 100644\n--- a/doc/guides/sample_app_ug/vhost.rst\n+++ b/doc/guides/sample_app_ug/vhost.rst\n@@ -38,7 +38,7 @@ Start the vswitch example\n \n .. code-block:: console\n \n- ./vhost-switch -l 0-3 -n 4 --socket-mem 1024 \\\n+ ./dpdk-vhost-switch -l 0-3 -n 4 --socket-mem 1024 \\\n -- --socket-file /tmp/sock0 --client \\\n ...\n \n@@ -78,13 +78,13 @@ could be done by:\n .. code-block:: console\n \n modprobe uio_pci_generic\n- $RTE_SDK/usertools/dpdk-devbind.py -b uio_pci_generic 0000:00:04.0\n+ dpdk/usertools/dpdk-devbind.py -b uio_pci_generic 0000:00:04.0\n \n Then start testpmd for packet forwarding testing.\n \n .. code-block:: console\n \n- ./x86_64-native-gcc/app/testpmd -l 0-1 -- -i\n+ ./<build_dir>/app/dpdk-testpmd -l 0-1 -- -i\n > start tx_first\n \n Inject packets\n@@ -192,11 +192,6 @@ Common Issues\n max queue number is larger than 128, device start will fail due to\n insufficient mbuf.\n \n- Change the default number to make it work as below, just set the number\n- according to the NIC's property. ::\n-\n- make EXTRA_CFLAGS=\"-DMAX_QUEUES=320\"\n-\n * Option \"builtin-net-driver\" is incompatible with QEMU\n \n QEMU vhost net device start will fail if protocol feature is not negotiated.\ndiff --git a/doc/guides/sample_app_ug/vhost_blk.rst b/doc/guides/sample_app_ug/vhost_blk.rst\nindex 681de6f3e1..788eef0d5f 100644\n--- a/doc/guides/sample_app_ug/vhost_blk.rst\n+++ b/doc/guides/sample_app_ug/vhost_blk.rst\n@@ -36,7 +36,7 @@ Start the vhost_blk example\n \n .. code-block:: console\n \n- ./vhost_blk -m 1024\n+ ./dpdk-vhost_blk -m 1024\n \n .. _vhost_blk_app_run_vm:\n \ndiff --git a/doc/guides/sample_app_ug/vhost_crypto.rst b/doc/guides/sample_app_ug/vhost_crypto.rst\nindex bbc25bde1c..7ae7addac4 100644\n--- a/doc/guides/sample_app_ug/vhost_crypto.rst\n+++ b/doc/guides/sample_app_ug/vhost_crypto.rst\n@@ -28,7 +28,7 @@ Start the vhost_crypto example\n \n .. code-block:: console\n \n- ./vhost_crypto [EAL options] --\n+ ./dpdk-vhost_crypto [EAL options] --\n \t\t--config (lcore,cdev-id,queue-id)[,(lcore,cdev-id,queue-id)]\n \t\t--socket-file lcore,PATH\n \t\t[--zero-copy]\ndiff --git a/doc/guides/sample_app_ug/vm_power_management.rst b/doc/guides/sample_app_ug/vm_power_management.rst\nindex 1b6de8e936..35afdac63f 100644\n--- a/doc/guides/sample_app_ug/vm_power_management.rst\n+++ b/doc/guides/sample_app_ug/vm_power_management.rst\n@@ -245,26 +245,23 @@ To build just the ``vm_power_manager`` application using ``make``:\n \n .. code-block:: console\n \n- export RTE_SDK=/path/to/rte_sdk\n- export RTE_TARGET=build\n- cd ${RTE_SDK}/examples/vm_power_manager/\n+ cd dpdk/examples/vm_power_manager/\n make\n \n-The resulting binary is ``${RTE_SDK}/build/examples/vm_power_manager``.\n+The resulting binary is ``dpdk/build/examples/vm_power_manager``.\n \n To build just the ``vm_power_manager`` application using ``meson``/``ninja``:\n \n .. code-block:: console\n \n- export RTE_SDK=/path/to/rte_sdk\n- cd ${RTE_SDK}\n+ cd dpdk\n meson build\n cd build\n ninja\n meson configure -Dexamples=vm_power_manager\n ninja\n \n-The resulting binary is ``${RTE_SDK}/build/examples/dpdk-vm_power_manager``.\n+The resulting binary is ``dpdk/build/examples/dpdk-vm_power_manager``.\n \n Running the Host Application\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n@@ -274,7 +271,7 @@ than the EAL options:\n \n .. code-block:: console\n \n- ./build/vm_power_mgr [EAL options]\n+ ./<build_dir>/examples/dpdk-vm_power_mgr [EAL options]\n \n The application requires exactly two cores to run. One core for the CLI\n and the other for the channel endpoint monitor. For example, to run on\n@@ -282,7 +279,7 @@ cores 0 and 1 on a system with four memory channels, issue the command:\n \n .. code-block:: console\n \n- ./build/vm_power_mgr -l 0-1 -n 4\n+ ./<build_dir>/examples/dpdk-vm_power_mgr -l 0-1 -n 4\n \n After successful initialization, the VM Power Manager CLI prompt appears:\n \n@@ -462,12 +459,10 @@ the following commands:\n \n .. code-block:: console\n \n- export RTE_SDK=/path/to/rte_sdk\n- export RTE_TARGET=build\n- cd ${RTE_SDK}/examples/vm_power_manager/guest_cli/\n+ cd dpdk/examples/vm_power_manager/guest_cli/\n make\n \n-The resulting binary is ``${RTE_SDK}/build/examples/guest_cli``.\n+The resulting binary is ``dpdk/build/examples/guest_cli``.\n \n **Note**: This sample application conditionally links in the Jansson JSON\n library. Consequently, if you are using a multilib or cross-compile\n@@ -498,15 +493,14 @@ To build just the ``vm_power_manager`` application using ``meson``/``ninja``:\n \n .. code-block:: console\n \n- export RTE_SDK=/path/to/rte_sdk\n- cd ${RTE_SDK}\n+ cd dpdk\n meson build\n cd build\n ninja\n meson configure -Dexamples=vm_power_manager/guest_cli\n ninja\n \n-The resulting binary is ``${RTE_SDK}/build/examples/guest_cli``.\n+The resulting binary is ``dpdk/build/examples/guest_cli``.\n \n Running the Guest Application\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n@@ -515,14 +509,14 @@ The standard EAL command line parameters are necessary:\n \n .. code-block:: console\n \n- ./build/vm_power_mgr [EAL options] -- [guest options]\n+ ./<build_dir>/examples/dpdk-vm_power_mgr [EAL options] -- [guest options]\n \n The guest example uses a channel for each lcore enabled. For example, to\n run on cores 0, 1, 2 and 3:\n \n .. code-block:: console\n \n- ./build/guest_vm_power_mgr -l 0-3\n+ ./<build_dir>/examples/dpdk-guest_vm_power_mgr -l 0-3\n \n .. _sending_policy:\n \n@@ -593,7 +587,7 @@ host, use a command like the following:\n \n .. code-block:: console\n \n- ./build/guest_vm_power_mgr -l 0-3 -n 4 -- --vm-name=ubuntu --policy=BRANCH_RATIO --vcpu-list=2-4\n+ ./<build_dir>/examples/dpdk-guest_vm_power_mgr -l 0-3 -n 4 -- --vm-name=ubuntu --policy=BRANCH_RATIO --vcpu-list=2-4\n \n Once the VM Power Manager Guest CLI appears, issuing the 'send_policy now' command\n will send the policy to the host:\n@@ -707,7 +701,7 @@ To start the application and configure the power policy, and send it to the host\n \n .. code-block:: console\n \n- ./build/guest_vm_power_mgr -l 0-3 -n 4 -- --vm-name=ubuntu --policy=BRANCH_RATIO --vcpu-list=2-4\n+ ./<build_dir>/examples/dpdk-guest_vm_power_mgr -l 0-3 -n 4 -- --vm-name=ubuntu --policy=BRANCH_RATIO --vcpu-list=2-4\n \n Once the VM Power Manager Guest CLI appears, issuing the 'send_policy now' command\n will send the policy to the host:\ndiff --git a/doc/guides/sample_app_ug/vmdq_dcb_forwarding.rst b/doc/guides/sample_app_ug/vmdq_dcb_forwarding.rst\nindex 8e1774d9e2..c908074eb0 100644\n--- a/doc/guides/sample_app_ug/vmdq_dcb_forwarding.rst\n+++ b/doc/guides/sample_app_ug/vmdq_dcb_forwarding.rst\n@@ -26,13 +26,13 @@ multiple queues. When run with 8 threads, that is, with the -c FF option, each t\n 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`.\n The Intel® 82599 10 Gigabit Ethernet Controller NIC also supports the splitting of traffic into 16 pools of 8 queues. While the\n Intel® X710 or XL710 Ethernet Controller NICs support many configurations of VMDQ pools of 4 or 8 queues each. For simplicity, only 16\n-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\n-in config/common_* file.\n+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\n+in config/rte_config.h file.\n The nb-pools, nb-tcs and enable-rss parameters can be passed on the command line, after the EAL parameters:\n \n .. code-block:: console\n \n- ./build/vmdq_dcb [EAL options] -- -p PORTMASK --nb-pools NP --nb-tcs TC --enable-rss\n+ ./<build_dir>/examples/dpdk-vmdq_dcb [EAL options] -- -p PORTMASK --nb-pools NP --nb-tcs TC --enable-rss\n \n where, NP can be 16 or 32, TC can be 4 or 8, rss is disabled by default.\n \n@@ -72,7 +72,7 @@ To run the example in a linux environment:\n \n .. code-block:: console\n \n- user@target:~$ ./build/vmdq_dcb -l 0-3 -n 4 -- -p 0x3 --nb-pools 32 --nb-tcs 4\n+ user@target:~$ ./<build_dir>/examples/dpdk-vmdq_dcb -l 0-3 -n 4 -- -p 0x3 --nb-pools 32 --nb-tcs 4\n \n Refer to the *DPDK Getting Started Guide* for general information on running applications and\n the Environment Abstraction Layer (EAL) options.\ndiff --git a/doc/guides/sample_app_ug/vmdq_forwarding.rst b/doc/guides/sample_app_ug/vmdq_forwarding.rst\nindex c3a3439e51..a1a8e77de2 100644\n--- a/doc/guides/sample_app_ug/vmdq_forwarding.rst\n+++ b/doc/guides/sample_app_ug/vmdq_forwarding.rst\n@@ -24,13 +24,13 @@ multiple queues. When run with 8 threads, that is, with the -c FF option, each t\n As supplied, the sample application configures the VMDq feature to have 32 pools with 4 queues each.\n The Intel® 82599 10 Gigabit Ethernet Controller NIC also supports the splitting of traffic into 16 pools of 2 queues.\n While the Intel® X710 or XL710 Ethernet Controller NICs support many configurations of VMDq pools of 4 or 8 queues each.\n-And queues numbers for each VMDq pool can be changed by setting CONFIG_RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM\n-in config/common_* file.\n+And queues numbers for each VMDq pool can be changed by setting RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM\n+in config/rte_config.h file.\n The nb-pools and enable-rss parameters can be passed on the command line, after the EAL parameters:\n \n .. code-block:: console\n \n- ./build/vmdq_app [EAL options] -- -p PORTMASK --nb-pools NP --enable-rss\n+ ./<build_dir>/examples/dpdk-vmdq [EAL options] -- -p PORTMASK --nb-pools NP --enable-rss\n \n where, NP can be 8, 16 or 32, rss is disabled by default.\n \n@@ -56,7 +56,7 @@ To run the example in a Linux environment:\n \n .. code-block:: console\n \n- user@target:~$ ./build/vmdq_app -l 0-3 -n 4 -- -p 0x3 --nb-pools 16\n+ user@target:~$ ./<build_dir>/examples/dpdk-vmdq -l 0-3 -n 4 -- -p 0x3 --nb-pools 16\n \n Refer to the *DPDK Getting Started Guide* for general information on running applications and\n the Environment Abstraction Layer (EAL) options.\n", "prefixes": [ "v3", "33/37" ] }