From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1027] mempool cache size parameter is misleading
Date: Tue, 07 Jun 2022 07:42:03 +0000 [thread overview]
Message-ID: <bug-1027-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1027
Bug ID: 1027
Summary: mempool cache size parameter is misleading
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: doc
Assignee: dev@dpdk.org
Reporter: mb@smartsharesystems.com
Target Milestone: ---
A flush threshold for the mempool cache was introduced in DPDK version
1.3. With this modification, the actual size of the mempool cache was
multiplied by 1.5, so e.g. a specified size of 512 allows the mempool cache to
hold up to 1.5 * 512 = 768 objects.
None of the documentation was updated to reflect this change.
E.g. the Programmer's Guide says:
"The maximum size of the cache is static and is defined at compilation time
(RTE_MEMPOOL_CACHE_MAX_SIZE)." But in reality, the maximum size of the cache is
RTE_MEMPOOL_CACHE_MAX_SIZE * 1.5.
Also, the "size" field of the rte_mempool_cache structure and the "cache_size"
parameter of the rte_mempool_create() function don't mention that the value is
1/1.5 of the actual size.
If we don't want to fix the code, then the documentation needs to be fixed.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-06-07 7:42 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-1027-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.