[dpdk-dev] [Bug 446] rte_lcore_index(-1) returns invalid data for non DPDK thread.

[dpdk-dev] [Bug 446] rte_lcore_index(-1) returns invalid data for non DPDK thread.

[bugzilla]

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.

[dpdk-dev] [Bug 446] rte_lcore_index(-1) returns invalid data for non DPDK thread.

[bugzilla]

https://bugs.dpdk.org/show_bug.cgi?id=446

Thomas Monjalon (thomas@monjalon.net) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #1 from Thomas Monjalon (thomas@monjalon.net) ---
Resolved in http://git.dpdk.org/dpdk/commit/?id=67ae5936c4

-- 
You are receiving this mail because:
You are the assignee for the bug.