From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 824] RTE_LCORE_FOREACH goes over unactive cores with dynamic linking on BlueField 2
Date: Tue, 05 Oct 2021 16:08:57 +0000 [thread overview]
Message-ID: <bug-824-3@http.bugs.dpdk.org/> (raw)
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.
next reply other threads:[~2021-10-05 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 16:08 bugzilla [this message]
2021-10-13 6:57 ` [dpdk-dev] [Bug 824] RTE_LCORE_FOREACH goes over unactive cores with dynamic linking on BlueField 2 bugzilla
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-824-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.