From: Haiyue Wang <haiyue.wang@intel.com>
To: dev@dpdk.org
Cc: Haiyue Wang <haiyue.wang@intel.com>
Subject: [dpdk-dev] [PATCH v2 1/2] net/ice: fix the missed memory free when dev is closed
Date: Mon, 14 Oct 2019 22:50:04 +0800 [thread overview]
Message-ID: <20191014145005.94650-2-haiyue.wang@intel.com> (raw)
In-Reply-To: <20191014145005.94650-1-haiyue.wang@intel.com>
The original protocol extraction memory free is removed by introducing
new design for releasing port upon close.
Fixes: bd513ece3c40 ("net/ice: release port upon close")
Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
---
drivers/net/ice/ice_ethdev.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/ice/ice_ethdev.c b/drivers/net/ice/ice_ethdev.c
index 022b58c01..880d2679b 100644
--- a/drivers/net/ice/ice_ethdev.c
+++ b/drivers/net/ice/ice_ethdev.c
@@ -2126,6 +2126,8 @@ ice_dev_close(struct rte_eth_dev *dev)
rte_free(hw->port_info);
hw->port_info = NULL;
ice_shutdown_all_ctrlq(hw);
+ rte_free(pf->proto_xtr);
+ pf->proto_xtr = NULL;
dev->dev_ops = NULL;
dev->rx_pkt_burst = NULL;
--
2.17.1
next prev parent reply other threads:[~2019-10-14 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 13:07 [dpdk-dev] [PATCH v1] net/ice: avoid the parsed devargs value being overwritten Haiyue Wang
2019-10-14 8:24 ` Ye Xiaolong
2019-10-14 13:51 ` Wang, Haiyue
2019-10-14 14:50 ` [dpdk-dev] [PATCH v2 0/2] net/ice: protocol extraction related issues Haiyue Wang
2019-10-14 14:50 ` Haiyue Wang [this message]
2019-10-14 14:50 ` [dpdk-dev] [PATCH v2 2/2] net/ice: avoid the parsed devargs value being overwritten Haiyue Wang
2019-10-14 23:21 ` [dpdk-dev] [PATCH v2 0/2] net/ice: protocol extraction related issues Ye Xiaolong
2019-10-16 3:05 ` Ye Xiaolong
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=20191014145005.94650-2-haiyue.wang@intel.com \
--to=haiyue.wang@intel.com \
--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).