From: Stephen Hemminger <stephen@networkplumber.org>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users@dpdk.org
Subject: Re: eal-intr-thread, rte_mp_handle threads of secondary running on ISOLATED cores
Date: Sat, 22 Apr 2023 09:08:47 -0700 [thread overview]
Message-ID: <20230422090847.09880fc6@hermes.local> (raw)
In-Reply-To: <CAO8pfFkrhTHvn8fe13Vv99jj=nSF=suN20ei0w034bajVbEAFQ@mail.gmail.com>
On Fri, 21 Apr 2023 23:34:48 +0200
Antonio Di Bacco <a.dibacco.ks@gmail.com> wrote:
> I have a primary process whose
> eal-intr-thread
> rte_mp_handle
> threads are running correctly on "non-isolated" cores.
>
> The primary forks a secondary whose
> eal-intr-thread
> rte_mp_handle
> threads are running on "isolated" cores.
>
> I'm using DPDK 21.11, I believe this is a bug. What is your opinion?
>
> BR,
> Anna.
This email is missing lots of info.
1. What is the bug you are seeing, what is the log?
2. Why are you trying to start DPDK in non-standard way?
Don't try and be creative and do things in new and different ways
unless you are trying to find new and different bugs!
prev parent reply other threads:[~2023-04-22 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 21:34 Antonio Di Bacco
2023-04-22 16:08 ` 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=20230422090847.09880fc6@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).