From: Tal Shnaiderman <talshn@nvidia.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
"pallavi.kadam@intel.com" <pallavi.kadam@intel.com>,
"dmitry.kozliuk@gmail.com" <dmitry.kozliuk@gmail.com>,
"navasile@linux.microsoft.com" <navasile@linux.microsoft.com>,
"dmitrym@microsoft.com" <dmitrym@microsoft.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eal/windows: fix default thread priority
Date: Tue, 9 Mar 2021 08:30:34 +0000 [thread overview]
Message-ID: <DM6PR12MB3945E29EF5FF82BF0974E91DA4929@DM6PR12MB3945.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210218114058.13248-1-talshn@nvidia.com>
> Subject: [dpdk-dev] [PATCH] eal/windows: fix default thread priority
>
> 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(-)
>
> diff --git a/lib/librte_eal/windows/eal_thread.c
> b/lib/librte_eal/windows/eal_thread.c
> index 908e726d16..9c3f6d69fd 100644
> --- a/lib/librte_eal/windows/eal_thread.c
> +++ b/lib/librte_eal/windows/eal_thread.c
> @@ -134,8 +134,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;
> }
> diff --git a/lib/librte_eal/windows/include/pthread.h
> b/lib/librte_eal/windows/include/pthread.h
> index fb11a07ce6..9aeab1fa70 100644
> --- a/lib/librte_eal/windows/include/pthread.h
> +++ b/lib/librte_eal/windows/include/pthread.h
> @@ -137,8 +137,8 @@ pthread_create(void *threadid, const void
> *threadattr, void *threadfunc,
> hThread = CreateThread(NULL, 0,
> (LPTHREAD_START_ROUTINE)threadfunc,
> args, 0, (LPDWORD)threadid);
> if (hThread) {
> - SetPriorityClass(GetCurrentProcess(),
> REALTIME_PRIORITY_CLASS);
> - SetThreadPriority(hThread,
> THREAD_PRIORITY_TIME_CRITICAL);
> + SetPriorityClass(GetCurrentProcess(),
> NORMAL_PRIORITY_CLASS);
> + SetThreadPriority(hThread, THREAD_PRIORITY_NORMAL);
> }
> return ((hThread != NULL) ? 0 : E_FAIL); }
> --
> 2.16.1.windows.4
Hi,
Any comments on the patch or can it be Acked as was discussed in the community call?
next prev parent reply other threads:[~2021-03-09 8:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 11:40 Tal Shnaiderman
2021-03-09 8:30 ` Tal Shnaiderman [this message]
2021-03-09 21:44 ` Dmitry Kozlyuk
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=DM6PR12MB3945E29EF5FF82BF0974E91DA4929@DM6PR12MB3945.namprd12.prod.outlook.com \
--to=talshn@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=stable@dpdk.org \
--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 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).