search for: _bkup

...sys" -> "/export/home/vnmrsys": File exists unexpected tag 91 rsync error: error in rsync protocol data stream (code 12) at io.c(298) 2. rsync -azSH --stats --delete-after --safe-links --exclude "SunWS_cache/" --exclude ".sb/" /export/home remote:/export/home/_bkup unexpected tag -55 rsync error: error in rsync protocol data stream (code 12) at io.c(298) where do I find out what these tags mean? I also get this occasionally mkstemp failed: File name too long 42776 100% 13.60MB/s 0:00:00 mkstemp failed: File name too long 13556 100% 12....

...> virtio_net netdev will get the backup name. >> What do you mean by "name"? > >bypass_netdev also is associated with the same pci device as the original virtio_net >netdev via SET_NETDEV_DEV().? Also, we added ndo_get_phys_port_name() to virtio_net >that will return _bkup when BACKUP feature is enabled. Okay. > >So for ex: if virtio_net inteface was getting 'ens12' as the name assigned by udev >without BACKUP feature,? when BACKUP feature is enabled,? the? bypass_netdev will be >named 'ens12' and the original virtio_net will get named a...

...> virtio_net netdev will get the backup name. >> What do you mean by "name"? > >bypass_netdev also is associated with the same pci device as the original virtio_net >netdev via SET_NETDEV_DEV().? Also, we added ndo_get_phys_port_name() to virtio_net >that will return _bkup when BACKUP feature is enabled. Okay. > >So for ex: if virtio_net inteface was getting 'ens12' as the name assigned by udev >without BACKUP feature,? when BACKUP feature is enabled,? the? bypass_netdev will be >named 'ens12' and the original virtio_net will get named a...

Tue, Apr 10, 2018 at 05:59:02PM CEST, sridhar.samudrala at intel.com wrote: >On 4/10/2018 8:43 AM, Jiri Pirko wrote: >> Tue, Apr 10, 2018 at 05:27:48PM CEST, sridhar.samudrala at intel.com wrote: >> > On 4/10/2018 8:22 AM, Jiri Pirko wrote: >> > > Tue, Apr 10, 2018 at 05:13:40PM CEST, sridhar.samudrala at intel.com wrote: >> > > > On 4/10/2018 3:55 AM,

Tue, Apr 10, 2018 at 05:59:02PM CEST, sridhar.samudrala at intel.com wrote: >On 4/10/2018 8:43 AM, Jiri Pirko wrote: >> Tue, Apr 10, 2018 at 05:27:48PM CEST, sridhar.samudrala at intel.com wrote: >> > On 4/10/2018 8:22 AM, Jiri Pirko wrote: >> > > Tue, Apr 10, 2018 at 05:13:40PM CEST, sridhar.samudrala at intel.com wrote: >> > > > On 4/10/2018 3:55 AM,

...;> netdev and >> virtio_net netdev will get the backup name. > What do you mean by "name"? bypass_netdev also is associated with the same pci device as the original virtio_net netdev via SET_NETDEV_DEV().? Also, we added ndo_get_phys_port_name() to virtio_net that will return _bkup when BACKUP feature is enabled. So for ex: if virtio_net inteface was getting 'ens12' as the name assigned by udev without BACKUP feature,? when BACKUP feature is enabled,? the? bypass_netdev will be named 'ens12' and the original virtio_net will get named as ens12n_bkup. > &g...

...ill get the backup name. > >> What do you mean by "name"? > > > >bypass_netdev also is associated with the same pci device as the original virtio_net > >netdev via SET_NETDEV_DEV().? Also, we added ndo_get_phys_port_name() to virtio_net > >that will return _bkup when BACKUP feature is enabled. > > Okay. > > > > >So for ex: if virtio_net inteface was getting 'ens12' as the name assigned by udev > >without BACKUP feature,? when BACKUP feature is enabled,? the? bypass_netdev will be > >named 'ens12' and the o...

...ev_bpf *xdp) } } +static int virtnet_get_phys_port_name(struct net_device *dev, char *buf, + size_t len) +{ + struct virtnet_info *vi = netdev_priv(dev); + int ret; + + if (!virtio_has_feature(vi->vdev, VIRTIO_NET_F_BACKUP)) + return -EOPNOTSUPP; + + ret = snprintf(buf, len, "_bkup"); + if (ret >= len) + return -EOPNOTSUPP; + + return 0; +} + static const struct net_device_ops virtnet_netdev = { .ndo_open = virtnet_open, .ndo_stop = virtnet_close, @@ -2292,6 +2314,7 @@ static const struct net_device_ops virtnet_netdev = { .ndo_xdp_xmit = vi...

...rtnet_get_phys_port_name(struct net_device *dev, char *buf, >+ size_t len) >+{ >+ struct virtnet_info *vi = netdev_priv(dev); >+ int ret; >+ >+ if (!virtio_has_feature(vi->vdev, VIRTIO_NET_F_BACKUP)) >+ return -EOPNOTSUPP; >+ >+ ret = snprintf(buf, len, "_bkup"); >+ if (ret >= len) >+ return -EOPNOTSUPP; >+ >+ return 0; >+} >+ > static const struct net_device_ops virtnet_netdev = { > .ndo_open = virtnet_open, > .ndo_stop = virtnet_close, >@@ -2292,6 +2314,7 @@ static const struct net_device_ops...

...rtnet_get_phys_port_name(struct net_device *dev, char *buf, >+ size_t len) >+{ >+ struct virtnet_info *vi = netdev_priv(dev); >+ int ret; >+ >+ if (!virtio_has_feature(vi->vdev, VIRTIO_NET_F_BACKUP)) >+ return -EOPNOTSUPP; >+ >+ ret = snprintf(buf, len, "_bkup"); >+ if (ret >= len) >+ return -EOPNOTSUPP; >+ >+ return 0; >+} >+ > static const struct net_device_ops virtnet_netdev = { > .ndo_open = virtnet_open, > .ndo_stop = virtnet_close, >@@ -2292,6 +2314,7 @@ static const struct net_device_ops...

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_BACKUP 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 new feature bit VIRTIO_NET_F_BACKUP that can be used