From: Stephen Hemminger <stephen@networkplumber.org>
To: Gagandeep Singh <G.Singh@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] eal: add worker threads cleanup in rte_eal_cleanup()
Date: Mon, 30 Mar 2026 13:38:18 -0700 [thread overview]
Message-ID: <20260330133819.7219f905@phoenix.local> (raw)
In-Reply-To: <AS8PR04MB8198C9AD2F57C3E178B8DC92E1182@AS8PR04MB8198.eurprd04.prod.outlook.com>
On Tue, 14 Jan 2025 04:53:51 +0000
Gagandeep Singh <G.Singh@nxp.com> wrote:
> This is fine for graceful application termination, but what about non-graceful application termination?
> I have a DPAA bus cleanup patch ready, and will submit it soon, But we still need
> destructor in case application exit without calling the rte_eal_cleanup().
Any destructor has to use only signal safe functions. if you want to handle non-graceful shutdown.
That is really hard to do.
next prev parent reply other threads:[~2026-03-30 20:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 6:47 [PATCH] eal: add worker threads cleanup in rte_eal_cleanup() Gagandeep Singh
2025-01-10 17:19 ` Stephen Hemminger
2025-01-13 5:13 ` Gagandeep Singh
2025-01-13 16:40 ` Stephen Hemminger
2025-01-14 4:53 ` Gagandeep Singh
2025-01-14 16:26 ` Stephen Hemminger
2026-03-30 20:38 ` Stephen Hemminger [this message]
2026-03-30 20:39 ` Stephen Hemminger
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=20260330133819.7219f905@phoenix.local \
--to=stephen@networkplumber.org \
--cc=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