From: Stephen Hemminger <stephen@networkplumber.org>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users@dpdk.org
Subject: Re: Multiple rte_launch_remote multiple times on main lcore
Date: Sun, 25 Jun 2023 07:49:26 -0700 [thread overview]
Message-ID: <20230625074926.38ea8586@hermes.local> (raw)
In-Reply-To: <CAO8pfF=wKdUvaKfiNvmFObsHNO9vxPj-D8qF0GP=N4eJ7nWTwg@mail.gmail.com>
On Tue, 20 Jun 2023 17:33:59 +0200
Antonio Di Bacco <a.dibacco.ks@gmail.com> wrote:
> Is it possible to launch multiple threads on the main lcore?
> Who will be in charge of scheduling those threads on the main lcore
> (main lcore is isolated)?
>
> Not the OS I suppose.
>
> Thank you
If you start trying to add threads like this, it will lead to
all sorts of locking problems. When one thread gets the lock
and then gets preempted by the scheduler and another thread
(bound to same lcore) tries to acquire the lock, it will spin
and wait until the first thread is rescheduled.
DPDK was designed for dedicated threads per lcore.
next prev parent reply other threads:[~2023-06-25 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 15:33 Antonio Di Bacco
2023-06-25 14:49 ` Stephen Hemminger [this message]
2023-06-27 18:20 ` Antonio Di Bacco
2023-06-27 22:40 ` Stephen Hemminger
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=20230625074926.38ea8586@hermes.local \
--to=stephen@networkplumber.org \
--cc=a.dibacco.ks@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).