* [DPDK/ethdev Bug 1622] ntnic: using signals and threads
@ 2025-01-28 18:59 bugzilla
0 siblings, 0 replies; only message in thread
From: bugzilla @ 2025-01-28 18:59 UTC (permalink / raw)
To: dev
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1622
Bug ID: 1622
Summary: ntnic: using signals and threads
Product: DPDK
Version: 25.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
No PMD should be making its own threads and must not use standard signal types.
The ntnic PMD is spawning a thread and trying to trap SIGINT.
This is broken for many reasons:
- application may want to manage SIGINT after rte_eal_init() is called
- there are other shutdown signals beside SIGINT (SIGTERM, SIGQUIT, ...)
- spawning a thread outside of EAL creates resource management issues
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2793 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2025-01-28 18:59 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-01-28 18:59 [DPDK/ethdev Bug 1622] ntnic: using signals and threads bugzilla
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).