All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1980] mempool name size assumes ring driver
Date: Tue, 11 Aug 2026 09:28:03 +0000	[thread overview]
Message-ID: <bug-1980-3@http.bugs.dpdk.org/> (raw)

http://bugs.dpdk.org/show_bug.cgi?id=1980

            Bug ID: 1980
           Summary: mempool name size assumes ring driver
           Product: DPDK
           Version: 26.07
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: mb@smartsharesystems.com
  Target Milestone: ---

When creating a mempool, the length of its name is checked.
RTE_MEMPOOL_NAMESIZE defines the max allowed length, and is derived from the
names of the memzones created for the mempool.
The mempool itself creates a memzone named "MP_name".
When using the Ring driver, the driver creates a memzone named "RG_MP_name".
This is what RTE_MEMPOOL_NAMESIZE is based on:
Max memzone name - strlen("RG_") - strlen("MP_").

Now, when using the Stack driver, the driver creates a memzone named
"STK_MP_name".
In this case, the RTE_MEMPOOL_NAMESIZE should be one byte less.
With a long name, creating the mempool will succeed, but populating it will
fail when the mempool driver tries to allocate the memzone for the mempool
entries.

Reducing RTE_MEMPOOL_NAMESIZE (by one) to consider the memzone name created by
the Stack driver would be an API change, and would not consider other drivers
possibly using even longer memzone names.

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

                 reply	other threads:[~2026-08-11  9:28 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-1980-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.