From: Zhe Tao <zhe.tao@intel.com>
To: dev@dpdk.org
Cc: wenzhuo.lu@intel.com, zhe.tao@intel.com,
konstantin.ananyev@intel.com, bruce.richardson@intel.com,
jing.d.chen@intel.com, cunming.liang@intel.com,
jingjing.wu@intel.com, helin.zhang@intel.com
Subject: [dpdk-dev] [PATCH v2 0/8] support reset of VF link
Date: Tue, 7 Jun 2016 13:45:10 +0800 [thread overview]
Message-ID: <1465278318-4949-1-git-send-email-zhe.tao@intel.com> (raw)
From: "zhe.tao" <zhe.tao@intel.com>
If the PF link is down and up, VF link will not work
accordingly.
This patch set addes the support of VF link reset. So, when VF
receices the messges of physical link down/up. APP can reset the
VF link and let it recover.
PS: This patch set is splitted from a previous patch set, *automatic
link recovery on ixgbe/igb VF*, and it's base on the patch set
*support mailbox interruption on ixgbe/igb VF*.
Wenzhuo Lu (6):
lib/librte_ether: support device reset
lib/librte_ether: defind RX/TX lock mode
ixgbe: RX/TX with lock on VF
ixgbe: implement device reset on VF
igb: RX/TX with lock on VF
igb: implement device reset on VF
zhe.tao (2):
i40e: RX/TX with lock on VF
i40e: implement device reset on VF
v1:
Added the implementation for the VF reset functionality.
v2:
Changed the i40e related operations during VF reset.
app/test-pmd/config.c | 3 +
doc/guides/rel_notes/release_16_07.rst | 14 +++
drivers/net/e1000/e1000_ethdev.h | 126 +++++++++++++++++++++++++++
drivers/net/e1000/igb_ethdev.c | 118 ++++++++++++++++++++++++-
drivers/net/e1000/igb_rxtx.c | 148 +++++++++-----------------------
drivers/net/i40e/i40e_ethdev.c | 4 +-
drivers/net/i40e/i40e_ethdev.h | 5 ++
drivers/net/i40e/i40e_ethdev_vf.c | 152 ++++++++++++++++++++++++++++++++-
drivers/net/i40e/i40e_rxtx.c | 55 ++++++++----
drivers/net/i40e/i40e_rxtx.h | 34 ++++++++
drivers/net/ixgbe/ixgbe_ethdev.c | 120 +++++++++++++++++++++++++-
drivers/net/ixgbe/ixgbe_ethdev.h | 32 ++++++-
drivers/net/ixgbe/ixgbe_rxtx.c | 116 ++++++++++++++++++++++---
drivers/net/ixgbe/ixgbe_rxtx.h | 13 +++
drivers/net/ixgbe/ixgbe_rxtx_vec.c | 6 ++
lib/librte_ether/rte_ethdev.c | 17 ++++
lib/librte_ether/rte_ethdev.h | 76 +++++++++++++++++
lib/librte_ether/rte_ether_version.map | 7 ++
18 files changed, 898 insertions(+), 148 deletions(-)
--
2.1.4
next reply other threads:[~2016-06-07 5:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 5:45 Zhe Tao [this message]
2016-06-07 5:45 ` [dpdk-dev] [PATCH v2 1/8] lib/librte_ether: support device reset Zhe Tao
2016-06-07 5:45 ` [dpdk-dev] [PATCH v2 2/8] lib/librte_ether: defind RX/TX lock mode Zhe Tao
2016-06-07 5:45 ` [dpdk-dev] [PATCH v2 3/8] ixgbe: RX/TX with lock on VF Zhe Tao
2016-06-07 5:45 ` [dpdk-dev] [PATCH v2 4/8] ixgbe: implement device reset " Zhe Tao
2016-06-07 5:45 ` [dpdk-dev] [PATCH v2 5/8] igb: RX/TX with lock " Zhe Tao
2016-06-07 5:45 ` [dpdk-dev] [PATCH v2 6/8] igb: implement device reset " Zhe Tao
2016-06-07 5:45 ` [dpdk-dev] [PATCH v2 7/8] i40e: RX/TX with lock " Zhe Tao
2016-06-07 5:45 ` [dpdk-dev] [PATCH v2 8/8] i40e: implement device reset " Zhe Tao
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=1465278318-4949-1-git-send-email-zhe.tao@intel.com \
--to=zhe.tao@intel.com \
--cc=bruce.richardson@intel.com \
--cc=cunming.liang@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=jing.d.chen@intel.com \
--cc=jingjing.wu@intel.com \
--cc=konstantin.ananyev@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).