All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1706] CPU affinity of registered non-EAL threads not reflected in lcore configuration
Date: Wed, 14 May 2025 09:29:31 +0000	[thread overview]
Message-ID: <bug-1706-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1706
           Summary: CPU affinity of registered non-EAL threads not
                    reflected in lcore configuration
           Product: DPDK
           Version: 25.03
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: mb@smartsharesystems.com
  Target Milestone: ---

If the CPU affinity of a registered non-EAL thread is changed by calling
rte_thread_set_affinity_by_id(), rte_lcore_cpuset() does not return the new CPU
affinity.

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

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

                 reply	other threads:[~2025-05-14  9:29 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-1706-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.