search for: vdev_netvsc

...on't like the application. >> > >> > Could you please explain how is the proposed patchset breaking >> > userspace? 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 >> V...

...on't like the application. >> > >> > Could you please explain how is the proposed patchset breaking >> > userspace? 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 >> V...

...gt; > You can't go breaking userspace even if you don't like the application. > > Could you please explain how is the proposed patchset breaking > userspace? 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...

...gt; > You can't go breaking userspace even if you don't like the application. > > Could you please explain how is the proposed patchset breaking > userspace? 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...

...; > Could you please explain how is the proposed patchset breaking > > >> > userspace? 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 w...

...>> > Could you please explain how is the proposed patchset breaking >> >> > userspace? 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...

...>> > Could you please explain how is the proposed patchset breaking >> >> > userspace? 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...

...userspace even if you don't like the application. > > > > Could you please explain how is the proposed patchset breaking > > userspace? 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. >...

...gt;> > > >> > Could you please explain how is the proposed patchset breaking > >> > userspace? 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 Mell...

...>> > > >> > Could you please explain how is the proposed patchset breaking > >> > userspace? 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 Mell...

...lease explain how is the proposed patchset breaking > >> >> > userspace? 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...

...the proposed patchset breaking >> >> >> > userspace? 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...

...the proposed patchset breaking >> >> >> > userspace? 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...

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