> From: Stephen Hemminger <step...@networkplumber.org> > Sent: Friday, April 16, 2021 11:09 AM > ... > On Fri, 16 Apr 2021 17:58:45 +0000 > Dexuan Cui <de...@microsoft.com> wrote: > > > > > > > > > This probably should be a separate patch. > > > > I think it is trying to address the case of VF discovery in > > > > Hyper-V/Azure > where > > > > the reported > > > > VF from Hypervisor is bogus or confused. > > > > > > This is for the Multi vPorts feature of MANA driver, which allows one VF > > > to > > > create multiple vPorts (NICs). They have the same PCI device and same VF > > > serial number, but different MACs. > > > > > > So we put the change in one patch to avoid distro vendors missing this > > > change when backporting the MANA driver. > > > > > > Thanks, > > > - Haiyang > > > > The netvsc change should come together in the same patch with this VF > > driver, otherwise the multi-vPorts functionality doesn't work properly. > > > > The netvsc change should not break any other existing VF drivers, because > > Hyper-V NIC SR-IOV implementation requires the the NetVSC network > > interface and the VF network interface should have the same MAC address, > > otherwise things won't work. > > > > Thanks, > > Dexuan > > Distro vendors should be able to handle a patch series. > Don't see why this could not be two patch series.
Ok. Will split this into 2 patches (the first one is the netvsc change, and the second is the Linux VF driver) and post v8 shortly.
