From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 14763469FD; Tue, 24 Jun 2025 15:34:52 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id F39E340A72; Tue, 24 Jun 2025 15:34:51 +0200 (CEST) Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.16]) by mails.dpdk.org (Postfix) with ESMTP id C00AF40A67 for ; Tue, 24 Jun 2025 15:34:49 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1750772091; x=1782308091; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=vQImWxYwXEt1kkZ4Pj1SzaaYkExlh1xKdAHcOJao1AY=; b=b16C9yFeIIyRfZBEv6OyQUjEEmKaNLKr5JxnB/l/R6I6Z7iQnlwObkJq Pv9ApSuHCahJdb07RurWwd6Dv31/uPO2dlrsQ+ukgYXbLEMAJHWfWXsJW j1/wJiZeF1emJA8ddhAQnP16CBQUP/nH+7A9qUsa+MGN/hqaQ77y9Lflz NI8scgqsUWy8hqxJAeg1LOKcZQfVUCJwGNwTSHpcWrA45BBYRkt4GB6+o Rnifh2OvQrPp6+ArBruI1Zfq66L/m0XpPGdRFnPCDQFpMqDNoOqz779B8 pxIHqnZXYM6dlKo45nzs5o/E4GC5Acb8uuuhJa6GNmhNI0U+gzq07xhRB Q==; X-CSE-ConnectionGUID: sxjiTB2lTeG2FXdG74BVYQ== X-CSE-MsgGUID: 54iJH2yNQPaC5Dlu9amkDA== X-IronPort-AV: E=McAfee;i="6800,10657,11474"; a="53112078" X-IronPort-AV: E=Sophos;i="6.16,261,1744095600"; d="scan'208";a="53112078" Received: from fmviesa004.fm.intel.com ([10.60.135.144]) by orvoesa108.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Jun 2025 06:34:32 -0700 X-CSE-ConnectionGUID: KiRbSHpzRhOZfSfLSlr4iw== X-CSE-MsgGUID: Ddv3ERTTSYW9RNEaBAVTNA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.16,261,1744095600"; d="scan'208";a="157410781" Received: from silpixa00401385.ir.intel.com ([10.237.214.33]) by fmviesa004.fm.intel.com with ESMTP; 24 Jun 2025 06:34:25 -0700 From: Bruce Richardson To: dev@dpdk.org Cc: Bruce Richardson , Nicolas Chautru , Anoob Joseph , Pravin Pathak , Ashwin Sekhar T K , Pavan Nikhilesh , Nithin Dabilpuram , Kiran Kumar K , Sunil Kumar Kori , Satha Rao , Harman Kalra , Praveen Shetty , Hemant Agrawal , Sachin Saxena , Gaetan Rivet , Anatoly Burakov , Cristian Dumitrescu , Harry van Haaren , Radu Nicolau , Akhil Goyal , Jingjing Wu , Maxime Coquelin , Chenbo Xia , Kai Ji , Rakesh Kudurumalla , Jerin Jacob , Srikanth Yalavarthi Subject: [PATCH 2/2] doc: use core lists rather than masks in guides Date: Tue, 24 Jun 2025 14:34:08 +0100 Message-ID: <20250624133409.550372-3-bruce.richardson@intel.com> X-Mailer: git-send-email 2.48.1 In-Reply-To: <20250624133409.550372-1-bruce.richardson@intel.com> References: <20250624133409.550372-1-bruce.richardson@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org For the guides for applications and examples, use the "-l" flag rather than the "-c" flag to pass in core lists rather than core masks. While for the trivial examples given, core masks work fine and may be easier; in real-world cases, with potentially hundreds of cores, core lists are a much better fix, so update the docs to reflect this. Similarly replace instances of "-s " with "-S ". Signed-off-by: Bruce Richardson --- doc/guides/bbdevs/acc100.rst | 2 +- doc/guides/bbdevs/fpga_5gnr_fec.rst | 4 +- doc/guides/bbdevs/fpga_lte_fec.rst | 2 +- doc/guides/bbdevs/vrb1.rst | 2 +- doc/guides/bbdevs/vrb2.rst | 2 +- doc/guides/cryptodevs/octeontx.rst | 2 +- doc/guides/eventdevs/dlb2.rst | 6 +-- doc/guides/faq/faq.rst | 8 ++-- doc/guides/freebsd_gsg/build_sample_apps.rst | 8 ++-- doc/guides/howto/packet_capture_framework.rst | 2 +- doc/guides/linux_gsg/build_sample_apps.rst | 10 ++--- doc/guides/mempool/cnxk.rst | 2 +- doc/guides/mempool/octeontx.rst | 2 +- doc/guides/nics/cnxk.rst | 2 +- doc/guides/nics/cpfl.rst | 2 +- doc/guides/nics/dpaa.rst | 2 +- doc/guides/nics/dpaa2.rst | 4 +- doc/guides/nics/fail_safe.rst | 8 ++-- doc/guides/nics/ice.rst | 4 +- doc/guides/nics/softnic.rst | 4 +- doc/guides/prog_guide/meson_ut.rst | 2 +- doc/guides/prog_guide/multi_proc_support.rst | 2 +- doc/guides/prog_guide/service_cores.rst | 8 ++-- doc/guides/sample_app_ug/bbdev_app.rst | 6 +-- doc/guides/sample_app_ug/ip_pipeline.rst | 2 +- doc/guides/sample_app_ug/ipsec_secgw.rst | 4 +- .../sample_app_ug/l2_forward_macsec.rst | 4 +- doc/guides/sample_app_ug/l3_forward.rst | 2 +- doc/guides/sample_app_ug/multi_process.rst | 8 ++-- doc/guides/sample_app_ug/ntb.rst | 2 +- doc/guides/sample_app_ug/pipeline.rst | 2 +- doc/guides/sample_app_ug/qos_scheduler.rst | 2 +- doc/guides/sample_app_ug/test_pipeline.rst | 2 +- doc/guides/sample_app_ug/vdpa.rst | 2 +- doc/guides/tools/comp_perf.rst | 5 +-- doc/guides/tools/cryptoperf.rst | 5 +-- doc/guides/tools/graph.rst | 13 +++---- doc/guides/tools/testbbdev.rst | 2 +- doc/guides/tools/testeventdev.rst | 39 +++++++++---------- doc/guides/tools/testmldev.rst | 27 +++++++------ 40 files changed, 105 insertions(+), 112 deletions(-) diff --git a/doc/guides/bbdevs/acc100.rst b/doc/guides/bbdevs/acc100.rst index 38a7a11d4e..6843e38c55 100644 --- a/doc/guides/bbdevs/acc100.rst +++ b/doc/guides/bbdevs/acc100.rst @@ -153,4 +153,4 @@ Specifically for the BBDEV ACC100 PMD, the command below can be used: .. code-block:: console ./pf_bb_config ACC100 -c acc100/acc100_config_vf_5g.cfg - ./test-bbdev.py -e="-c 0xff0 -a${VF_PCI_ADDR}" -c validation -n 64 -b 32 -l 1 -v ./ldpc_dec_default.data + ./test-bbdev.py -e="-l 4-11 -a${VF_PCI_ADDR}" -c validation -n 64 -b 32 -l 1 -v ./ldpc_dec_default.data diff --git a/doc/guides/bbdevs/fpga_5gnr_fec.rst b/doc/guides/bbdevs/fpga_5gnr_fec.rst index 5301076d93..58d19ffbd2 100644 --- a/doc/guides/bbdevs/fpga_5gnr_fec.rst +++ b/doc/guides/bbdevs/fpga_5gnr_fec.rst @@ -231,11 +231,11 @@ Vista Creek (N3000) .. code-block:: console ./pf_bb_config FPGA_5GNR -c fpga_5gnr/fpga_5gnr_config_vf.cfg - ./test-bbdev.py -e="-c 0xff0 -a${VF_PCI_ADDR}" -c validation -n 64 -b 32 -l 1 -v ./ldpc_dec_default.data + ./test-bbdev.py -e="-l 4-11 -a${VF_PCI_ADDR}" -c validation -n 64 -b 32 -l 1 -v ./ldpc_dec_default.data Arrow Creek (N6000) .. code-block:: console ./pf_bb_config AGX100 -c agx100/agx100_config_1vf.cfg - ./test-bbdev.py -e="-c 0xff0 -a${VF_PCI_ADDR}" -c validation -n 64 -b 32 -l 1 -v ./ldpc_dec_default.data + ./test-bbdev.py -e="-l 4-11 -a${VF_PCI_ADDR}" -c validation -n 64 -b 32 -l 1 -v ./ldpc_dec_default.data diff --git a/doc/guides/bbdevs/fpga_lte_fec.rst b/doc/guides/bbdevs/fpga_lte_fec.rst index 34ca18ecc6..7e3748222c 100644 --- a/doc/guides/bbdevs/fpga_lte_fec.rst +++ b/doc/guides/bbdevs/fpga_lte_fec.rst @@ -211,4 +211,4 @@ Specifically for the BBDEV FPGA LTE FEC PMD, the command below can be used: .. code-block:: console ./pf_bb_config FPGA_LTE -c fpga_lte/fpga_lte_config_vf.cfg - ./test-bbdev.py -e="-c 0xff0 -a${VF_PCI_ADDR}" -c validation -n 64 -b 32 -l 1 -v ./turbo_dec_default.data + ./test-bbdev.py -e="-l 4-11 -a${VF_PCI_ADDR}" -c validation -n 64 -b 32 -l 1 -v ./turbo_dec_default.data diff --git a/doc/guides/bbdevs/vrb1.rst b/doc/guides/bbdevs/vrb1.rst index e450e0061f..255c4ea040 100644 --- a/doc/guides/bbdevs/vrb1.rst +++ b/doc/guides/bbdevs/vrb1.rst @@ -163,4 +163,4 @@ Specifically for the bbdev Intel vRAN Boost v1 PMD, the command below can be use .. code-block:: console pf_bb_config ACC200 -c ./acc200/acc200_config_vf_5g.cfg - test-bbdev.py -e="-c 0xff0 -a${VF_PCI_ADDR}" -c validation -n 64 -b 64 -l 1 -v ./ldpc_dec_default.data + test-bbdev.py -e="-l 4-11 -a${VF_PCI_ADDR}" -c validation -n 64 -b 64 -l 1 -v ./ldpc_dec_default.data diff --git a/doc/guides/bbdevs/vrb2.rst b/doc/guides/bbdevs/vrb2.rst index 5389d533f5..45c83e875f 100644 --- a/doc/guides/bbdevs/vrb2.rst +++ b/doc/guides/bbdevs/vrb2.rst @@ -175,4 +175,4 @@ Specifically for the bbdev Intel vRAN Boost v2 PMD, the command below can be use .. code-block:: console pf_bb_config VRB2 -c ./vrb2/vrb2_config_vf_5g.cfg - test-bbdev.py -e="-c 0xff0 -a${VF_PCI_ADDR}" -c validation -n 64 -b 64 -l 1 -v ./ldpc_dec_default.data + test-bbdev.py -e="-l 4-11 -a${VF_PCI_ADDR}" -c validation -n 64 -b 64 -l 1 -v ./ldpc_dec_default.data diff --git a/doc/guides/cryptodevs/octeontx.rst b/doc/guides/cryptodevs/octeontx.rst index a39f3f3d02..8b0eb8a979 100644 --- a/doc/guides/cryptodevs/octeontx.rst +++ b/doc/guides/cryptodevs/octeontx.rst @@ -114,7 +114,7 @@ OCTEON TX crypto PMD. .. code-block:: console - ./build/ipsec-secgw --log-level=8 -c 0xff -- -P -p 0x3 -u 0x2 --config + ./build/ipsec-secgw --log-level=8 -l 0-7 -- -P -p 0x3 -u 0x2 --config "(1,0,0),(0,0,0)" -f ep1.cfg Testing diff --git a/doc/guides/eventdevs/dlb2.rst b/doc/guides/eventdevs/dlb2.rst index 8ec7168f20..daa8bf27fb 100644 --- a/doc/guides/eventdevs/dlb2.rst +++ b/doc/guides/eventdevs/dlb2.rst @@ -408,9 +408,9 @@ the DLB device locally available on the same tile along with other resources. To allocate optimal resources, probing is done for each producer port (PP) for a given CPU and the best performing ports are allocated to producers. The cpu used for probing is either the first -core of producer coremask (if present) or the second core of EAL -coremask. This will be extended later to probe for all CPUs in the -producer coremask or EAL coremask. Producer coremask can be passed +core of producer coremask DLB2 device parameter (if present) or the second core of EAL +core list. This will be extended later to probe for all CPUs in the +producer coremask or EAL core list. Producer coremask can be passed along with the BDF of the DLB devices. .. code-block:: console diff --git a/doc/guides/faq/faq.rst b/doc/guides/faq/faq.rst index c7a774da2a..d675c870ff 100644 --- a/doc/guides/faq/faq.rst +++ b/doc/guides/faq/faq.rst @@ -47,11 +47,9 @@ therefore all the hugepages are allocated on the wrong socket. To avoid this scenario, either lower the amount of hugepage memory available to 1 GB size (or less), or run the application with taskset affinitizing the application to a would-be main core. -For example, if your EAL coremask is 0xff0, the main core will usually be the first core in the coremask (0x10); this is what you have to supply to taskset:: +For example, if your EAL core list is '4-11', the main core will usually be the first core in the list (core 4); this is what you have to supply to taskset:: - taskset 0x10 ./l2fwd -l 4-11 -n 2 - -.. Note: Instead of '-c 0xff0' use the '-l 4-11' as a cleaner way to define lcores. + taskset -c 4 ./l2fwd -l 4-11 -n 2 In this way, the hugepages have a greater chance of being allocated to the correct socket. Additionally, a ``--numa-mem`` option could be used to ensure the availability of memory for each socket, so that if hugepages were allocated on @@ -167,7 +165,7 @@ Can I split packet RX to use DPDK and have an application's higher order functio ---------------------------------------------------------------------------------------------------------------- The DPDK's lcore threads are Linux pthreads bound onto specific cores. Configure the DPDK to do work on the same -cores and run the application's other work on other cores using the DPDK's "coremask" setting to specify which +cores and run the application's other work on other cores using the DPDK's "core list" (-l/--lcores) setting to specify which cores it should launch itself on. diff --git a/doc/guides/freebsd_gsg/build_sample_apps.rst b/doc/guides/freebsd_gsg/build_sample_apps.rst index 7bdd88e56d..112c524a43 100644 --- a/doc/guides/freebsd_gsg/build_sample_apps.rst +++ b/doc/guides/freebsd_gsg/build_sample_apps.rst @@ -61,10 +61,10 @@ A large number of options can be given to the EAL when running an application. A full list of options can be got by passing `--help` to a DPDK application. Some of the EAL options for FreeBSD are as follows: -* ``-c COREMASK`` or ``-l CORELIST``: - A hexadecimal bit mask of the cores to run on. Note that core numbering - can change between platforms and should be determined beforehand. The corelist - is a list of cores to use instead of a core mask. +* ``-l CORELIST``: + A comma-separated list of the cores, or ranges of cores to run on. + For example, ``-l 0,1,4-6`` will run on cores 0, 1, 4, 5 and 6. + Note that core numbering can change between platforms and should be determined beforehand. * ``-b ``: Blocklisting of ports; prevent EAL from using specified PCI device diff --git a/doc/guides/howto/packet_capture_framework.rst b/doc/guides/howto/packet_capture_framework.rst index 24d4bd0e73..8e64e7a83e 100644 --- a/doc/guides/howto/packet_capture_framework.rst +++ b/doc/guides/howto/packet_capture_framework.rst @@ -89,7 +89,7 @@ inspect them using ``tcpdump``. #. Launch testpmd as the primary application:: - sudo /app/dpdk-testpmd -c 0xf0 -n 4 -- -i --port-topology=chained + sudo /app/dpdk-testpmd -l 4-7 -n 4 -- -i --port-topology=chained #. Launch the dpdk-dumpcap as follows:: diff --git a/doc/guides/linux_gsg/build_sample_apps.rst b/doc/guides/linux_gsg/build_sample_apps.rst index 5746a623f8..8b8026705b 100644 --- a/doc/guides/linux_gsg/build_sample_apps.rst +++ b/doc/guides/linux_gsg/build_sample_apps.rst @@ -33,16 +33,16 @@ The following is the list of options that can be given to the EAL: .. code-block:: console - ./rte-app [-c COREMASK | -l CORELIST] [-n NUM] [-b ] \ + ./rte-app [ -l CORELIST] [-n NUM] [-b ] \ [--numa-mem=MB,...] [-d LIB.so|DIR] [-m MB] [-r NUM] [-v] [--file-prefix] \ [--proc-type ] The EAL options are as follows: -* ``-c COREMASK`` or ``-l CORELIST``: - An hexadecimal bit mask of the cores to run on. Note that core numbering can - change between platforms and should be determined beforehand. The corelist is - a set of core numbers instead of a bitmap core mask. +* ``-l CORELIST``: + A comma-separated list of the cores, or ranges of cores to run on. + For example, ``-l 0,1,4-6`` will run on cores 0, 1, 4, 5 and 6. + Note that core numbering can change between platforms and should be determined beforehand. * ``-n NUM``: Number of memory channels per processor socket. diff --git a/doc/guides/mempool/cnxk.rst b/doc/guides/mempool/cnxk.rst index ffd9a6de86..3d0729245a 100644 --- a/doc/guides/mempool/cnxk.rst +++ b/doc/guides/mempool/cnxk.rst @@ -88,4 +88,4 @@ Standalone mempool device Example command to run ``mempool_autotest`` test with standalone CN10K NPA device:: - echo "mempool_autotest" | /app/test/dpdk-test -c 0xf0 --mbuf-pool-ops-name="cn10k_mempool_ops" + echo "mempool_autotest" | /app/test/dpdk-test -l 4-7 --mbuf-pool-ops-name="cn10k_mempool_ops" diff --git a/doc/guides/mempool/octeontx.rst b/doc/guides/mempool/octeontx.rst index 51915af96a..eeaa7fb1dc 100644 --- a/doc/guides/mempool/octeontx.rst +++ b/doc/guides/mempool/octeontx.rst @@ -60,5 +60,5 @@ Example: .. code-block:: console - .//app/test/dpdk-test -c 0xf --base-virtaddr=0x100000000000 \ + .//app/test/dpdk-test -l 0-3 --base-virtaddr=0x100000000000 \ --mbuf-pool-ops-name="octeontx_fpavf" diff --git a/doc/guides/nics/cnxk.rst b/doc/guides/nics/cnxk.rst index 3c1baed478..2ba0c9e058 100644 --- a/doc/guides/nics/cnxk.rst +++ b/doc/guides/nics/cnxk.rst @@ -63,7 +63,7 @@ for details. .. code-block:: console - .//app/dpdk-testpmd -c 0xc -a 0002:02:00.0 -- --portmask=0x1 --nb-cores=1 --port-topology=loop --rxq=1 --txq=1 + .//app/dpdk-testpmd -l 2,3 -a 0002:02:00.0 -- --portmask=0x1 --nb-cores=1 --port-topology=loop --rxq=1 --txq=1 EAL: Detected 4 lcore(s) EAL: Detected 1 NUMA nodes EAL: Multi-process socket /var/run/dpdk/rte/mp_socket diff --git a/doc/guides/nics/cpfl.rst b/doc/guides/nics/cpfl.rst index 3bfab2136d..e8bb1966cf 100644 --- a/doc/guides/nics/cpfl.rst +++ b/doc/guides/nics/cpfl.rst @@ -213,7 +213,7 @@ low level hardware resources. .. code-block:: console - dpdk-testpmd -c 0x3 -n 4 -a 0000:af:00.6,vport=[0-1],flow_parser="refpkg.json" -- -i + dpdk-testpmd -l 0,1 -n 4 -a 0000:af:00.6,vport=[0-1],flow_parser="refpkg.json" -- -i #. Create one flow to forward ETH-IPV4-TCP from I/O port to a local(CPF's) vport. Flow should be created on vport X. Group M should match fxp module. Action port_representor Y means forward packet to local vport Y:: diff --git a/doc/guides/nics/dpaa.rst b/doc/guides/nics/dpaa.rst index de3ae96e07..8748ee767e 100644 --- a/doc/guides/nics/dpaa.rst +++ b/doc/guides/nics/dpaa.rst @@ -254,7 +254,7 @@ for details. .. code-block:: console - .//app/dpdk-testpmd -c 0xff -n 1 \ + .//app/dpdk-testpmd -l 0-7 -n 1 \ -- -i --portmask=0x3 --nb-cores=1 --no-flush-rx ..... diff --git a/doc/guides/nics/dpaa2.rst b/doc/guides/nics/dpaa2.rst index 3175a8b421..94bf1907df 100644 --- a/doc/guides/nics/dpaa2.rst +++ b/doc/guides/nics/dpaa2.rst @@ -445,7 +445,7 @@ for details. .. code-block:: console - ./dpdk-testpmd -c 0xff -n 1 -- -i --portmask=0x3 --nb-cores=1 --no-flush-rx + ./dpdk-testpmd -l 0-7 -n 1 -- -i --portmask=0x3 --nb-cores=1 --no-flush-rx ..... EAL: Registered [pci] bus. @@ -607,7 +607,7 @@ For a detailed usage description please refer to "Traffic Management" section in .. code-block:: console - ./dpdk-testpmd -c 0xf -n 1 -- -i --portmask 0x3 --nb-cores=1 --txq=4 --rxq=4 + ./dpdk-testpmd -l 0-3 -n 1 -- -i --portmask 0x3 --nb-cores=1 --txq=4 --rxq=4 #. Stop all ports: diff --git a/doc/guides/nics/fail_safe.rst b/doc/guides/nics/fail_safe.rst index ae9f08ec8d..58307360a4 100644 --- a/doc/guides/nics/fail_safe.rst +++ b/doc/guides/nics/fail_safe.rst @@ -116,7 +116,7 @@ This section shows some example of using **testpmd** with a fail-safe PMD. .. code-block:: console - .//app/dpdk-testpmd -c 0xff -n 4 \ + .//app/dpdk-testpmd -l 0-7 -n 4 \ --vdev 'net_failsafe0,mac=de:ad:be:ef:01:02,dev(84:00.0),dev(net_ring0)' \ -b 84:00.0 -b 00:04.0 -- -i @@ -130,7 +130,7 @@ This section shows some example of using **testpmd** with a fail-safe PMD. .. code-block:: console - .//app/dpdk-testpmd -c 0xff -n 4 \ + .//app/dpdk-testpmd -l 0-7 -n 4 \ --vdev 'net_failsafe0,mac=de:ad:be:ef:01:02,dev(84:00.0),dev(net_ring0)' \ -a 81:00.0 -- -i @@ -138,7 +138,7 @@ This section shows some example of using **testpmd** with a fail-safe PMD. .. code-block:: console - .//app/dpdk-testpmd -c 0xff -n 4 -a ff:ff.f \ + .//app/dpdk-testpmd -l 0-7 -n 4 -a ff:ff.f \ --vdev='net_failsafe0,exec(echo 84:00.0)' -- -i #. Start testpmd, automatically probing the device 84:00.0 and using it with @@ -146,7 +146,7 @@ This section shows some example of using **testpmd** with a fail-safe PMD. .. code-block:: console - .//app/dpdk-testpmd -c 0xff -n 4 \ + .//app/dpdk-testpmd -l 0-7 -n 4 \ --vdev 'net_failsafe0,dev(0000:84:00.0),dev(net_ring0)' -- -i diff --git a/doc/guides/nics/ice.rst b/doc/guides/nics/ice.rst index 77985ae5a2..86dec50c27 100644 --- a/doc/guides/nics/ice.rst +++ b/doc/guides/nics/ice.rst @@ -189,7 +189,7 @@ Runtime Configuration .. code-block:: console - dpdk-testpmd -c 0xff -- -i + dpdk-testpmd -l 0-7 -- -i port stop 0 port detach 0 port attach 18:00.0,proto_xtr='[(1,2-3,8-9):tcp,10-13:vlan]',field_offs=92,field_name=pmd_dyn @@ -200,7 +200,7 @@ Runtime Configuration .. code-block:: console - dpdk-testpmd -c 0xff -- -i + dpdk-testpmd -l 0-7 -- -i port stop 0 port detach 0 port attach 18:00.0,proto_xtr=vlan,proto_xtr='[(1,2-3,8-9):tcp,10-23:ipv6]', \ diff --git a/doc/guides/nics/softnic.rst b/doc/guides/nics/softnic.rst index 64939fd484..4e841cb9a3 100644 --- a/doc/guides/nics/softnic.rst +++ b/doc/guides/nics/softnic.rst @@ -121,7 +121,7 @@ Soft NIC testing .. code-block:: console - ./dpdk-testpmd -c 0x7 -s 0x4 --vdev 'net_softnic0,firmware=