A few places in documentation refer to master lcore
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
doc/guides/howto/debug_troubleshoot.rst | 2 +-
doc/guides/linux_gsg/eal_args.include.rst | 4 ++--
doc/guides/nics/bnxt.rst | 2 +-
doc/guides/sample_app_ug/hello_world.rst | 2 +-
doc/guides/sample_app_ug/timer.rst | 2 +-
5 files changed, 6 insertions(+), 6 deletions(-)
@@ -311,7 +311,7 @@ Custom worker function :numref:`dtg_distributor_worker`.
SERVICE. Check performance functions are mapped to run on the cores.
* For high-performance execution logic ensure running it on correct NUMA
- and non-master core.
+ and worker core.
* Analyze run logic with ``rte_dump_stack``, ``rte_dump_registers`` and
``rte_memdump`` for more insights.
@@ -33,9 +33,9 @@ Lcore-related options
At a given instance only one core option ``--lcores``, ``-l`` or ``-c`` can
be used.
-* ``--master-lcore <core ID>``
+* ``--initial-lcore <core ID>``
- Core ID that is used as master.
+ Core ID that is used as initial lcore.
* ``-s <service core mask>``
@@ -403,7 +403,7 @@ The application enables multiple TX and RX queues when it is started.
.. code-block:: console
- testpmd -l 1,3,5 --master-lcore 1 --txq=2 –rxq=2 --nb-cores=2
+ testpmd -l 1,3,5 --initial-lcore 1 --txq=2 –rxq=2 --nb-cores=2
**TSS**
@@ -77,7 +77,7 @@ The code that launches the function on each lcore is as follows:
/* call lcore_hello() on every worker lcore */
- RTE_LCORE_FOREACH_SLAVE(lcore_id) {
+ RTE_LCORE_FOREACH_WORKER(lcore_id) {
rte_eal_remote_launch(lcore_hello, NULL, lcore_id);
}
@@ -55,7 +55,7 @@ the main loop is executed on each worker lcore using the well-known rte_eal_remo
/* call lcore_mainloop() on every worker lcore */
- RTE_LCORE_FOREACH_SLAVE(lcore_id) {
+ RTE_LCORE_FOREACH_WORKER(lcore_id) {
rte_eal_remote_launch(lcore_mainloop, NULL, lcore_id);
}