All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1704] CPU_SETSIZE should not be used
Date: Fri, 02 May 2025 15:47:58 +0000	[thread overview]
Message-ID: <bug-1704-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1704
           Summary: CPU_SETSIZE should not be used
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: mb@smartsharesystems.com
  Target Milestone: ---

The EAL assumes that cpu_set_t is an array holding CPU_SETSIZE elements.
This doesn't work when the host has more physical CPU cores than CPU_SETSIZE.

Instead, it should use CPU_ALLOC()/CPU_FREE() with the correct number of
physical CPU cores in the host.

man CPU_SET(3):
https://man7.org/linux/man-pages/man3/CPU_SET.3.html

-- 
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-05-02 15:48 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-1704-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.