From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1935] rte_lcore_to_cpu_id returns incorrect cpu-id when `lcore-map or re-map lcore` option used
Date: Sat, 11 Apr 2026 13:14:30 +0000 [thread overview]
Message-ID: <bug-1935-3@http.bugs.dpdk.org/> (raw)
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.
reply other threads:[~2026-04-11 13:14 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-1935-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