[dpdk-dev] [PATCH 02/13] net/failsafe: check code of promiscuous mode switch

Stephen Hemminger stephen at networkplumber.org
Thu Sep 5 19:13:19 CEST 2019


On Thu, 5 Sep 2019 19:49:09 +0300
Andrew Rybchenko <arybchenko at solarflare.com> wrote:

> On 9/5/19 7:40 PM, Stephen Hemminger wrote:
> > On Thu, 5 Sep 2019 17:10:40 +0100
> > Andrew Rybchenko <arybchenko at solarflare.com> wrote:
> >  
> >> From: Ivan Ilchenko <Ivan.Ilchenko at oktetlabs.ru>
> >>
> >> rte_eth_promiscuous_enable()/rte_eth_promiscuous_disable() return
> >> value was changed from void to int, so this patch modify usage
> >> of these functions across net/failsafe according to new return type.
> >>
> >> Try to keep promiscuous mode consistent across all active
> >> devices in the case of failure.
> >>
> >> Signed-off-by: Ivan Ilchenko <Ivan.Ilchenko at oktetlabs.ru>
> >> Signed-off-by: Andrew Rybchenko <arybchenko at solarflare.com>  
> > In reality, failsafe's promiscious mode is actually a lie.
> > The only common use case of failsafe is on Azure/Hyper-V and in a guest
> > setting promiscuous is not allowed. That is why there is no promiscuous
> > setting in netvsc PMD.  

I forgot Hyper-V is not same as Azure.
It will always fail on Azure, but will work be allowed on Hyper-V (if enabled on host).


More information about the dev mailing list