From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 291] FM10K dpdk driver - memory leak with KNI interface - interface up/down
Date: Tue, 04 Jun 2019 08:17:39 +0000 [thread overview]
Message-ID: <bug-291-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=291
Bug ID: 291
Summary: FM10K dpdk driver - memory leak with KNI interface -
interface up/down
Product: DPDK
Version: 16.11
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: david@silicom.co.il
Target Milestone: ---
Created attachment 40
--> https://bugs.dpdk.org/attachment.cgi?id=40&action=edit
patch done to dpdk 16.11.7 to fix the memory leak.
Fm10k dpdk driver – memory leak: we have seen that when working with the dpdk
driver 16.11.7 (but see this memory leak also on other dpdk versions - 19.05
probably some others) with KNI interface and doing loop of interface down and
up we see that there is memory leak. We have found the cause for that and we
think that we have the fix for that. i have attached the patch we did. if more
info is needed let us know.
thanks, David Hendel.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-06-04 8:17 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-291-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).