d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

examples/eventdev: check CPU core enabling

Browse Source 
In the case that the cores are isolated, if "-l" or "-c" parameter is not
added, the cores will not be enabled and can not launch worker function
correctly. In the meanwhile, no error information is reported.

For example:
totally CPUs:16
isolated CPUs:1-8
command: sudo gdb -args ./dpdk-eventdev_pipeline --vdev event_sw0 \
        -- -r1 -t1 -e4 -w F00 -s4 -n0 -c32 -W1000 -D

cores information:
rte_config->lcore_role = {ROLE_RTE, ROLE_OFF, ROLE_OFF, ROLE_OFF,
                          ROLE_OFF, ROLE_OFF, ROLE_OFF, ROLE_OFF,
                          ROLE_OFF, ROLE_RTE, ROLE_RTE, ROLE_RTE,
                          ROLE_RTE, ROLE_RTE, ROLE_RTE, ROLE_RTE}

output information:
...
[main()] lcore 9 executing worker, using eventdev port 0
[main()] lcore 10 executing worker, using eventdev port 1
[main()] lcore 11 executing worker, using eventdev port 2

This is because "RTE_LCORE_FOREACH_WORKER" chooses the enabled core. In
the case that the cores are isolated, "the lcore_role" flag of isolated
cores are set as "ROLE_OFF" by default(not enabled). So if we choose
these isolated cores as workers, "RTE_LCORE_FOREACH_WORKER" will ignore
these cores and not launch worker functions on them.

To fix this, add "-l" parameters to doc and add lcore enabled check.

Fixes: 1094ca96689c ("doc: add SW eventdev pipeline to sample app guide")
Cc: stable@dpdk.org

Signed-off-by: Feifei Wang <feifei.wang2@arm.com>
Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
This commit is contained in:
Feifei Wang 2021-01-14 18:30:59 +08:00 committed by Jerin Jacob
parent 21b1ca4843
commit 3d15913432
2 changed files with 11 additions and 3 deletions
doc/guides/sample_app_ug
eventdev_pipeline.rst
examples/eventdev_pipeline
main.c

5
doc/guides/sample_app_ug/eventdev_pipeline.rst

@ -34,6 +34,7 @@ options.
An example eventdev pipeline running with the software eventdev PMD using An example eventdev pipeline running with the software eventdev PMD using
these settings is shown below: these settings is shown below:
* ``-l 0,2,8-15``: lcore to use
* ``-r1``: core mask 0x1 for RX * ``-r1``: core mask 0x1 for RX
* ``-t1``: core mask 0x1 for TX * ``-t1``: core mask 0x1 for TX
* ``-e4``: core mask 0x4 for the software scheduler * ``-e4``: core mask 0x4 for the software scheduler
@ -46,8 +47,8 @@ these settings is shown below:
.. code-block:: console .. code-block:: console
./<build_dir>/examples/dpdk-eventdev_pipeline --vdev event_sw0 -- -r1 -t1 \ ./<build_dir>/examples/dpdk-eventdev_pipeline -l 0,2,8-15 --vdev event_sw0 \
-e4 -w FF00 -s4 -n0 -c32 -W1000 -D -- -r1 -t1 -e4 -w FF00 -s4 -n0 -c32 -W1000 -D
The application has some sanity checking built-in, so if there is a function The application has some sanity checking built-in, so if there is a function
(e.g.; the RX core) which doesn't have a cpu core mask assigned, the application (e.g.; the RX core) which doesn't have a cpu core mask assigned, the application

9
examples/eventdev_pipeline/main.c

@ -239,8 +239,15 @@ parse_app_args(int argc, char **argv)
if (fdata->worker_core[i]) if (fdata->worker_core[i])
cdata.num_workers++; cdata.num_workers++;
if (core_in_use(i)) if (core_in_use(i)) {
if (!rte_lcore_is_enabled(i)) {
printf("lcore %d is not enabled in lcore list\n",
i);
rte_exit(EXIT_FAILURE,
"check lcore params failed\n");
}
cdata.active_cores++; cdata.active_cores++;
}
} }
} }