search for: bondingish

...nges the userspace >> > API at all. >> > >> >> The DPDK has a device driver vdev_netvsc which scans the Linux network devices >> to look for Linux netvsc device and the paired VF device and setup the >> DPDK environment. This setup creates a DPDK failsafe (bondingish) instance >> and sets up TAP support over the Linux netvsc device as well as the Mellanox >> VF device. >> >> So it depends on existing 2 device model. You can't go to a 3 device model >> or start hiding devices from userspace. > > Okay so how does the existi...

...nges the userspace >> > API at all. >> > >> >> The DPDK has a device driver vdev_netvsc which scans the Linux network devices >> to look for Linux netvsc device and the paired VF device and setup the >> DPDK environment. This setup creates a DPDK failsafe (bondingish) instance >> and sets up TAP support over the Linux netvsc device as well as the Mellanox >> VF device. >> >> So it depends on existing 2 device model. You can't go to a 3 device model >> or start hiding devices from userspace. > > Okay so how does the existi...

...ace? Ignoring DPDK for now, I don't think it changes the userspace > API at all. > The DPDK has a device driver vdev_netvsc which scans the Linux network devices to look for Linux netvsc device and the paired VF device and setup the DPDK environment. This setup creates a DPDK failsafe (bondingish) instance and sets up TAP support over the Linux netvsc device as well as the Mellanox VF device. So it depends on existing 2 device model. You can't go to a 3 device model or start hiding devices from userspace. Also, I am working on associating netvsc and VF device based on serial number ra...

...ace? Ignoring DPDK for now, I don't think it changes the userspace > API at all. > The DPDK has a device driver vdev_netvsc which scans the Linux network devices to look for Linux netvsc device and the paired VF device and setup the DPDK environment. This setup creates a DPDK failsafe (bondingish) instance and sets up TAP support over the Linux netvsc device as well as the Mellanox VF device. So it depends on existing 2 device model. You can't go to a 3 device model or start hiding devices from userspace. Also, I am working on associating netvsc and VF device based on serial number ra...

...t; >> > > > >> > > >> The DPDK has a device driver vdev_netvsc which scans the Linux network devices > > >> to look for Linux netvsc device and the paired VF device and setup the > > >> DPDK environment. This setup creates a DPDK failsafe (bondingish) instance > > >> and sets up TAP support over the Linux netvsc device as well as the Mellanox > > >> VF device. > > >> > > >> So it depends on existing 2 device model. You can't go to a 3 device model > > >> or start hiding devices fro...

...>> >> > >> >> >> >> The DPDK has a device driver vdev_netvsc which scans the Linux network devices >> >> to look for Linux netvsc device and the paired VF device and setup the >> >> DPDK environment. This setup creates a DPDK failsafe (bondingish) instance >> >> and sets up TAP support over the Linux netvsc device as well as the Mellanox >> >> VF device. >> >> >> >> So it depends on existing 2 device model. You can't go to a 3 device model >> >> or start hiding devices from use...

...>> >> > >> >> >> >> The DPDK has a device driver vdev_netvsc which scans the Linux network devices >> >> to look for Linux netvsc device and the paired VF device and setup the >> >> DPDK environment. This setup creates a DPDK failsafe (bondingish) instance >> >> and sets up TAP support over the Linux netvsc device as well as the Mellanox >> >> VF device. >> >> >> >> So it depends on existing 2 device model. You can't go to a 3 device model >> >> or start hiding devices from use...

...don't think it changes the userspace > > API at all. > > > > The DPDK has a device driver vdev_netvsc which scans the Linux network devices > to look for Linux netvsc device and the paired VF device and setup the > DPDK environment. This setup creates a DPDK failsafe (bondingish) instance > and sets up TAP support over the Linux netvsc device as well as the Mellanox > VF device. > > So it depends on existing 2 device model. You can't go to a 3 device model > or start hiding devices from userspace. Okay so how does the existing patch break that? IIUC do...

...> API at all. > >> > > >> > >> The DPDK has a device driver vdev_netvsc which scans the Linux network devices > >> to look for Linux netvsc device and the paired VF device and setup the > >> DPDK environment. This setup creates a DPDK failsafe (bondingish) instance > >> and sets up TAP support over the Linux netvsc device as well as the Mellanox > >> VF device. > >> > >> So it depends on existing 2 device model. You can't go to a 3 device model > >> or start hiding devices from userspace. > >...

...t; > API at all. > >> > > >> > >> The DPDK has a device driver vdev_netvsc which scans the Linux network devices > >> to look for Linux netvsc device and the paired VF device and setup the > >> DPDK environment. This setup creates a DPDK failsafe (bondingish) instance > >> and sets up TAP support over the Linux netvsc device as well as the Mellanox > >> VF device. > >> > >> So it depends on existing 2 device model. You can't go to a 3 device model > >> or start hiding devices from userspace. > > &g...

...t; > >> >> > >> >> The DPDK has a device driver vdev_netvsc which scans the Linux network devices > >> >> to look for Linux netvsc device and the paired VF device and setup the > >> >> DPDK environment. This setup creates a DPDK failsafe (bondingish) instance > >> >> and sets up TAP support over the Linux netvsc device as well as the Mellanox > >> >> VF device. > >> >> > >> >> So it depends on existing 2 device model. You can't go to a 3 device model > >> >> or star...

...> >> >> >> >> The DPDK has a device driver vdev_netvsc which scans the Linux network devices >> >> >> to look for Linux netvsc device and the paired VF device and setup the >> >> >> DPDK environment. This setup creates a DPDK failsafe (bondingish) instance >> >> >> and sets up TAP support over the Linux netvsc device as well as the Mellanox >> >> >> VF device. >> >> >> >> >> >> So it depends on existing 2 device model. You can't go to a 3 device model >> >&...

...> >> >> >> >> The DPDK has a device driver vdev_netvsc which scans the Linux network devices >> >> >> to look for Linux netvsc device and the paired VF device and setup the >> >> >> DPDK environment. This setup creates a DPDK failsafe (bondingish) instance >> >> >> and sets up TAP support over the Linux netvsc device as well as the Mellanox >> >> >> VF device. >> >> >> >> >> >> So it depends on existing 2 device model. You can't go to a 3 device model >> >&...

On Fri, 20 Apr 2018 18:00:58 +0200 Jiri Pirko <jiri at resnulli.us> wrote: > Fri, Apr 20, 2018 at 05:28:02PM CEST, stephen at networkplumber.org wrote: > >On Thu, 19 Apr 2018 18:42:04 -0700 > >Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > > > >> Use the registration/notification framework supported by the generic > >> failover

On Fri, 20 Apr 2018 18:00:58 +0200 Jiri Pirko <jiri at resnulli.us> wrote: > Fri, Apr 20, 2018 at 05:28:02PM CEST, stephen at networkplumber.org wrote: > >On Thu, 19 Apr 2018 18:42:04 -0700 > >Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > > > >> Use the registration/notification framework supported by the generic > >> failover