search for: failover_destroy

...00, Sridhar Samudrala wrote: > +#if IS_ENABLED(CONFIG_NET_FAILOVER) > + > +int failover_create(struct net_device *standby_dev, > + struct failover **pfailover); Should we rename all these structs net_failover? It's possible to extend the concept to storage I think. > +void failover_destroy(struct failover *failover); > + > +int failover_register(struct net_device *standby_dev, struct failover_ops *ops, > + struct failover **pfailover); > +void failover_unregister(struct failover *failover); > + > +int failover_slave_unregister(struct net_device *slave_dev); &...

..._debug("virtio_net: registering device failed\n"); - goto free_vqs; + goto free_failover; } virtio_device_ready(vdev); @@ -2879,6 +2908,8 @@ static int virtnet_probe(struct virtio_device *vdev) vi->vdev->config->reset(vdev); unregister_netdev(dev); +free_failover: + failover_destroy(vi->failover); free_vqs: cancel_delayed_work_sync(&vi->refill); free_receive_page_frags(vi); @@ -2913,6 +2944,8 @@ static void virtnet_remove(struct virtio_device *vdev) unregister_netdev(vi->dev); + failover_destroy(vi->failover); + remove_vq_common(vi); free_netde...

...ster() > failover_unregister() > 2. new virtio_net based solution that uses 3 netdev model. In this model, > the failover module provides interfaces to create/destroy additional master > netdev and all the slave events are managed internally. > failover_create() > failover_destroy() > These functions call failover_register()/failover_unregister() with the > master netdev created by the failover module. > > Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> I like this patch. Yes something to improve (see below) > --- > include/linux...

...ster() > failover_unregister() > 2. new virtio_net based solution that uses 3 netdev model. In this model, > the failover module provides interfaces to create/destroy additional master > netdev and all the slave events are managed internally. > failover_create() > failover_destroy() > These functions call failover_register()/failover_unregister() with the > master netdev created by the failover module. > > Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> I like this patch. Yes something to improve (see below) > --- > include/linux...

...ave events. failover_register() failover_unregister() 2. new virtio_net based solution that uses 3 netdev model. In this model, the failover module provides interfaces to create/destroy additional master netdev and all the slave events are managed internally. failover_create() failover_destroy() These functions call failover_register()/failover_unregister() with the master netdev created by the failover module. Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> --- include/linux/netdevice.h | 16 + include/net/failover.h | 96 ++++++ net/Kconfig...

The main motivation for this patch is to enable cloud service providers to provide an accelerated datapath to virtio-net enabled VMs in a transparent manner with no/minimal guest userspace changes. This also enables hypervisor controlled live migration to be supported with VMs that have direct attached SR-IOV VF devices. Patch 1 introduces a new feature bit VIRTIO_NET_F_STANDBY that can be used

...ver_unregister() >> 2. new virtio_net based solution that uses 3 netdev model. In this model, >> the failover module provides interfaces to create/destroy additional master >> netdev and all the slave events are managed internally. >> failover_create() >> failover_destroy() >> These functions call failover_register()/failover_unregister() with the >> master netdev created by the failover module. >> >> Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> > I like this patch. Yes something to improve (see below) > >&...