diff options
author | Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org> | 2015-11-19 16:30:03 +0200 |
---|---|---|
committer | Maxim Uvarov <maxim.uvarov@linaro.org> | 2015-11-30 12:20:28 +0300 |
commit | 7294ab04a6b8dd06889e27165a5fdfc1edf436c3 (patch) | |
tree | 3920d13e3a877870afde89b0e125146aa4195c8e /example/timer/odp_timer_test.c | |
parent | 725e4eddedec794566579ff1843d4784054ab64b (diff) |
linux-generic: cpumask: warn that CPU0 is used by control and worker thread
By default, all control threads execute on CPU 0 and
odp_cpumask_default_control() returns this CPU. For reasons of
performance, control and worker CPU's shouldn't overlap but for some
scenarios it can be desirable to utilize all CPU's for worker threads.
Thus we leave the decision of CPU allocation to the user but report
when a CPU is used for both control and worker threads.
Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>
Reviewed-by: Ola Liljedahl <ola.liljedahl@linaro.org>
Signed-off-by: Maxim Uvarov <maxim.uvarov@linaro.org>
Diffstat (limited to 'example/timer/odp_timer_test.c')
0 files changed, 0 insertions, 0 deletions