[DPDK/core Bug 1980] mempool name size assumes ring driver

[DPDK/core Bug 1980] mempool name size assumes ring driver

[bugzilla]

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.