From: Long Li <longli@microsoft.com>
To: Jakub Kicinski <kuba@kernel.org>, Long Li <longli@linuxonhyperv.com>
Cc: KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Wei Liu <wei.liu@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2 0/3] hv_netvsc: Prevent packet loss during VF add/remove
Date: Tue, 12 Jan 2021 21:31:23 +0000 [thread overview]
Message-ID: <MN2PR21MB11666A2B3D026DA710E470ADCEAA9@MN2PR21MB1166.namprd21.prod.outlook.com> (raw)
In-Reply-To: <20210111180717.19126810@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
> Subject: Re: [PATCH v2 0/3] hv_netvsc: Prevent packet loss during VF
> add/remove
>
> On Fri, 8 Jan 2021 16:53:40 -0800 Long Li wrote:
> > From: Long Li <longli@microsoft.com>
> >
> > This patch set fixes issues with packet loss on VF add/remove.
>
> These patches are for net-next? They just optimize the amount of packet
> loss on switch, not fix bugs, right?
Yes, those patches are for net-next.
They eliminate the packet loss introduced from Linux side during VF changes. They can be seen as optimizations.
next prev parent reply other threads:[~2021-01-12 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 0:53 [PATCH v2 0/3] hv_netvsc: Prevent packet loss during VF add/remove Long Li
2021-01-09 0:53 ` [PATCH v2 1/3] hv_netvsc: Check VF datapath when sending traffic to VF Long Li
2021-01-09 0:53 ` [PATCH v2 2/3] hv_netvsc: Wait for completion on request SWITCH_DATA_PATH Long Li
2021-01-09 0:53 ` [PATCH v2 3/3] hv_netvsc: Process NETDEV_GOING_DOWN on VF hot remove Long Li
2021-01-12 2:07 ` [PATCH v2 0/3] hv_netvsc: Prevent packet loss during VF add/remove Jakub Kicinski
2021-01-12 21:31 ` Long Li [this message]
2021-01-13 4:10 ` patchwork-bot+netdevbpf
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=MN2PR21MB11666A2B3D026DA710E470ADCEAA9@MN2PR21MB1166.namprd21.prod.outlook.com \
--to=longli@microsoft.com \
--cc=davem@davemloft.net \
--cc=haiyangz@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@linuxonhyperv.com \
--cc=netdev@vger.kernel.org \
--cc=sthemmin@microsoft.com \
--cc=wei.liu@kernel.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).