patches for DPDK stable branches
 help / color / mirror / Atom feed
From: David Marchand <>
To: Dmitry Kozlyuk <>,
	 "Dmitry Malloy (MESHCHANINOV)" <>,
	 Narcisa Ana Maria Vasile <>,
	Pallavi Kadam <>
Cc: dev <>, dpdk stable <>,
	Qiming Yang <>,
	 Qi Zhang <>,
	Haiyue Wang <>,
	 Thomas Monjalon <>
Subject: Re: [dpdk-stable] [PATCH 2/2] net/ice: fix leak on thread termination
Date: Fri, 7 May 2021 10:13:16 +0200
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, May 6, 2021 at 11:45 AM David Marchand
<> wrote:
> A terminated pthread should be joined or detached so that its associated
> resources are released.
> The "ice-reset-<vf_id>" threads are used to service some reset task in the
> background, but they are never joined by the thread that created them.
> The easiest solution is to detach new threads.

Not so "easy" for Windows.

I think I'll simply #ifndef WINDOWS my addition.
Maybe the leak does not exist on Windows? but if it does, the
situation won't change by doing nothing on Windows.

If there is strong objection, I'll need some help to add a
pthread_detach() wrapper in windows EAL.
From my quick read at the API, I'd say I need to find the current
thread handle (via OpenThread) then CloseHandle it.
But does it work from "pthread_self()" ?

Since a new API thread is in preparation, the "thread detaching" from
the pthread API is something to consider.
I could not find it in Narcissa series.

David Marchand

  parent reply	other threads:[~2021-05-07  8:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2021-05-06  9:44 ` [dpdk-stable] [PATCH 1/2] net/ark: " David Marchand
2021-05-11 17:55   ` Ed Czeck
2021-05-06  9:44 ` [dpdk-stable] [PATCH 2/2] net/ice: " David Marchand
2021-05-06 10:31   ` Wang, Haiyue
2021-05-07  8:13   ` David Marchand [this message]
2021-05-07 17:14     ` Dmitry Kozlyuk
     [not found] ` <>
2021-05-11 11:33   ` [dpdk-stable] [PATCH v2 1/2] net/ark: " David Marchand
2021-05-11 11:33   ` [dpdk-stable] [PATCH v2 2/2] net/ice: " David Marchand
2021-05-11 17:34     ` Dmitry Kozlyuk

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

patches for DPDK stable branches

This inbox may be cloned and mirrored by anyone:

	git clone --mirror stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ \
	public-inbox-index stable

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone