* [dpdk-dev] [Bug 446] rte_lcore_index(-1) returns invalid data for non DPDK thread.
@ 2020-04-08 20:16 bugzilla
2020-07-09 7:01 ` bugzilla
0 siblings, 1 reply; 2+ messages in thread
From: bugzilla @ 2020-04-08 20:16 UTC (permalink / raw)
To: dev
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-07-09 7:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-08 20:16 [dpdk-dev] [Bug 446] rte_lcore_index(-1) returns invalid data for non DPDK thread bugzilla
2020-07-09 7:01 ` 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).