From: Stephen Hemminger <stephen@networkplumber.org>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users@dpdk.org
Subject: Re: Large interruptions for EAL thread running on isol core
Date: Thu, 23 Jun 2022 11:41:59 -0700 [thread overview]
Message-ID: <20220623114159.0fb198b3@hermes.local> (raw)
In-Reply-To: <CAO8pfF=yo37Ng5QAcopL=6LgKMHr4+=pPcONPATyS+OD0GLgfg@mail.gmail.com>
On Thu, 23 Jun 2022 20:03:02 +0200
Antonio Di Bacco <a.dibacco.ks@gmail.com> wrote:
> I'm running a DPDK thread on an isolated core. I also set some flags
> that could help keeping the core at rest on linux like: nosoftlockup
> nohz_full rcu_nocbs irqaffinity.
>
> Unfortunately the thread gets some interruptions that stop the thread
> for about 20-30 micro seconds. This seems smal but my application
> suffers a lot.
>
> I also tried to use rte_thread_set_priority that indeed has a strong
> effect but unfortunately creates problems to Linux (like network not
> working).
>
> Is there any other knob that could help running the DPDK thread with
> minimum or no interruptions at all?
Look with perf and see what is happening.
First check for interrupt affinity.
Don't try real time priority.
The other thing to look for would be any BIOS settings.
Some system management units can take away CPU silently for polling
some internal housekeeping.
next prev parent reply other threads:[~2022-06-23 18:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 18:03 Antonio Di Bacco
2022-06-23 18:07 ` Omer Yamac
2022-06-24 9:43 ` Antonio Di Bacco
2022-06-23 18:41 ` Stephen Hemminger [this message]
2022-06-24 9:45 ` Antonio Di Bacco
2022-06-24 10:43 ` Kinsella, Ray
2022-06-23 19:03 ` Carsten Andrich
2022-06-24 15:01 ` Stephen Hemminger
2022-06-24 15:41 ` Carsten Andrich
2022-06-24 16:42 ` Stephen Hemminger
2022-06-28 7:25 ` Carsten Andrich
2022-06-28 15:19 ` 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=20220623114159.0fb198b3@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).