From: Stephen Hemminger <stephen@networkplumber.org>
To: fwefew 4t4tg <7532yahoo@gmail.com>
Cc: users@dpdk.org
Subject: Re: --lcores: what it does and does not do
Date: Sat, 30 Mar 2024 15:40:29 -0700 [thread overview]
Message-ID: <20240330154029.19f5dee7@hermes.local> (raw)
In-Reply-To: <CA+Tq66X5PL6B1QgV9CGrkMjJ=eUdp+C25_brr=ifcyLGfznQdA@mail.gmail.com>
On Sat, 30 Mar 2024 17:45:41 -0400
fwefew 4t4tg <7532yahoo@gmail.com> wrote:
> // If program run with --lcores=(1)@2,(2)@4 this loop will
> // create and run two threads lcore 1 pinned to CPU 2 and lcore 2
> // pinned to CPU 4. the output will look like:
> // hello from core 1
> // hello from core 2
> RTE_LCORE_FOREACH_WORKER(lcore_id) {
> rte_eal_remote_launch(lcore_hello, NULL, lcore_id);
> }
> .
You don't need that loop, that is what rte_eal_mp_remote_launch does
with more error checking.
prev parent reply other threads:[~2024-03-30 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 16:06 fwefew 4t4tg
2024-03-30 16:52 ` Stephen Hemminger
2024-03-30 21:45 ` fwefew 4t4tg
2024-03-30 22:40 ` Stephen Hemminger [this message]
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=20240330154029.19f5dee7@hermes.local \
--to=stephen@networkplumber.org \
--cc=7532yahoo@gmail.com \
--cc=users@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;
as well as URLs for NNTP newsgroup(s).