From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/2] netvsc PMD fixes for 19.05
Date: Thu, 2 May 2019 19:24:29 +0100 [thread overview]
Message-ID: <ba6a490b-243b-0e80-e2b2-ecc1b9feba6f@intel.com> (raw)
In-Reply-To: <20190430181217.20875-1-stephen@networkplumber.org>
On 4/30/2019 7:12 PM, Stephen Hemminger wrote:
> 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
Series applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-05-02 18:24 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 ` [dpdk-dev] [PATCH v2 0/2] netvsc PMD fixes for 19.05 Stephen Hemminger
2019-04-30 18:12 ` 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 ` Ferruh Yigit [this message]
2019-05-02 18:24 ` [dpdk-dev] [PATCH v2 0/2] netvsc PMD fixes for 19.05 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=ba6a490b-243b-0e80-e2b2-ecc1b9feba6f@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).