From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1471] Some rte_pktmbuf functions do not respect RTE_LIBRTE_MBUF_DEBUG
Date: Fri, 21 Jun 2024 19:03:56 +0000 [thread overview]
Message-ID: <bug-1471-3-Q0c20H5zzy@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1471-3@http.bugs.dpdk.org/>
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1471
Morten Brørup (mb@smartsharesystems.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Morten Brørup (mb@smartsharesystems.com) ---
I tend to agree with you on this.
Although older versions of the mbuf library didn't have this restriction for
RTE_LIBRTE_MBUF_DEBUG (which was only used in the header file, and thus
controllable for the application build), RTE_LIBRTE_MEMPOOL_DEBUG works as you
describe, so the same could be reasonably assumed about RTE_LIBRTE_MBUF_DEBUG.
Let's not consider it a bug.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2941 bytes --]
prev parent reply other threads:[~2024-06-21 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 18:33 [DPDK/core Bug 1471] rte_pktmbuf_free_bulk does " bugzilla
2024-06-21 19:03 ` bugzilla [this message]
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-Q0c20H5zzy@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).