search for: netdev_lag_tx_type_activebackup

...ilover rx handler (err = %d)\n", >>+ err); >>+ goto err_handler_register; >>+ } >>+ >>+ err = netdev_upper_dev_link(slave_dev, failover_dev, NULL); > >Please use netdev_master_upper_dev_link(). Don't forget to fillup struct netdev_lag_upper_info - NETDEV_LAG_TX_TYPE_ACTIVEBACKUP Also, please call netdev_lower_state_changed() when the active slave device changes from primary->backup of backup->primary and whenever link state of a slave changes [...]

...ilover rx handler (err = %d)\n", >>+ err); >>+ goto err_handler_register; >>+ } >>+ >>+ err = netdev_upper_dev_link(slave_dev, failover_dev, NULL); > >Please use netdev_master_upper_dev_link(). Don't forget to fillup struct netdev_lag_upper_info - NETDEV_LAG_TX_TYPE_ACTIVEBACKUP Also, please call netdev_lower_state_changed() when the active slave device changes from primary->backup of backup->primary and whenever link state of a slave changes [...]

...> > > + goto err_handler_register; > > > > + } > > > > + > > > > + err = netdev_upper_dev_link(slave_dev, failover_dev, NULL); > > > Please use netdev_master_upper_dev_link(). > > Don't forget to fillup struct netdev_lag_upper_info - NETDEV_LAG_TX_TYPE_ACTIVEBACKUP > > > > > > Also, please call netdev_lower_state_changed() when the active slave > > device changes from primary->backup of backup->primary and whenever link > > state of a slave changes > > > Sure. will look into it.? Do you think this will help with...

...n", >>> + err); >>> + goto err_handler_register; >>> + } >>> + >>> + err = netdev_upper_dev_link(slave_dev, failover_dev, NULL); >> Please use netdev_master_upper_dev_link(). > Don't forget to fillup struct netdev_lag_upper_info - NETDEV_LAG_TX_TYPE_ACTIVEBACKUP > > > Also, please call netdev_lower_state_changed() when the active slave > device changes from primary->backup of backup->primary and whenever link > state of a slave changes > Sure. will look into it.? Do you think this will help with the issue you saw with having to chan...

...slave_dev, failover_dev)) + goto done; + + err = netdev_rx_handler_register(slave_dev, fops->slave_handle_frame, + failover_dev); + if (err) { + netdev_err(slave_dev, "can not register failover rx handler (err = %d)\n", + err); + goto done; + } + + lag_upper_info.tx_type = NETDEV_LAG_TX_TYPE_ACTIVEBACKUP; + err = netdev_master_upper_dev_link(slave_dev, failover_dev, NULL, + &lag_upper_info, NULL); + if (err) { + netdev_err(slave_dev, "can not set failover device %s (err = %d)\n", + failover_dev->name, err); + goto err_upper_link; + } + + slave_dev->priv_flags |= IF...

...+ goto err_vlan_add; + } + + err = netdev_rx_handler_register(slave_dev, net_failover_handle_frame, + failover_dev); + if (err) { + netdev_err(slave_dev, "can not register failover rx handler (err = %d)\n", + err); + goto err_handler_register; + } + + lag_upper_info.tx_type = NETDEV_LAG_TX_TYPE_ACTIVEBACKUP; + err = netdev_master_upper_dev_link(slave_dev, failover_dev, NULL, + &lag_upper_info, NULL); + if (err) { + netdev_err(slave_dev, "can not set failover device %s (err = %d)\n", + failover_dev->name, err); + goto err_upper_link; + } + + slave_dev->priv_flags |= IF...

...+ goto err_vlan_add; + } + + err = netdev_rx_handler_register(slave_dev, net_failover_handle_frame, + failover_dev); + if (err) { + netdev_err(slave_dev, "can not register failover rx handler (err = %d)\n", + err); + goto err_handler_register; + } + + lag_upper_info.tx_type = NETDEV_LAG_TX_TYPE_ACTIVEBACKUP; + err = netdev_master_upper_dev_link(slave_dev, failover_dev, NULL, + &lag_upper_info, NULL); + if (err) { + netdev_err(slave_dev, "can not set failover device %s (err = %d)\n", + failover_dev->name, err); + goto err_upper_link; + } + + slave_dev->priv_flags |= IF...

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

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 failover module that provides a generic interface for

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 failover module that provides a generic interface for