From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 242] repeat to calling 'rte_pktmbuf_free' function, make the mempool exist the same 'rte_mbuf' obj;
Date: Mon, 08 Apr 2019 11:45:43 +0000 [thread overview]
Message-ID: <bug-242-3@http.bugs.dpdk.org/> (raw)
Message-ID: <20190408114543.5kz6BclWliUS1EtST70TaTuauvDzPBd1hE9pXin76tk@z> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=242
Bug ID: 242
Summary: repeat to calling 'rte_pktmbuf_free' function, make
the mempool exist the same 'rte_mbuf' obj;
Product: DPDK
Version: 18.11
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: linke0602@live.cn
Target Milestone: ---
when I use 'rte_pktmbuf_free' function to free the same packet many times, the
mp->pool_data contains the same 'rte_mbuf' obj; As a result, packet coming from
'rte_pktmbuf_alloc' function exist packet change unexplainably. In
'rte_pktbuf_prefee_seg' function, m->refcnt only decreases to 1, this is q
question?
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-04-08 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 11:45 bugzilla [this message]
2019-04-08 11:45 ` 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-242-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).