Skip to contentSkip to conversation

ntnic: using signals and threads

DPDK/ethdev Bug 1622 [email protected] 1 participant 1 message Jan 28, 2025

lore
Share & tools
lore
#0 lore raw

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: [email protected]
          Reporter: [email protected]

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

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.