From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Zhu, TaoX" <taox.zhu@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Ye, Xiaolong" <xiaolong.ye@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"martin.weiser@allegro-packets.com"
<martin.weiser@allegro-packets.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v5] net/ixgbe: fix resource leak after thread exits normally
Date: Tue, 21 Apr 2020 22:37:50 +0000 [thread overview]
Message-ID: <BYAPR11MB3301CDBC72C1549C4FCA70D79AD50@BYAPR11MB3301.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200421185320.16946-1-taox.zhu@intel.com>
>
> When the thread exits normally, pthread_join() is not called, which can
> result in a resource leak. Therefore, the thread is set to separation
> mode using function pthread_detach(), so that no program call
> pthread_join() is required to recycle, and when the thread exits,
> the system automatically reclaims resources.
>
> Wait for the thread to finish with timeout argument(0 means that it will
> not return until link complete), wait until the thread finishes before
> returning. Normally, the thread will finish in a shorter time, and give
> a warning message if it hasn't finished in a longer time.
>
> Fixes: 819d0d1d57f1 ("net/ixgbe: fix blocking system events")
> Cc: stable@dpdk.org
>
> Signed-off-by: Zhu Tao <taox.zhu@intel.com>
> ---
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> --
> 1.8.3.1
next prev parent reply other threads:[~2020-04-21 22:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 5:18 [dpdk-dev] [PATCH] net/ixgbe: fix resource leak after thread exits normally taox.zhu
2020-04-10 6:22 ` [dpdk-dev] [PATCH v2] " taox.zhu
2020-04-10 12:09 ` Ananyev, Konstantin
[not found] ` <60652C6914E08D41B9AA1580751B3CA9015ED8D2@SHSMSX103.ccr.corp.intel.com>
2020-04-14 10:25 ` Ananyev, Konstantin
2020-04-14 11:26 ` Ananyev, Konstantin
2020-04-15 12:27 ` [dpdk-dev] [PATCH v3] " taox.zhu
2020-04-15 14:18 ` [dpdk-dev] [PATCH v4] " taox.zhu
2020-04-20 8:49 ` Ye Xiaolong
2020-04-21 18:53 ` [dpdk-dev] [PATCH v5] " taox.zhu
2020-04-21 22:37 ` Ananyev, Konstantin [this message]
2020-04-22 2:33 ` Ye Xiaolong
2020-04-22 12:37 ` [dpdk-dev] [PATCH v6] " taox.zhu
2020-04-22 5:18 ` Ye Xiaolong
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=BYAPR11MB3301CDBC72C1549C4FCA70D79AD50@BYAPR11MB3301.namprd11.prod.outlook.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=martin.weiser@allegro-packets.com \
--cc=stable@dpdk.org \
--cc=taox.zhu@intel.com \
--cc=wenzhuo.lu@intel.com \
--cc=xiaolong.ye@intel.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 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.