* [DPDK/core Bug 1935] rte_lcore_to_cpu_id returns incorrect cpu-id when `lcore-map or re-map lcore` option used
@ 2026-04-11 13:14 bugzilla
0 siblings, 0 replies; only message in thread
From: bugzilla @ 2026-04-11 13:14 UTC (permalink / raw)
To: dev
http://bugs.dpdk.org/show_bug.cgi?id=1935
Bug ID: 1935
Summary: rte_lcore_to_cpu_id returns incorrect cpu-id when
`lcore-map or re-map lcore` option used
Product: DPDK
Version: 26.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: vipin.varghese@amd.com
Target Milestone: ---
DPDK: 26.03
test application: modified examples/helloworld
cmd:
working: `./build/helloworld -l0,1,67,14,33`
faulty-1: `./build/helloworld -l0,1,67,14,33 -R`
faulty-2: `./build/helloworld -l0@8,1@18,2@67,3@14,4@33`
expected behaviour: if there are eal args for remap or map lcore, the API (as
per current understanding) should return the actual core on which it runs. API
`rte_lcore_cpuset` returns a valid value in all cases.
attaching screenshot for reference
--
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:[~2026-04-11 13:14 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-04-11 13:14 [DPDK/core Bug 1935] rte_lcore_to_cpu_id returns incorrect cpu-id when `lcore-map or re-map lcore` option used bugzilla
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox