All of lore.kernel.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-1622-3@http.bugs.dpdk.org/> (raw)

[-- 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 --]

                 reply	other threads:[~2025-01-28 18:59 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=bug-1622-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.