From: Stephen Hemminger <stephen@networkplumber.org>
To: Carsten Andrich <carsten.andrich@tu-ilmenau.de>
Cc: users@dpdk.org
Subject: Re: Large interruptions for EAL thread running on isol core
Date: Fri, 24 Jun 2022 08:01:24 -0700 [thread overview]
Message-ID: <20220624080124.244a01a9@hermes.local> (raw)
In-Reply-To: <9a95a560-c7c6-d4fa-1041-836fa400f497@tu-ilmenau.de>
On Thu, 23 Jun 2022 21:03:49 +0200
Carsten Andrich <carsten.andrich@tu-ilmenau.de> wrote:
> 2. Use real-time priority (SCHED_FIFO w/ priority 99) for the DPDK
> threads and
> echo -1 > /proc/sys/kernel/sched_rt_runtime_us
> to disable the runtime limit. With the runtime limit in place, the
> SCHED_FIFO performance will be significantly worse than SCHED_OTHER.
This can cause major issues if application is normal DPDK application (never does system calls).
If an interrupt or other event happens on your isolated CPU, the work that it would
do in soft irq is never performed. FIFO has higher priority than kernel threads.
This can lead to mystery lockups from other applications (reads not completing, network timeouts, etc).
In any semi-recent kernel using SCHED_NO_HZ_FULL will keep clock ticks from happening
on the isolated cores.
next prev parent reply other threads:[~2022-06-24 15:01 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
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 [this message]
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=20220624080124.244a01a9@hermes.local \
--to=stephen@networkplumber.org \
--cc=carsten.andrich@tu-ilmenau.de \
--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).