From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1471] rte_pktmbuf_free_bulk does not respect RTE_LIBRTE_MBUF_DEBUG
Date: Fri, 21 Jun 2024 18:33:05 +0000 [thread overview]
Message-ID: <bug-1471-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1471
Bug ID: 1471
Summary: rte_pktmbuf_free_bulk does not respect
RTE_LIBRTE_MBUF_DEBUG
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: ---
rte_pktmbuf_free_bulk() calls __rte_mbuf_sanity_check(), which behaves
differently depending on RTE_LIBRTE_MBUF_DEBUG being defined or not.
Unfortunately, rte_pktmbuf_free_bulk() is not inline, but in the C file.
This means that the behavior of __rte_mbuf_sanity_check() within
rte_pktmbuf_free_bulk() is controlled by the RTE_LIBRTE_MBUF_DEBUG setting when
building the DPDK library, not when building the application.
rte_pktmbuf_free_bulk() should have been inline in the header file, so the
application developer can control its __rte_mbuf_sanity_check() behavior by
using RTE_LIBRTE_MBUF_DEBUG setting when building the application.
How to remove this function from the ABI and make it inline instead?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3174 bytes --]
next reply other threads:[~2024-06-21 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 18:33 bugzilla [this message]
2024-06-21 19:03 ` [DPDK/core Bug 1471] Some rte_pktmbuf functions do " bugzilla
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-1471-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).