All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1696] eth_dev_start can not be called by a secondary process
Date: Fri, 11 Apr 2025 00:27:04 +0000	[thread overview]
Message-ID: <bug-1696-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 875 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1696

            Bug ID: 1696
           Summary: eth_dev_start can not be called by a secondary process
           Product: DPDK
           Version: 25.03
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: stephen@networkplumber.org
  Target Milestone: ---

The problem is that if secondary process calls eth_dev_start it doesn't end up
impacting the primary process (or other secondary processes).

Either:
- eth_dev_start should not be allowed from secondary proces
- or eth_dev_start needs to have MP hook and cause it to be proxied to primary.

Related to Bug # 73?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 2969 bytes --]

                 reply	other threads:[~2025-04-11  0:27 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-1696-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.