Hi
+ Shahaf
From: Stephen Hemminger
> On Wed, 12 Jun 2019 05:15:47 +
> Matan Azrad wrote:
>
> > From: Stephen Hemminger
> > > > Hi Stephen
> > > >
> > > > From: Stephen Hemminger
> > > > > When using DPDK on Azure it is common to have one non-DPDK
> > > interface.
> > > > > If that non-D
On Wed, 12 Jun 2019 05:15:47 +
Matan Azrad wrote:
> From: Stephen Hemminger
> > > Hi Stephen
> > >
> > > From: Stephen Hemminger
> > > > When using DPDK on Azure it is common to have one non-DPDK
> > interface.
> > > > If that non-DPDK interface is present vdev_netvsc correctly skip i
From: Stephen Hemminger
> > Hi Stephen
> >
> > From: Stephen Hemminger
> > > When using DPDK on Azure it is common to have one non-DPDK
> interface.
> > > If that non-DPDK interface is present vdev_netvsc correctly skip it.
> > > But if the non-DPDK has accelerated networking the Mellanox driv
On Tue, 11 Jun 2019 06:21:21 +
Matan Azrad wrote:
> Hi Stephen
>
> From: Stephen Hemminger
> > When using DPDK on Azure it is common to have one non-DPDK interface.
> > If that non-DPDK interface is present vdev_netvsc correctly skip it.
> > But if the non-DPDK has accelerated networking the
Hi Stephen
From: Stephen Hemminger
> When using DPDK on Azure it is common to have one non-DPDK interface.
> If that non-DPDK interface is present vdev_netvsc correctly skip it.
> But if the non-DPDK has accelerated networking the Mellanox driver will still
> get associated with DPDK (and break co
When using DPDK on Azure it is common to have one non-DPDK interface.
If that non-DPDK interface is present vdev_netvsc correctly skip it.
But if the non-DPDK has accelerated networking the Mellanox driver will
still get associated with DPDK (and break connectivity).
The current process is to tell
6 matches
Mail list logo
