From: Dexuan Cui <decui@microsoft.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Haiyang Zhang <haiyangz@microsoft.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
KY Srinivasan <kys@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
"wei.liu@kernel.org" <wei.liu@kernel.org>,
Wei Liu <liuwe@microsoft.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"leon@kernel.org" <leon@kernel.org>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"bernd@petrovitsch.priv.at" <bernd@petrovitsch.priv.at>,
"rdunlap@infradead.org" <rdunlap@infradead.org>,
Shachar Raindel <shacharr@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>
Subject: RE: [PATCH v7 net-next] net: mana: Add a driver for Microsoft Azure Network Adapter (MANA)
Date: Fri, 16 Apr 2021 18:44:31 +0000 [thread overview]
Message-ID: <MW2PR2101MB089264E445CE0F4E08BC913DBF4C9@MW2PR2101MB0892.namprd21.prod.outlook.com> (raw)
In-Reply-To: <20210416110836.67a4a88e@hermes.local>
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Friday, April 16, 2021 11:09 AM
> ...
> On Fri, 16 Apr 2021 17:58:45 +0000
> Dexuan Cui <decui@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.
prev parent reply other threads:[~2021-04-16 18:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210416060705.21998-1-decui@microsoft.com>
2021-04-16 16:40 ` [PATCH v7 net-next] net: mana: Add a driver for Microsoft Azure Network Adapter (MANA) Stephen Hemminger
2021-04-16 17:10 ` Haiyang Zhang
2021-04-16 17:58 ` Dexuan Cui
2021-04-16 18:08 ` Stephen Hemminger
2021-04-16 18:44 ` Dexuan Cui [this message]
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=MW2PR2101MB089264E445CE0F4E08BC913DBF4C9@MW2PR2101MB0892.namprd21.prod.outlook.com \
--to=decui@microsoft.com \
--cc=andrew@lunn.ch \
--cc=bernd@petrovitsch.priv.at \
--cc=davem@davemloft.net \
--cc=haiyangz@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=leon@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuwe@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=shacharr@microsoft.com \
--cc=stephen@networkplumber.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).