From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 322] eal: ctrl thread calculation assumes 1:1 mapping between cpu and lcore id
Date: Tue, 16 Jul 2019 08:48:48 +0000 [thread overview]
Message-ID: <bug-322-3@http.bugs.dpdk.org/> (raw)
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.
reply other threads:[~2019-07-16 8:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-322-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).