[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BL0PR2101MB093051C80B1625AAE3728551CA4A0@BL0PR2101MB0930.namprd21.prod.outlook.com>
Date: Tue, 4 Aug 2020 17:26:43 +0000
From: Haiyang Zhang <haiyangz@...rosoft.com>
To: Stephen Hemminger <stephen@...workplumber.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"wei.liu@...nel.org" <wei.liu@...nel.org>,
"Shah, Ashish N" <ashish.n.shah@...el.com>
Subject: RE: [PATCH] hv_netvsc: do not use VF device if link is down
> -----Original Message-----
> From: Stephen Hemminger <stephen@...workplumber.org>
> Sent: Tuesday, August 4, 2020 12:54 PM
> To: Haiyang Zhang <haiyangz@...rosoft.com>; davem@...emloft.net;
> kuba@...nel.org
> Cc: netdev@...r.kernel.org; wei.liu@...nel.org; Stephen Hemminger
> <stephen@...workplumber.org>; Shah, Ashish N <ashish.n.shah@...el.com>
> Subject: [PATCH] hv_netvsc: do not use VF device if link is down
>
> If the accelerated networking SRIOV VF device has lost carrier
> use the synthetic network device which is available as backup
> path. This is a rare case since if VF link goes down, normally
> the VMBus device will also loose external connectivity as well.
> But if the communication is between two VM's on the same host
> the VMBus device will still work.
>
> Reported-by: "Shah, Ashish N" <ashish.n.shah@...el.com>
> Fixes: 0c195567a8f6 ("netvsc: transparent VF management")
> Signed-off-by: Stephen Hemminger <stephen@...workplumber.org>
Reviewed-by: Haiyang Zhang <haiyangz@...rosoft.com>
Thank you.
Powered by blists - more mailing lists