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: Tue, 28 Jun 2022 08:19:18 -0700 [thread overview]
Message-ID: <20220628081918.0fc0f31c@hermes.local> (raw)
In-Reply-To: <0906411a-90ad-5651-0153-e34a29027f66@tu-ilmenau.de>
On Tue, 28 Jun 2022 09:25:50 +0200
Carsten Andrich <carsten.andrich@tu-ilmenau.de> wrote:
> On 24.06.22 17:01, Stephen Hemminger wrote:
> > 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).
>
> Thanks for pointing that out. Do you know of any official kernel
> documentation that could shed some light on that? I haven't had any
> serious issues like the ones you list, but maybe I've been lucky. My
> DPDK applications typically run on fairly minimal systems used
> exclusively for DPDK tasks, which require minimal latency/jitter. Minor
> side-effects from using SCHED_FIFO are tolerable in my case, if it
> improves performance.
Do some looking around and you will find good documentation like:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_for_real_time/7/html/tuning_guide/real_time_throttling
This characteristic of real-time threads means that it is quite easy to
write an application which monopolizes 100% of a given CPU. At first
glance this sounds like it might be a good idea, but in reality it
causes lots of headaches for the operating system. The OS is
responsible for managing both system-wide and per-CPU resources and
must periodically examine data structures describing these resources
and perform housekeeping activities with them. If a core is monopolized
by a SCHED_FIFO thread, it cannot perform the housekeeping tasks and
eventually the entire system becomes unstable, potentially causing a
crash.
prev parent reply other threads:[~2022-06-28 15:19 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
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 [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=20220628081918.0fc0f31c@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).