* [dpdk-dev] [Bug 824] RTE_LCORE_FOREACH goes over unactive cores with dynamic linking on BlueField 2
@ 2021-10-05 16:08 bugzilla
2021-10-13 6:57 ` bugzilla
0 siblings, 1 reply; 2+ messages in thread
From: bugzilla @ 2021-10-05 16:08 UTC (permalink / raw)
To: dev
https://bugs.dpdk.org/show_bug.cgi?id=824
Bug ID: 824
Summary: RTE_LCORE_FOREACH goes over unactive cores with
dynamic linking on BlueField 2
Product: DPDK
Version: 21.08
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: barbette@kth.se
Target Milestone: ---
This may not only happen on BlueField 2 only, but this is where I catched the
bug...
test.c
> #include <rte_lcore.h>
> #include <rte_eal.h>
> int
> main(int argc, char **argv)
> {
> int ret;
> int lcore_id;
> /* init EAL */
> ret = rte_eal_init(argc, argv);
> if (ret < 0)
> rte_exit(EXIT_FAILURE, "Invalid EAL parameters\n");
> printf("Have %d cores\n", rte_lcore_count());
> RTE_LCORE_FOREACH(lcore_id) {
> printf("Core %d\n",lcore_id);
> }
> }
Then compile using dynamic linking:
> gcc -o mytest test.c $(pkg-config --libs libdpdk) $(pkg-config --cflags
> libdpdk)
Run:
> ./mytest
> Have 8 cores
> Core 0
> Core 1
> ...
> Core 63
With --static --libs it works fine
Maybe a check should be done to verify the core is active in RTE_LCORE_FOREACH
but I did not see any doc and there is no such things in the example.
--
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:[~2021-10-13 6:57 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-05 16:08 [dpdk-dev] [Bug 824] RTE_LCORE_FOREACH goes over unactive cores with dynamic linking on BlueField 2 bugzilla
2021-10-13 6:57 ` 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).