From: Stephen Hemminger <stephen@networkplumber.org>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users@dpdk.org
Subject: Re: Can I use main lcore as a worker core?
Date: Tue, 18 Mar 2025 14:55:52 -0700 [thread overview]
Message-ID: <20250318145552.5db8cc38@hermes.local> (raw)
In-Reply-To: <CAO8pfFmJgnWHLayoptAZZ9-UW=iB5SMeGqq_XGHxFoPnUxF6qQ@mail.gmail.com>
On Tue, 18 Mar 2025 15:38:31 +0100
Antonio Di Bacco <a.dibacco.ks@gmail.com> wrote:
> When I instantiate a process with 4 cores, I have 3 worker cores and
> one main lcore.
>
> I'm wasting an isolated core (the main lcore) to do nothing.
>
> I want to overcome this and use also the main lcore.
>
> Best regards,
> Anna.
It is often useful to main lcore on non-isolated CPU and have it available
for application control tasks. I.e Don't use it for polling instead block
on epoll etc.
prev parent reply other threads:[~2025-03-18 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 14:38 Antonio Di Bacco
2025-03-18 16:35 ` Rajesh Kumar
2025-03-18 21:55 ` 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=20250318145552.5db8cc38@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).