* [dpdk-dev] [Bug 322] eal: ctrl thread calculation assumes 1:1 mapping between cpu and lcore id
@ 2019-07-16 8:48 bugzilla
0 siblings, 0 replies; only message in thread
From: bugzilla @ 2019-07-16 8:48 UTC (permalink / raw)
To: dev
https://bugs.dpdk.org/show_bug.cgi?id=322
Bug ID: 322
Summary: eal: ctrl thread calculation assumes 1:1 mapping
between cpu and lcore id
Product: DPDK
Version: 18.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: johan.kallstrom@ericsson.com
Target Milestone: ---
ctrl thread calculation assumes 1:1 mapping between cpu and lcore id.
This is not the case when --lcores and the optional cpuset mask is used.
The calculation introduced in c3568ea376700 (and 18.11.2 23a9f69ed3d9) assumes
a 1:1 mapping between cpu and lcore id. This is not the case when --lcores and
the optional cpuset mask is used.
The calculation fails when --lcores and cpuset mask is set so cpu and lcore no
longer maps 1:1.
The code silently started on the wrong physical thread with following eal
arguments(if not cpusets are used to limit the thread affinity):
--master-lcore 0 --lcores (0,19)@(19,1,2,3)
If cpusets are used(and the calculated thread is outside the cpuset) eal fails
to start with the following output:
EAL: Failed to create thread for interrupt handling
EAL: FATAL: Cannot init interrupt-handling thread
EAL: Cannot init interrupt-handling thread
EAL: Error - exiting with code: 1
Cause: Invalid EAL arguments: -1 - Unknown error -1
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-07-16 8:48 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-16 8:48 [dpdk-dev] [Bug 322] eal: ctrl thread calculation assumes 1:1 mapping between cpu and lcore id bugzilla
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).