From: Di ChenxuX <chenxux.di@intel.com>
To: dev@dpdk.org
Cc: Wenzhuo Lu <wenzhuo.lu@intel.com>,
Beilei Xing <beilei.xing@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Yang Qiming <qiming.yang@intel.com>,
Di ChenxuX <chenxux.di@intel.com>
Subject: [dpdk-dev] [PATCH 0/5] drivers/net: release port upon close
Date: Mon, 2 Sep 2019 10:27:40 +0000 [thread overview]
Message-ID: <20190902102745.66695-1-chenxux.di@intel.com> (raw)
Set RTE_ETH_DEV_CLOSE_REMOVE upon probe so all the private resources
for the port can be freed by rte_eth_dev_close().
This patch cover all the intel drivers.
Di ChenxuX (5):
net/e1000: release port upon close
net/fm10k: release port upon close
net/i40e: release port upon close
net/ice: release port upon close
net/ixgbe: release port upon close
drivers/net/e1000/e1000_ethdev.h | 1 +
drivers/net/e1000/igb_ethdev.c | 142 +++++++++++++-----------
drivers/net/fm10k/fm10k.h | 3 +
drivers/net/fm10k/fm10k_ethdev.c | 122 ++++++++++++---------
drivers/net/i40e/i40e_ethdev.c | 131 +++++++++++-----------
drivers/net/i40e/i40e_ethdev_vf.c | 25 +++--
drivers/net/ice/ice_ethdev.c | 33 ++++--
drivers/net/ice/ice_ethdev.h | 1 +
drivers/net/ixgbe/ixgbe_ethdev.c | 176 +++++++++++++++++-------------
drivers/net/ixgbe/ixgbe_ethdev.h | 2 +
10 files changed, 362 insertions(+), 274 deletions(-)
--
2.17.1
next reply other threads:[~2019-09-02 11:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 10:27 Di ChenxuX [this message]
2019-09-02 10:27 ` [dpdk-dev] [PATCH 1/5] net/e1000: " Di ChenxuX
2019-09-02 15:59 ` Ye Xiaolong
2019-09-02 10:27 ` [dpdk-dev] [PATCH 2/5] net/fm10k: " Di ChenxuX
2019-09-02 10:27 ` [dpdk-dev] [PATCH 3/5] net/i40e: " Di ChenxuX
2019-09-02 10:27 ` [dpdk-dev] [PATCH 4/5] net/ice: " Di ChenxuX
2019-09-02 15:51 ` Ye Xiaolong
2019-09-02 10:27 ` [dpdk-dev] [PATCH 5/5] net/ixgbe: " Di ChenxuX
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=20190902102745.66695-1-chenxux.di@intel.com \
--to=chenxux.di@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=wenzhuo.lu@intel.com \
/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).