From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 255] Mbuf leak when rte_port_ethdev_writer_tx_bulk is called with more than 32 packets
Date: Tue, 16 Apr 2019 20:05:11 +0000 [thread overview]
Message-ID: <bug-255-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=255
Bug ID: 255
Summary: Mbuf leak when rte_port_ethdev_writer_tx_bulk is
called with more than 32 packets
Product: DPDK
Version: 18.05
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: jeyaga.ang@gmail.com
Target Milestone: ---
The test was run with Juniper Tungsten Fabric that uses DPDK 18.05. If the
rte_port_ethdev_writer_tx_bulk is called with more than 32 packets, there is
mbuf leak happening.
The code that calls the bulk send is as below
https://github.com/Juniper/contrail-vrouter/blob/master/dpdk/vr_dpdk_interface.c#L1871
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-04-16 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 20:05 bugzilla [this message]
2019-04-16 20:05 ` bugzilla
2019-05-22 19:49 ` 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-255-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).