search for: nfo_op

Displaying 7 results from an estimated 7 matches for "nfo_op".

Did you mean: nfo_ops
2018 May 07
0
[PATCH net-next v10 2/4] net: Introduce generic failover module
...can be a + * standby or a primary netdev. + * + */ +static int net_failover_slave_register(struct net_device *slave_dev) +{ + struct net_device *standby_dev, *primary_dev, *failover_dev; + struct netdev_lag_upper_info lag_upper_info; + struct net_failover_info *nfo_info; + struct net_failover_ops *nfo_ops; + bool slave_is_standby; + u32 orig_mtu; + int err; + + ASSERT_RTNL(); + + failover_dev = net_failover_get_bymac(slave_dev->perm_addr, &nfo_ops); + if (!failover_dev) + goto done; + + if (failover_dev->type != slave_dev->type) + goto done; + + if (nfo_ops && nfo_ops->sla...
2018 May 07
1
[PATCH net-next v10 2/4] net: Introduce generic failover module
On Mon, 7 May 2018 15:10:44 -0700 Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > + if (netif_running(failover_dev)) { > + err = dev_open(slave_dev); > + if (err && (err != -EBUSY)) { > + netdev_err(failover_dev, "Opening slave %s failed err:%d\n", > + slave_dev->name, err); > + goto err_dev_open; > + } > + } > + >
2018 Apr 25
5
[PATCH net-next v8 0/4] Enable virtio_net to act as a standby for a passthru device
This is another update based on feedback from MST and Stephen on the last patchset. Hopefully this series can be integrated and any further enhancements can be made on top of this patchset. v8: - Made the failover managment routines more robust by updating the feature bits/other fields in the failover netdev when slave netdevs are registered/unregistered. (mst) - added support for handling
2018 May 07
9
[PATCH net-next v10 0/4] Enable virtio_net to act as a standby for a passthru device
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
2018 May 07
2
[PATCH net-next v10 2/4] net: Introduce generic failover module
On Mon, 7 May 2018 15:10:44 -0700 Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > +static struct net_device *net_failover_get_bymac(u8 *mac, > + struct net_failover_ops **ops) > +{ > + struct net_device *failover_dev; > + struct net_failover *failover; > + > + spin_lock(&net_failover_lock); > + list_for_each_entry(failover,
2018 May 07
2
[PATCH net-next v10 2/4] net: Introduce generic failover module
On Mon, 7 May 2018 15:10:44 -0700 Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > +static struct net_device *net_failover_get_bymac(u8 *mac, > + struct net_failover_ops **ops) > +{ > + struct net_device *failover_dev; > + struct net_failover *failover; > + > + spin_lock(&net_failover_lock); > + list_for_each_entry(failover,
2018 May 08
0
[PATCH net-next v10 2/4] net: Introduce generic failover module
...>> + return NULL; >> +} > This is broken if non-ethernet devices such as Infiniband are present. There is check to make sure that a slave and failover devices are of the same type in net_failover_slave_register() failover_dev = net_failover_get_bymac(slave_dev->perm_addr, &nfo_ops); ??????? if (!failover_dev) ??????????????? goto done; ??????? if (failover_dev->type != slave_dev->type) ??????????????? goto done; Do you think this is not good enough? I had an explicit check for ARPHRD_ETHER in earlier patchsets, but removed it based on Jiri's comment.