From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH v2 0/2] netvsc PMD fixes for 19.05
Date: Tue, 30 Apr 2019 11:12:15 -0700 [thread overview]
Message-ID: <20190430181217.20875-1-stephen@networkplumber.org> (raw)
In-Reply-To: <20190429203325.10696-1-stephen@networkplumber.org>
Netvsc needed to reset incoming port as was recently done
for failsafe. Implement the new close semantics.
Stephen Hemminger (2):
net/netvsc: reset mbuf port on VF receive
net/netvsc: free all queues on close
drivers/net/netvsc/hn_ethdev.c | 8 ++-
drivers/net/netvsc/hn_rxtx.c | 93 ++++++++++++++++++++++++----------
drivers/net/netvsc/hn_var.h | 1 +
drivers/net/netvsc/hn_vf.c | 11 +++-
4 files changed, 82 insertions(+), 31 deletions(-)
--
2.20.1
next prev parent reply other threads:[~2019-04-30 18:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 20:33 [dpdk-dev] [PATCH 0/2] netvsc pmd " Stephen Hemminger
2019-04-29 20:33 ` Stephen Hemminger
2019-04-29 20:33 ` [dpdk-dev] [PATCH 1/2] net/netvsc: reset mbuf port on VF receive Stephen Hemminger
2019-04-29 20:33 ` Stephen Hemminger
2019-04-30 8:01 ` Ferruh Yigit
2019-04-30 8:01 ` Ferruh Yigit
2019-04-30 15:05 ` Stephen Hemminger
2019-04-30 15:05 ` Stephen Hemminger
2019-04-29 20:33 ` [dpdk-dev] [PATCH 2/2] net/netvsc: free all queues on close Stephen Hemminger
2019-04-29 20:33 ` Stephen Hemminger
2019-04-30 8:11 ` Ferruh Yigit
2019-04-30 8:11 ` Ferruh Yigit
2019-04-30 18:12 ` Stephen Hemminger [this message]
2019-04-30 18:12 ` [dpdk-dev] [PATCH v2 0/2] netvsc PMD fixes for 19.05 Stephen Hemminger
2019-04-30 18:12 ` [dpdk-dev] [PATCH v2 1/2] net/netvsc: reset mbuf port on VF receive Stephen Hemminger
2019-04-30 18:12 ` Stephen Hemminger
2019-04-30 18:12 ` [dpdk-dev] [PATCH v2 2/2] net/netvsc: free all queues on close Stephen Hemminger
2019-04-30 18:12 ` Stephen Hemminger
2019-05-02 18:24 ` [dpdk-dev] [PATCH v2 0/2] netvsc PMD fixes for 19.05 Ferruh Yigit
2019-05-02 18:24 ` Ferruh Yigit
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=20190430181217.20875-1-stephen@networkplumber.org \
--to=stephen@networkplumber.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).