On Mon, Dec 18, 2017 at 12:13 PM, Thomas Monjalon
wrote:
> 18/12/2017 19:23, Stephen Hemminger:
> > Please don't call this drivers/net/hyperv/
> > that name conflicts with the real netvsc PMD that I am working on.
> >
> > Maybe vdev-netvsc?
>
> I expect your PMD to be in drivers/net/netvsc/
> Why
On Mon, Dec 18, 2017 at 10:23:04AM -0800, Stephen Hemminger wrote:
> On Mon, 18 Dec 2017 17:46:19 +0100
> Adrien Mazarguil wrote:
>
> > Virtual machines hosted by Hyper-V/Azure platforms are fitted with
> > simplified virtual network devices named NetVSC that are used for fast
> > communication b
18/12/2017 19:23, Stephen Hemminger:
> Please don't call this drivers/net/hyperv/
> that name conflicts with the real netvsc PMD that I am working on.
>
> Maybe vdev-netvsc?
I expect your PMD to be in drivers/net/netvsc/
Why is it conflicting with drivers/net/hyperv/ ?
On Mon, 18 Dec 2017 17:46:19 +0100
Adrien Mazarguil wrote:
> Virtual machines hosted by Hyper-V/Azure platforms are fitted with
> simplified virtual network devices named NetVSC that are used for fast
> communication between VM to VM, VM to hypervisor, and the outside.
>
> They appear as standar
Virtual machines hosted by Hyper-V/Azure platforms are fitted with
simplified virtual network devices named NetVSC that are used for fast
communication between VM to VM, VM to hypervisor, and the outside.
They appear as standard system netdevices to user-land applications, the
main difference bein
5 matches
Mail list logo