From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 446] rte_lcore_index(-1) returns invalid data for non DPDK thread.
Date: Wed, 08 Apr 2020 20:16:06 +0000 [thread overview]
Message-ID: <bug-446-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=446
Bug ID: 446
Summary: rte_lcore_index(-1) returns invalid data for non DPDK
thread.
Product: DPDK
Version: 20.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
Calling rte_lcore_index() with -1 as lcore returns the relative index of the
current lcore in the cpuset. But if called from a non-DPDK thread the value is
undefined. It ends up referencing outside lcore_config array and gets some
other value. In our tests it got 253; but could be anything.
It is documented to return -1 on error. It does that if passed an lcore value
outside the cpu set, it should return -1 if run in non-DPDK thread as well.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-04-08 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 20:16 bugzilla [this message]
2020-07-09 7:01 ` [dpdk-dev] [Bug 446] rte_lcore_index(-1) returns invalid data for non DPDK thread bugzilla
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-446-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.