From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path:
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
by inbox.dpdk.org (Postfix) with ESMTP id C636145F7C;
Tue, 28 Jan 2025 19:59:56 +0100 (CET)
Received: from mails.dpdk.org (localhost [127.0.0.1])
by mails.dpdk.org (Postfix) with ESMTP id 780C740151;
Tue, 28 Jan 2025 19:59:56 +0100 (CET)
Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178])
by mails.dpdk.org (Postfix) with ESMTP id 9AF4740144
for ; Tue, 28 Jan 2025 19:59:55 +0100 (CET)
Received: by inbox.dpdk.org (Postfix, from userid 33)
id 82DB246000; Tue, 28 Jan 2025 19:59:55 +0100 (CET)
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1622] ntnic: using signals and threads
Date: Tue, 28 Jan 2025 18:59:54 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: DPDK
X-Bugzilla-Component: ethdev
X-Bugzilla-Version: 25.03
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: stephen@networkplumber.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: dev@dpdk.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
op_sys bug_status bug_severity priority component assigned_to reporter
target_milestone
Message-ID:
Content-Type: multipart/alternative; boundary=17380907950.cdEFd3a.2401326
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
MIME-Version: 1.0
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dev-bounces@dpdk.org
--17380907950.cdEFd3a.2401326
Date: Tue, 28 Jan 2025 19:59:55 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
https://bugs.dpdk.org/show_bug.cgi?id=3D1622
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 ty=
pes.
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
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--17380907950.cdEFd3a.2401326
Date: Tue, 28 Jan 2025 19:59:55 +0100
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
No PMD should be making its own th=
reads 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