From: Jingjing Wu <jingjing.wu@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 0/2] i40evf: support interrupt based pf reset request
Date: Wed, 27 Jan 2016 09:46:36 +0800 [thread overview]
Message-ID: <1453859198-23617-1-git-send-email-jingjing.wu@intel.com> (raw)
v2 changes:
remove the change on vf reset status checking
add pf event report support in release note
If DPDK is used on VF while the host is using Linux Kernel
driver as PF driver on FVL NIC, some setting on PF will trigger
VF reset. DPDK VF need to know the event.
This patch set makes the interrupt based request of PF reset
from PF supported by enabling the adminq event process in
VF driver.
Users can register a callback for this interrupt event to get
informed, when a PF reset request detected like:
rte_eth_dev_callback_register(portid,
RTE_ETH_EVENT_INTR_RESET,
reset_event_callback,
arg);
Jingjing Wu (2):
i40evf: allocate virtchnl cmd buffer for each vf
i40evf: support interrupt based pf reset request
doc/guides/rel_notes/release_2_3.rst | 1 +
drivers/net/i40e/i40e_ethdev.h | 2 +
drivers/net/i40e/i40e_ethdev_vf.c | 423 +++++++++++++++++++++++++----------
lib/librte_ether/rte_ethdev.h | 1 +
4 files changed, 304 insertions(+), 123 deletions(-)
--
2.4.0
next reply other threads:[~2016-01-27 1:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 1:46 Jingjing Wu [this message]
2016-01-27 1:46 ` [dpdk-dev] [PATCH v2 1/2] i40evf: allocate virtchnl cmd buffer for each vf Jingjing Wu
2016-01-27 1:46 ` [dpdk-dev] [PATCH v2 2/2] i40evf: support interrupt based pf reset request Jingjing Wu
-- strict thread matches above, loose matches on Subject: below --
2016-01-13 12:31 [dpdk-dev] [PATCH 0/2] " Jingjing Wu
2016-01-27 1:49 ` [dpdk-dev] [PATCH v2 " Jingjing Wu
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=1453859198-23617-1-git-send-email-jingjing.wu@intel.com \
--to=jingjing.wu@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).