patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Tal Shnaiderman <talshn@nvidia.com>
Cc: dpdk stable <stable@dpdk.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	pallavi.kadam@intel.com,  dmitry.kozliuk@gmail.com,
	navasile@linux.microsoft.com, dmitrym@microsoft.com,
	 Xueming Li <xuemingl@nvidia.com>
Subject: Re: [dpdk-stable] [PATCH 19.11.9] eal/windows: fix default thread priority
Date: Mon, 31 May 2021 10:41:25 +0200	[thread overview]
Message-ID: <CAATJJ0Lzudz=NMxARYu=tyc018iahmCyUqQp5qA85cGTBa1xfQ@mail.gmail.com> (raw)
In-Reply-To: <20210523081242.19860-1-talshn@nvidia.com>

On Sun, May 23, 2021 at 10:13 AM Tal Shnaiderman <talshn@nvidia.com> wrote:
>
> [ upstream commit 16afcbfa30e9c2831264fb349457a4228fa687c8 ]

Thank you for the backport, queued for 19.11.9 now

> The hard-coded thread priority for Windows threads in EAL
> is REALTIME_PRIORITY_CLASS/THREAD_PRIORITY_TIME_CRITICAL.
>
> This results in issues with DPDK threads causing OS thread starvation
> and eventually a bugcheck.
>
> The fix reduce the thread priority to
> NORMAL_PRIORITY_CLASS/THREAD_PRIORITY_NORMAL.
>
> Bugzilla ID: 600
>
> Reported-by: Odi Assli <odia@nvidia.com>
> Signed-off-by: Tal Shnaiderman <talshn@nvidia.com>
> Acked-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
> ---
>  lib/librte_eal/windows/eal/eal_thread.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lib/librte_eal/windows/eal/eal_thread.c b/lib/librte_eal/windows/eal/eal_thread.c
> index 0591d4c7fb..af1e7fe2ea 100644
> --- a/lib/librte_eal/windows/eal/eal_thread.c
> +++ b/lib/librte_eal/windows/eal/eal_thread.c
> @@ -147,8 +147,8 @@ eal_thread_create(pthread_t *thread)
>         if (!th)
>                 return -1;
>
> -       SetPriorityClass(GetCurrentProcess(), REALTIME_PRIORITY_CLASS);
> -       SetThreadPriority(th, THREAD_PRIORITY_TIME_CRITICAL);
> +       SetPriorityClass(GetCurrentProcess(), NORMAL_PRIORITY_CLASS);
> +       SetThreadPriority(th, THREAD_PRIORITY_NORMAL);
>
>         return 0;
>  }
> --
> 2.16.1.windows.4
>


-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

      reply	other threads:[~2021-05-31  8:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-23  8:12 Tal Shnaiderman
2021-05-31  8:41 ` Christian Ehrhardt [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='CAATJJ0Lzudz=NMxARYu=tyc018iahmCyUqQp5qA85cGTBa1xfQ@mail.gmail.com' \
    --to=christian.ehrhardt@canonical.com \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=dmitrym@microsoft.com \
    --cc=navasile@linux.microsoft.com \
    --cc=pallavi.kadam@intel.com \
    --cc=stable@dpdk.org \
    --cc=talshn@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=xuemingl@nvidia.com \
    /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).