From: Gagandeep Singh <g.singh@nxp.com>
To: dev@dpdk.org
Subject: [PATCH] eal: add worker threads cleanup in rte_eal_cleanup()
Date: Fri, 10 Jan 2025 12:17:17 +0530 [thread overview]
Message-ID: <20250110064717.1372216-1-g.singh@nxp.com> (raw)
This patch introduces a worker thread cleanup function in the EAL library,
ensuring proper termination of created pthreads and invocation of
registered pthread destructors.
This guarantees the correct cleanup of thread-specific resources,
used by drivers or applications.
Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
---
lib/eal/linux/eal.c | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/lib/eal/linux/eal.c b/lib/eal/linux/eal.c
index a6220524a4..a828905783 100644
--- a/lib/eal/linux/eal.c
+++ b/lib/eal/linux/eal.c
@@ -913,6 +913,32 @@ eal_worker_thread_create(unsigned int lcore_id)
return ret;
}
+static void
+eal_worker_thread_cleanup(void)
+{
+ unsigned int lcore_id;
+ int ret = 0;
+
+ /* Cancel all the worker pthreads */
+ RTE_LCORE_FOREACH_WORKER(lcore_id) {
+ /* Check for non zero id */
+ if (!lcore_config[lcore_id].thread_id.opaque_id)
+ continue;
+
+ ret = pthread_cancel((pthread_t)lcore_config[lcore_id].thread_id.opaque_id);
+ if (ret != 0) {
+ EAL_LOG(WARNING, "Pthread cancel fails for lcore %d",
+ lcore_id);
+ }
+ ret = pthread_join((pthread_t)lcore_config[lcore_id].thread_id.opaque_id, NULL);
+ if (ret != 0) {
+ EAL_LOG(WARNING, "Pthread join fails for lcore %d",
+ lcore_id);
+ }
+ }
+ EAL_LOG(DEBUG, "Worker thread clean up done");
+}
+
/* Launch threads, called at application init(). */
int
rte_eal_init(int argc, char **argv)
@@ -1321,6 +1347,7 @@ rte_eal_cleanup(void)
#endif
rte_mp_channel_cleanup();
eal_bus_cleanup();
+ eal_worker_thread_cleanup();
rte_trace_save();
eal_trace_fini();
eal_mp_dev_hotplug_cleanup();
--
2.25.1
reply other threads:[~2025-01-10 6:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250110064717.1372216-1-g.singh@nxp.com \
--to=g.singh@nxp.com \
--cc=dev@dpdk.org \
/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).