All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Tal Shnaiderman <talshn@nvidia.com>
Cc: dev@dpdk.org, thomas@monjalon.net, pallavi.kadam@intel.com,
	navasile@linux.microsoft.com, dmitrym@microsoft.com,
	david.marchand@redhat.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal/windows: fix default thread priority
Date: Wed, 10 Mar 2021 00:44:09 +0300	[thread overview]
Message-ID: <20210310004409.2fb28b27@sovereign> (raw)
In-Reply-To: <20210218114058.13248-1-talshn@nvidia.com>

2021-02-18 13:40 (UTC+0200), Tal Shnaiderman:
> 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
> Fixes: 53ffd9f080f ("eal/windows: add minimum viable code")
> Cc: stable@dpdk.org
> 
> Reported-by: Odi Assli <odia@nvidia.com>
> Signed-off-by: Tal Shnaiderman <talshn@nvidia.com>
> ---
>  lib/librte_eal/windows/eal_thread.c      | 4 ++--
>  lib/librte_eal/windows/include/pthread.h | 4 ++--
>  2 files changed, 4 insertions(+), 4 deletions(-)

Acked-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>

  parent reply	other threads:[~2021-03-09 21:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18 11:40 [dpdk-dev] [PATCH] eal/windows: fix default thread priority Tal Shnaiderman
2021-03-09  8:30 ` Tal Shnaiderman
2021-03-09 21:44 ` Dmitry Kozlyuk [this message]
2021-03-16 11:41   ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon

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=20210310004409.2fb28b27@sovereign \
    --to=dmitry.kozliuk@gmail.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.