Patch Detail
get:
Show a patch.
patch:
Update a patch.
put:
Update a patch.
GET /api/patches/76800/?format=api
{ "id": 76800, "url": "http://patches.dpdk.org/api/patches/76800/?format=api", "web_url": "http://patches.dpdk.org/project/dpdk/patch/20200907220711.437405-20-thomas@monjalon.net/", "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": "<20200907220711.437405-20-thomas@monjalon.net>", "list_archive_url": "https://inbox.dpdk.org/dev/20200907220711.437405-20-thomas@monjalon.net", "date": "2020-09-07T22:06:59", "name": "[v4,19/31] doc: remove references to make from prog guide", "commit_ref": null, "pull_url": null, "state": "superseded", "archived": true, "hash": "47fe2454ee1c81e7b340b33c01b372a53db89584", "submitter": { "id": 685, "url": "http://patches.dpdk.org/api/people/685/?format=api", "name": "Thomas Monjalon", "email": "thomas@monjalon.net" }, "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/20200907220711.437405-20-thomas@monjalon.net/mbox/", "series": [ { "id": 12000, "url": "http://patches.dpdk.org/api/series/12000/?format=api", "web_url": "http://patches.dpdk.org/project/dpdk/list/?series=12000", "date": "2020-09-07T22:06:40", "name": "remove make support in DPDK", "version": 4, "mbox": "http://patches.dpdk.org/series/12000/mbox/" } ], "comments": "http://patches.dpdk.org/api/patches/76800/comments/", "check": "warning", "checks": "http://patches.dpdk.org/api/patches/76800/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 9D7F8A04AA;\n\tTue, 8 Sep 2020 00:10:21 +0200 (CEST)", "from [92.243.14.124] (localhost [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id C4D591C243;\n\tTue, 8 Sep 2020 00:07:52 +0200 (CEST)", "from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com\n [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id B93B41C1C6\n for <dev@dpdk.org>; Tue, 8 Sep 2020 00:07:47 +0200 (CEST)", "from compute7.internal (compute7.nyi.internal [10.202.2.47])\n by mailout.nyi.internal (Postfix) with ESMTP id 8D7665C0098;\n Mon, 7 Sep 2020 18:07:47 -0400 (EDT)", "from mailfrontend1 ([10.202.2.162])\n by compute7.internal (MEProxy); Mon, 07 Sep 2020 18:07:47 -0400", "from xps.monjalon.net (184.203.134.77.rev.sfr.net [77.134.203.184])\n by mail.messagingengine.com (Postfix) with ESMTPA id B2B643280059;\n Mon, 7 Sep 2020 18:07:46 -0400 (EDT)" ], "DKIM-Signature": [ "v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=\n from:to:cc:subject:date:message-id:in-reply-to:references\n :mime-version:content-transfer-encoding; s=fm2; bh=8NhrkkYJ+mDid\n U5vEqfaOY89G31IqB2xYIfqinD8bTA=; b=XDzYetfld5ZGBIkLF49sV1O6VwmIU\n B21VScQM+xT6+eV3zgccuRGaVbsOK5tWS40wb/FSWa42aCroszP6UgTe2VPoqVjB\n nEiPYR2CdVx5c/lyQ5jtz3gsJk1YiAZNYR0tLkcsZEmoDBbfTYp4enG5BOLyGc01\n HjgF8b3frKSlsbfkwxWvRcpcAMhxcEM2lQs8tl17NgQme+pOBvrdn9LdtUMQV54B\n 1itFWw6G1dRX0EbvNT77G9wxAfDjiD8Vdl4ZH6hN6AL8Q9pmeodZlbJNYVLYrTtZ\n Q1oIZ4BBKVOaqIlZp8vBLevVj1YPtthUeR8IGqXbXZQkbcIgkkIDJqlfQ==", "v=1; a=rsa-sha256; c=relaxed/relaxed; d=\n messagingengine.com; h=cc:content-transfer-encoding:date:from\n :in-reply-to:message-id:mime-version:references:subject:to\n :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=\n fm3; bh=8NhrkkYJ+mDidU5vEqfaOY89G31IqB2xYIfqinD8bTA=; b=V3iomFZr\n 0EwaISDXV94BzAwQWavNTxZ3RJZxlFqaRFpJOE3pCWu4sS/Ft3iXxlcE/yyuwTY0\n I5umuOHjF5VLRsL6T6ELwrWJ6ZmWNZwiudqOGBmVvnSCaLH4/YKD6U0pTyL8S5fu\n rITIy7dmDO9TAliFz7JICobQIo3RBu/mRyWaTzVKovFfUUPmqpC9RTFBc8Hi5L4/\n NTZnsm2IJN9PeQW5NEeIzKXNr9C632F1RRSpv5A3niqkh4nfKjQ9z9lYrwTAqHTY\n rPVGRpHUkhI/zaetmyyxG6RobUAboY0MEWC4MdkT9wHj1qEaS4f5UOxY6uO5j5xi\n wy7K16pv3XM1Mg==" ], "X-ME-Sender": "<xms:M69WX7TLWdaAZCsQzhUjEX8v8FfF0-fEm9l1iR7C5NFazntIvdZ1SQ>\n <xme:M69WX8yPJRt_xzEyPyJxu6L2ypZb6ab3BL2dtHtsUaKscVW1_Aj_w95QQambdEr7L\n rV9fW5FF5ww3kjhsQ>", "X-ME-Proxy-Cause": "\n gggruggvucftvghtrhhoucdtuddrgeduiedrudehuddgtdefucetufdoteggodetrfdotf\n fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen\n uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne\n cujfgurhephffvufffkffojghfggfgsedtkeertdertddtnecuhfhrohhmpefvhhhomhgr\n shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg\n ftrfgrthhtvghrnhepvdehgfeivdejgedtveehfefhteelfefgieevgfffveefjeegtdfg\n uedthedtgeevnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghruf\n hiiigvpeejnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl\n ohhnrdhnvght", "X-ME-Proxy": "<xmx:M69WXw3an72AZlIpY1BdubK5UcdfdunliOPLDsAox3gGG3LmEcbFiw>\n <xmx:M69WX7Dx1uk5OVnFunjgzAiJsWKKJQWQyQrbnLTJTSmTxSEM88xObw>\n <xmx:M69WX0jMLFjPl6ENKXpBb8ICnB5slE5QG9pbYnuHF1bJsm4MO-8EKg>\n <xmx:M69WX3sa2isSBNqSVyR2gzhTSMxBHYRAbuBVBgR7RcrgnMmFTndv_g>", "From": "Thomas Monjalon <thomas@monjalon.net>", "To": "dev@dpdk.org", "Cc": "david.marchand@redhat.com, bruce.richardson@intel.com,\n ciara.power@intel.com, Kevin Laatz <kevin.laatz@intel.com>", "Date": "Tue, 8 Sep 2020 00:06:59 +0200", "Message-Id": "<20200907220711.437405-20-thomas@monjalon.net>", "X-Mailer": "git-send-email 2.28.0", "In-Reply-To": "<20200907220711.437405-1-thomas@monjalon.net>", "References": "<20200903152717.42095-1-ciara.power@intel.com>\n <20200907220711.437405-1-thomas@monjalon.net>", "MIME-Version": "1.0", "Content-Transfer-Encoding": "8bit", "Subject": "[dpdk-dev] [PATCH v4 19/31] doc: remove references to make from\n\tprog guide", "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": "From: Ciara Power <ciara.power@intel.com>\n\nMake is no longer supported for compiling DPDK, references are now\nremoved in the documentation.\n\nSigned-off-by: Ciara Power <ciara.power@intel.com>\nReviewed-by: Kevin Laatz <kevin.laatz@intel.com>\n---\n doc/guides/prog_guide/env_abstraction_layer.rst | 17 ++++++-----------\n doc/guides/prog_guide/graph_lib.rst | 6 ++----\n .../prog_guide/ip_fragment_reassembly_lib.rst | 5 -----\n doc/guides/prog_guide/kernel_nic_interface.rst | 14 +++++++-------\n .../link_bonding_poll_mode_drv_lib.rst | 15 ++++++++-------\n doc/guides/prog_guide/lto.rst | 12 +-----------\n doc/guides/prog_guide/mbuf_lib.rst | 4 ++--\n doc/guides/prog_guide/mempool_lib.rst | 7 +++----\n doc/guides/prog_guide/profile_app.rst | 17 +++--------------\n doc/guides/prog_guide/qos_framework.rst | 10 +---------\n doc/guides/prog_guide/rcu_lib.rst | 7 +++----\n doc/guides/prog_guide/trace_lib.rst | 3 +--\n .../prog_guide/writing_efficient_code.rst | 3 +--\n 13 files changed, 38 insertions(+), 82 deletions(-)", "diff": "diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/prog_guide/env_abstraction_layer.rst\nindex f64ae953d1..936c885081 100644\n--- a/doc/guides/prog_guide/env_abstraction_layer.rst\n+++ b/doc/guides/prog_guide/env_abstraction_layer.rst\n@@ -201,16 +201,16 @@ each segment is strictly one physical page. It is possible to change the amount\n of virtual memory being preallocated at startup by editing the following config\n variables:\n \n-* ``CONFIG_RTE_MAX_MEMSEG_LISTS`` controls how many segment lists can DPDK have\n-* ``CONFIG_RTE_MAX_MEM_MB_PER_LIST`` controls how much megabytes of memory each\n+* ``RTE_MAX_MEMSEG_LISTS`` controls how many segment lists can DPDK have\n+* ``RTE_MAX_MEM_MB_PER_LIST`` controls how much megabytes of memory each\n segment list can address\n-* ``CONFIG_RTE_MAX_MEMSEG_PER_LIST`` controls how many segments each segment can\n+* ``RTE_MAX_MEMSEG_PER_LIST`` controls how many segments each segment can\n have\n-* ``CONFIG_RTE_MAX_MEMSEG_PER_TYPE`` controls how many segments each memory type\n+* ``RTE_MAX_MEMSEG_PER_TYPE`` controls how many segments each memory type\n can have (where \"type\" is defined as \"page size + NUMA node\" combination)\n-* ``CONFIG_RTE_MAX_MEM_MB_PER_TYPE`` controls how much megabytes of memory each\n+* ``RTE_MAX_MEM_MB_PER_TYPE`` controls how much megabytes of memory each\n memory type can address\n-* ``CONFIG_RTE_MAX_MEM_MB`` places a global maximum on the amount of memory\n+* ``RTE_MAX_MEM_MB`` places a global maximum on the amount of memory\n DPDK can reserve\n \n Normally, these options do not need to be changed.\n@@ -715,11 +715,6 @@ However, they can be used in configuration code.\n Refer to the rte_malloc() function description in the *DPDK API Reference*\n manual for more information.\n \n-Cookies\n-~~~~~~~\n-\n-When CONFIG_RTE_MALLOC_DEBUG is enabled, the allocated memory contains\n-overwrite protection fields to help identify buffer overflows.\n \n Alignment and NUMA Constraints\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\ndiff --git a/doc/guides/prog_guide/graph_lib.rst b/doc/guides/prog_guide/graph_lib.rst\nindex 669d77c740..c922d10f3d 100644\n--- a/doc/guides/prog_guide/graph_lib.rst\n+++ b/doc/guides/prog_guide/graph_lib.rst\n@@ -45,13 +45,11 @@ Performance tuning parameters\n -----------------------------\n \n - Test with various burst size values (256, 128, 64, 32) using\n- CONFIG_RTE_GRAPH_BURST_SIZE config option.\n+ RTE_GRAPH_BURST_SIZE config option.\n The testing shows, on x86 and arm64 servers, The sweet spot is 256 burst\n size. While on arm64 embedded SoCs, it is either 64 or 128.\n-- Disable node statistics (using ``CONFIG_RTE_LIBRTE_GRAPH_STATS`` config option)\n+- Disable node statistics (using ``RTE_LIBRTE_GRAPH_STATS`` config option)\n if not needed.\n-- Use arm64 optimized memory copy for arm64 architecture by\n- selecting ``CONFIG_RTE_ARCH_ARM64_MEMCPY``.\n \n Programming model\n -----------------\ndiff --git a/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst b/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst\nindex 6ac1bba649..314d4adbb8 100644\n--- a/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst\n+++ b/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst\n@@ -103,8 +103,3 @@ Debug logging and Statistics Collection\n \n The RTE_LIBRTE_IP_FRAG_TBL_STAT config macro controls statistics collection for the Fragment Table.\n This macro is not enabled by default.\n-\n-The RTE_LIBRTE_IP_FRAG_DEBUG controls debug logging of IP fragments processing and reassembling.\n-This macro is disabled by default.\n-Note that while logging contains a lot of detailed information,\n-it slows down packet processing and might cause the loss of a lot of packets.\ndiff --git a/doc/guides/prog_guide/kernel_nic_interface.rst b/doc/guides/prog_guide/kernel_nic_interface.rst\nindex 32d09ccf82..de5d75bd4c 100644\n--- a/doc/guides/prog_guide/kernel_nic_interface.rst\n+++ b/doc/guides/prog_guide/kernel_nic_interface.rst\n@@ -65,7 +65,7 @@ disabled, and the default carrier state of KNI interfaces is set to *off*.\n \n .. code-block:: console\n \n- # insmod kmod/rte_kni.ko\n+ # insmod <build_dir>/kernel/linux/kni/rte_kni.ko\n \n .. _kni_loopback_mode:\n \n@@ -77,14 +77,14 @@ by specifying the ``lo_mode`` parameter:\n \n .. code-block:: console\n \n- # insmod kmod/rte_kni.ko lo_mode=lo_mode_fifo\n+ # insmod <build_dir>/kernel/linux/kni/rte_kni.ko lo_mode=lo_mode_fifo\n \n The ``lo_mode_fifo`` loopback option will loop back ring enqueue/dequeue\n operations in kernel space.\n \n .. code-block:: console\n \n- # insmod kmod/rte_kni.ko lo_mode=lo_mode_fifo_skb\n+ # insmod <build_dir>/kernel/linux/kni/rte_kni.ko lo_mode=lo_mode_fifo_skb\n \n The ``lo_mode_fifo_skb`` loopback option will loop back ring enqueue/dequeue\n operations and sk buffer copies in kernel space.\n@@ -105,7 +105,7 @@ Single kernel thread mode is enabled as follows:\n \n .. code-block:: console\n \n- # insmod kmod/rte_kni.ko kthread_mode=single\n+ # insmod <build_dir>/kernel/linux/kni/rte_kni.ko kthread_mode=single\n \n This mode will create only one kernel thread for all KNI interfaces to\n receive data on the kernel side. By default, this kernel thread is not\n@@ -122,7 +122,7 @@ kernel thread mode is enabled as follows:\n \n .. code-block:: console\n \n- # insmod kmod/rte_kni.ko kthread_mode=multiple\n+ # insmod <build_dir>/kernel/linux/kni/rte_kni.ko kthread_mode=multiple\n \n This mode will create a separate kernel thread for each KNI interface to\n receive data on the kernel side. The core affinity of each ``kni_thread``\n@@ -163,13 +163,13 @@ To set the default carrier state to *on*:\n \n .. code-block:: console\n \n- # insmod kmod/rte_kni.ko carrier=on\n+ # insmod <build_dir>/kernel/linux/kni/rte_kni.ko carrier=on\n \n To set the default carrier state to *off*:\n \n .. code-block:: console\n \n- # insmod kmod/rte_kni.ko carrier=off\n+ # insmod <build_dir>/kernel/linux/kni/rte_kni.ko carrier=off\n \n If the ``carrier`` parameter is not specified, the default carrier state\n of KNI interfaces will be set to *off*.\ndiff --git a/doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst b/doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst\nindex 2459fd243e..244dca56c4 100644\n--- a/doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst\n+++ b/doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst\n@@ -28,8 +28,9 @@ bonded device and its slave devices.\n .. note::\n \n The Link Bonding PMD Library is enabled by default in the build\n- configuration files, the library can be disabled by setting\n- ``CONFIG_RTE_LIBRTE_PMD_BOND=n`` and recompiling the DPDK.\n+ configuration, the library can be disabled using the meson option\n+ \"-Ddisable_drivers=net/bond\".\n+\n \n Link Bonding Modes Overview\n ---------------------------\n@@ -377,7 +378,7 @@ Device names and bonding options must be separated by commas as shown below:\n \n .. code-block:: console\n \n- $RTE_TARGET/app/testpmd -l 0-3 -n 4 --vdev 'net_bonding0,bond_opt0=..,bond opt1=..'--vdev 'net_bonding1,bond _opt0=..,bond_opt1=..'\n+ ./<build_dir>/app/dpdk-testpmd -l 0-3 -n 4 --vdev 'net_bonding0,bond_opt0=..,bond opt1=..'--vdev 'net_bonding1,bond _opt0=..,bond_opt1=..'\n \n Link Bonding EAL Options\n ^^^^^^^^^^^^^^^^^^^^^^^^\n@@ -477,22 +478,22 @@ Create a bonded device in round robin mode with two slaves specified by their PC\n \n .. code-block:: console\n \n- $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\n+ ./<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\n \n Create a bonded device in round robin mode with two slaves specified by their PCI address and an overriding MAC address:\n \n .. code-block:: console\n \n- $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\n+ ./<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\n \n Create a bonded device in active backup mode with two slaves specified, and a primary slave specified by their PCI addresses:\n \n .. code-block:: console\n \n- $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\n+ ./<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\n \n Create a bonded device in balance mode with two slaves specified by their PCI addresses, and a transmission policy of layer 3 + 4 forwarding:\n \n .. code-block:: console\n \n- $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\n+ ./<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\ndiff --git a/doc/guides/prog_guide/lto.rst b/doc/guides/prog_guide/lto.rst\nindex 277a6f1090..f79c449598 100644\n--- a/doc/guides/prog_guide/lto.rst\n+++ b/doc/guides/prog_guide/lto.rst\n@@ -26,17 +26,7 @@ need to explicitly initialize variable in order to silence the compiler.\n Please note that turning LTO on causes considerable extension of\n build time.\n \n-When using make based build, link time optimization can be enabled for\n-the whole DPDK by setting:\n-\n-.. code-block:: console\n-\n- CONFIG_RTE_ENABLE_LTO=y\n-\n-in config file.\n-\n-For the meson based build it can be enabled by setting meson built-in\n-'b_lto' option:\n+Link time optimization can be enabled by setting meson built-in 'b_lto' option:\n \n .. code-block:: console\n \ndiff --git a/doc/guides/prog_guide/mbuf_lib.rst b/doc/guides/prog_guide/mbuf_lib.rst\nindex c3dbfb9221..2f190b40e4 100644\n--- a/doc/guides/prog_guide/mbuf_lib.rst\n+++ b/doc/guides/prog_guide/mbuf_lib.rst\n@@ -266,8 +266,8 @@ can be found in several of the sample applications, for example, the IPv4 Multic\n Debug\n -----\n \n-In debug mode (CONFIG_RTE_MBUF_DEBUG is enabled),\n-the functions of the mbuf library perform sanity checks before any operation (such as, buffer corruption, bad type, and so on).\n+In debug mode, the functions of the mbuf library perform sanity checks before any operation (such as, buffer corruption,\n+bad type, and so on).\n \n Use Cases\n ---------\ndiff --git a/doc/guides/prog_guide/mempool_lib.rst b/doc/guides/prog_guide/mempool_lib.rst\nindex e3e1f940be..f0bdcd3be1 100644\n--- a/doc/guides/prog_guide/mempool_lib.rst\n+++ b/doc/guides/prog_guide/mempool_lib.rst\n@@ -17,14 +17,13 @@ This library is used by the :ref:`Mbuf Library <Mbuf_Library>`.\n Cookies\n -------\n \n-In debug mode (CONFIG_RTE_LIBRTE_MEMPOOL_DEBUG is enabled), cookies are added at the beginning and end of allocated blocks.\n+In debug mode, cookies are added at the beginning and end of allocated blocks.\n The allocated objects then contain overwrite protection fields to help debugging buffer overflows.\n \n Stats\n -----\n \n-In debug mode (CONFIG_RTE_LIBRTE_MEMPOOL_DEBUG is enabled),\n-statistics about get from/put in the pool are stored in the mempool structure.\n+In debug mode, statistics about get from/put in the pool are stored in the mempool structure.\n Statistics are per-lcore to avoid concurrent access to statistics counters.\n \n Memory Alignment Constraints on x86 architecture\n@@ -90,7 +89,7 @@ the speed at which a core can access its own cache for a specific memory pool wi\n The cache is composed of a small, per-core table of pointers and its length (used as a stack).\n This internal cache can be enabled or disabled at creation of the pool.\n \n-The maximum size of the cache is static and is defined at compilation time (CONFIG_RTE_MEMPOOL_CACHE_MAX_SIZE).\n+The maximum size of the cache is static and is defined at compilation time (RTE_MEMPOOL_CACHE_MAX_SIZE).\n \n :numref:`figure_mempool` shows a cache in operation.\n \ndiff --git a/doc/guides/prog_guide/profile_app.rst b/doc/guides/prog_guide/profile_app.rst\nindex e5d0e9079e..7093681983 100644\n--- a/doc/guides/prog_guide/profile_app.rst\n+++ b/doc/guides/prog_guide/profile_app.rst\n@@ -33,14 +33,6 @@ Refer to the\n for details about application profiling.\n \n \n-Profiling with VTune\n-~~~~~~~~~~~~~~~~~~~~\n-\n-To allow VTune attaching to the DPDK application, reconfigure and recompile\n-the DPDK with ``CONFIG_RTE_ETHDEV_RXTX_CALLBACKS`` and\n-``CONFIG_RTE_ETHDEV_PROFILE_WITH_VTUNE`` enabled.\n-\n-\n Profiling on ARM64\n ------------------\n \n@@ -76,8 +68,7 @@ cycle counter for user space access by configuring the PMU from the privileged\n mode (kernel space).\n \n By default the ``rte_rdtsc()`` implementation uses a portable ``cntvct_el0``\n-scheme. Application can choose the PMU based implementation with\n-``CONFIG_RTE_ARM_EAL_RDTSC_USE_PMU``.\n+scheme.\n \n The example below shows the steps to configure the PMU based cycle counter on\n an ARMv8 machine.\n@@ -88,10 +79,8 @@ an ARMv8 machine.\n cd armv8_pmu_cycle_counter_el0\n make\n sudo insmod pmu_el0_cycle_counter.ko\n- cd $DPDK_DIR\n- make config T=arm64-armv8a-linux-gcc\n- echo \"CONFIG_RTE_ARM_EAL_RDTSC_USE_PMU=y\" >> build/.config\n- make\n+\n+Please refer to :doc:`../linux_gsg/build_dpdk` for details on compiling DPDK with meson.\n \n .. warning::\n \ndiff --git a/doc/guides/prog_guide/qos_framework.rst b/doc/guides/prog_guide/qos_framework.rst\nindex a159709450..4e4ea33ccb 100644\n--- a/doc/guides/prog_guide/qos_framework.rst\n+++ b/doc/guides/prog_guide/qos_framework.rst\n@@ -1525,15 +1525,7 @@ Integration with the DPDK QoS Scheduler\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n \n RED functionality in the DPDK QoS scheduler is disabled by default.\n-To enable it, use the DPDK configuration parameter:\n-\n-::\n-\n- CONFIG_RTE_SCHED_RED=y\n-\n-This parameter must be set to y.\n-The parameter is found in the build configuration files in the DPDK/config directory,\n-for example, DPDK/config/common_linux.\n+The parameter is found in the build configuration files in the DPDK/config directory.\n RED configuration parameters are specified in the rte_red_params structure within the rte_sched_port_params structure\n that is passed to the scheduler on initialization.\n RED parameters are specified separately for four traffic classes and three packet colors (green, yellow and red)\ndiff --git a/doc/guides/prog_guide/rcu_lib.rst b/doc/guides/prog_guide/rcu_lib.rst\nindex d142d0c79d..d0aef3bc16 100644\n--- a/doc/guides/prog_guide/rcu_lib.rst\n+++ b/doc/guides/prog_guide/rcu_lib.rst\n@@ -186,10 +186,9 @@ they entered a quiescent state. This API checks if a writer has triggered a\n quiescent state query and update the state accordingly.\n \n The ``rte_rcu_qsbr_lock()`` and ``rte_rcu_qsbr_unlock()`` are empty functions.\n-However, when ``CONFIG_RTE_LIBRTE_RCU_DEBUG`` is enabled, these APIs aid\n-in debugging issues. One can mark the access to shared data structures on the\n-reader side using these APIs. The ``rte_rcu_qsbr_quiescent()`` will check if\n-all the locks are unlocked.\n+However, these APIs can aid in debugging issues. One can mark the access to\n+shared data structures on the reader side using these APIs. The\n+``rte_rcu_qsbr_quiescent()`` will check if all the locks are unlocked.\n \n Resource reclamation framework for DPDK\n ---------------------------------------\ndiff --git a/doc/guides/prog_guide/trace_lib.rst b/doc/guides/prog_guide/trace_lib.rst\nindex 9bbfd165d8..fbadf9fde9 100644\n--- a/doc/guides/prog_guide/trace_lib.rst\n+++ b/doc/guides/prog_guide/trace_lib.rst\n@@ -135,8 +135,7 @@ In order to avoid performance impact in fast path code, the library introduced\n the user must use ``RTE_TRACE_POINT_FP`` instead of ``RTE_TRACE_POINT``.\n \n ``RTE_TRACE_POINT_FP`` is compiled out by default and it can be enabled using\n-``CONFIG_RTE_ENABLE_TRACE_FP`` configuration parameter.\n-The ``enable_trace_fp`` option shall be used for the same for meson build.\n+the ``enable_trace_fp`` option for meson build.\n \n Event record mode\n -----------------\ndiff --git a/doc/guides/prog_guide/writing_efficient_code.rst b/doc/guides/prog_guide/writing_efficient_code.rst\nindex 2639ef7bf6..db2f1ddbc2 100644\n--- a/doc/guides/prog_guide/writing_efficient_code.rst\n+++ b/doc/guides/prog_guide/writing_efficient_code.rst\n@@ -258,8 +258,7 @@ For instance:\n Setting the Target CPU Type\n ---------------------------\n \n-The DPDK supports CPU microarchitecture-specific optimizations by means of CONFIG_RTE_MACHINE option\n-in the DPDK configuration file.\n+The DPDK supports CPU microarchitecture-specific optimizations by means of RTE_MACHINE option.\n The degree of optimization depends on the compiler's ability to optimize for a specific microarchitecture,\n therefore it is preferable to use the latest compiler versions whenever possible.\n \n", "prefixes": [ "v4", "19/31" ] }