From: John Alexander <John.Alexander@datapath.co.uk>
To: Tal Shnaiderman <firstname.lastname@example.org>,
Dmitry Kozlyuk <email@example.com>,
"Dmitry Malloy (MESHCHANINOV)" <firstname.lastname@example.org>,
Narcisa Ana Maria Vasile <Narcisa.Vasile@microsoft.com>
Cc: Eilon Greenstein <email@example.com>,
Omar Cardona <firstname.lastname@example.org>,
Rani Sharoni <email@example.com>, Odi Assli <firstname.lastname@example.org>,
Harini Ramakrishnan <Harini.Ramakrishnan@microsoft.com>,
NBU-Contact-Thomas Monjalon <email@example.com>,
Subject: Re: [dpdk-dev] Windows DPDK real-time priority threads causing thread starvation
Date: Wed, 9 Dec 2020 16:08:07 +0000 [thread overview]
Message-ID: <DB6PR0902MB2072CF8D4AFA71CAB28218E6B4CC0@DB6PR0902MB2072.eurprd09.prod.outlook.com> (raw)
I tend to run with a winbdg kernel debugger (KDNET) connected to my debug target machines. It quite often reports deadlock detection when we have such "real-time" threads never yielding on a core. If we hog core-0 in particular dwm.exe never gets a look in so the desktop stops being drawn too.
> -----Original Message-----
> From: dev <firstname.lastname@example.org> On Behalf Of Tal Shnaiderman
> Sent: 09 December 2020 14:16
> To: Dmitry Kozlyuk <email@example.com>; Dmitry Malloy
> (MESHCHANINOV) <firstname.lastname@example.org>; Narcisa Ana Maria Vasile
> Cc: Eilon Greenstein <email@example.com>; Omar Cardona
> <firstname.lastname@example.org>; Rani Sharoni <email@example.com>; Odi Assli
> <firstname.lastname@example.org>; Harini Ramakrishnan
> <Harini.Ramakrishnan@microsoft.com>; NBU-Contact-Thomas Monjalon
> <email@example.com>; firstname.lastname@example.org
> Subject: [dpdk-dev] Windows DPDK real-time priority threads causing thread
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
> During our verification tests on Windows DPDK we've noticed that DPDK
> polling threads, which run in REALTIME_PRIORITY_CLASS are causing
> starvation to other threads from the OS which need to change affinity and
> run in lower priority.
> While running an application for a while we see the OS thread waits for 2:30
> minutes and raises a bugcheck, see below example of such flow:
> 1) DPDK thread running on core-0 in real-time high priority(24) polling mode.
> 2) The thread is blocking the system function NtSetSystemInformation
> (ExpUpdateTimerConfiguration) in another thread from
> switching to core-0 via KeSetSystemGroupAffinityThread since the calling
> thread is priority 15.
> 3) NtSetSystemInformation exclusively acquired system-wide lock
> (ExpTimeRefreshLock) hence
> it blocks other threads (e.g. calling NtQuerySystemInformation).
> We've seen this behavior only while running on Windows 2019 VMs, maybe
> on native machines OS scheduling of such flow is done differently?
> Below is usage explanation from the documentation of SetPriorityClass :
> - REALTIME_PRIORITY_CLASS
> Process that has the highest possible priority. The threads of the process
> preempt the threads of all other processes, including operating system
> processes performing important tasks. For example, a real-time process that
> executes for more than a very brief interval can cause disk caches not to
> flush or cause the mouse to be unresponsive.
> So I assume using this kind of thread for a long period as we do can cause
> unstable behavior.
> How do you think we can resolve this? Are there such cases in Linux?
>  - https://docs.microsoft.com/en-
next prev parent reply other threads:[~2020-12-09 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 14:15 Tal Shnaiderman
2020-12-09 16:08 ` John Alexander [this message]
2020-12-09 16:08 ` Stephen Hemminger
2020-12-09 16:12 ` [dpdk-dev] [EXTERNAL] " Dmitry Malloy (MESHCHANINOV)
2020-12-16 14:53 ` Tal Shnaiderman
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).