search for: iff_bypass_slave

Displaying 20 results from an estimated 20 matches for "iff_bypass_slave".

2018 Apr 18
2
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...@ -1430,6 +1430,8 @@ enum netdev_priv_flags { >> > > > IFF_PHONY_HEADROOM = 1<<24, >> > > > IFF_MACSEC = 1<<25, >> > > > IFF_NO_RX_HANDLER = 1<<26, >> > > > + IFF_BYPASS = 1 << 27, >> > > > + IFF_BYPASS_SLAVE = 1 << 28, >> > > I wonder, why you don't follow the existing coding style... Also, please >> > > add these to into the comment above. >> > To avoid checkpatch warnings. If it is OK to ignore these warnings, I can switch back >> > to the existing...
2018 Apr 18
2
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...@ -1430,6 +1430,8 @@ enum netdev_priv_flags { >> > > > IFF_PHONY_HEADROOM = 1<<24, >> > > > IFF_MACSEC = 1<<25, >> > > > IFF_NO_RX_HANDLER = 1<<26, >> > > > + IFF_BYPASS = 1 << 27, >> > > > + IFF_BYPASS_SLAVE = 1 << 28, >> > > I wonder, why you don't follow the existing coding style... Also, please >> > > add these to into the comment above. >> > To avoid checkpatch warnings. If it is OK to ignore these warnings, I can switch back >> > to the existing...
2018 Apr 18
0
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...inux/netdevice.h >>>> @@ -1430,6 +1430,8 @@ enum netdev_priv_flags { >>>> IFF_PHONY_HEADROOM = 1<<24, >>>> IFF_MACSEC = 1<<25, >>>> IFF_NO_RX_HANDLER = 1<<26, >>>> + IFF_BYPASS = 1 << 27, >>>> + IFF_BYPASS_SLAVE = 1 << 28, >>> I wonder, why you don't follow the existing coding style... Also, please >>> add these to into the comment above. >> To avoid checkpatch warnings. If it is OK to ignore these warnings, I can switch back >> to the existing coding style to be co...
2018 Apr 18
2
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...t; +++ b/include/linux/netdevice.h >> > @@ -1430,6 +1430,8 @@ enum netdev_priv_flags { >> > IFF_PHONY_HEADROOM = 1<<24, >> > IFF_MACSEC = 1<<25, >> > IFF_NO_RX_HANDLER = 1<<26, >> > + IFF_BYPASS = 1 << 27, >> > + IFF_BYPASS_SLAVE = 1 << 28, >> I wonder, why you don't follow the existing coding style... Also, please >> add these to into the comment above. > >To avoid checkpatch warnings. If it is OK to ignore these warnings, I can switch back >to the existing coding style to be consistent. Pl...
2018 Apr 18
2
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...t; +++ b/include/linux/netdevice.h >> > @@ -1430,6 +1430,8 @@ enum netdev_priv_flags { >> > IFF_PHONY_HEADROOM = 1<<24, >> > IFF_MACSEC = 1<<25, >> > IFF_NO_RX_HANDLER = 1<<26, >> > + IFF_BYPASS = 1 << 27, >> > + IFF_BYPASS_SLAVE = 1 << 28, >> I wonder, why you don't follow the existing coding style... Also, please >> add these to into the comment above. > >To avoid checkpatch warnings. If it is OK to ignore these warnings, I can switch back >to the existing coding style to be consistent. Pl...
2018 Apr 18
0
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...netdev_priv_flags { > >> > > > IFF_PHONY_HEADROOM = 1<<24, > >> > > > IFF_MACSEC = 1<<25, > >> > > > IFF_NO_RX_HANDLER = 1<<26, > >> > > > + IFF_BYPASS = 1 << 27, > >> > > > + IFF_BYPASS_SLAVE = 1 << 28, > >> > > I wonder, why you don't follow the existing coding style... Also, please > >> > > add these to into the comment above. > >> > To avoid checkpatch warnings. If it is OK to ignore these warnings, I can switch back > >>...
2018 Apr 11
2
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...587293728f70 100644 >--- a/include/linux/netdevice.h >+++ b/include/linux/netdevice.h >@@ -1430,6 +1430,8 @@ enum netdev_priv_flags { > IFF_PHONY_HEADROOM = 1<<24, > IFF_MACSEC = 1<<25, > IFF_NO_RX_HANDLER = 1<<26, >+ IFF_BYPASS = 1 << 27, >+ IFF_BYPASS_SLAVE = 1 << 28, I wonder, why you don't follow the existing coding style... Also, please add these to into the comment above. > }; > > #define IFF_802_1Q_VLAN IFF_802_1Q_VLAN >@@ -1458,6 +1460,8 @@ enum netdev_priv_flags { > #define IFF_RXFH_CONFIGURED IFF_RXFH_CONFIGURE...
2018 Apr 11
2
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...587293728f70 100644 >--- a/include/linux/netdevice.h >+++ b/include/linux/netdevice.h >@@ -1430,6 +1430,8 @@ enum netdev_priv_flags { > IFF_PHONY_HEADROOM = 1<<24, > IFF_MACSEC = 1<<25, > IFF_NO_RX_HANDLER = 1<<26, >+ IFF_BYPASS = 1 << 27, >+ IFF_BYPASS_SLAVE = 1 << 28, I wonder, why you don't follow the existing coding style... Also, please add these to into the comment above. > }; > > #define IFF_802_1Q_VLAN IFF_802_1Q_VLAN >@@ -1458,6 +1460,8 @@ enum netdev_priv_flags { > #define IFF_RXFH_CONFIGURED IFF_RXFH_CONFIGURE...
2018 Apr 10
0
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...netdevice.h index cf44503ea81a..587293728f70 100644 --- a/include/linux/netdevice.h +++ b/include/linux/netdevice.h @@ -1430,6 +1430,8 @@ enum netdev_priv_flags { IFF_PHONY_HEADROOM = 1<<24, IFF_MACSEC = 1<<25, IFF_NO_RX_HANDLER = 1<<26, + IFF_BYPASS = 1 << 27, + IFF_BYPASS_SLAVE = 1 << 28, }; #define IFF_802_1Q_VLAN IFF_802_1Q_VLAN @@ -1458,6 +1460,8 @@ enum netdev_priv_flags { #define IFF_RXFH_CONFIGURED IFF_RXFH_CONFIGURED #define IFF_MACSEC IFF_MACSEC #define IFF_NO_RX_HANDLER IFF_NO_RX_HANDLER +#define IFF_BYPASS IFF_BYPASS +#define IFF_BYPASS_SLA...
2018 Apr 11
0
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...clude/linux/netdevice.h >> +++ b/include/linux/netdevice.h >> @@ -1430,6 +1430,8 @@ enum netdev_priv_flags { >> IFF_PHONY_HEADROOM = 1<<24, >> IFF_MACSEC = 1<<25, >> IFF_NO_RX_HANDLER = 1<<26, >> + IFF_BYPASS = 1 << 27, >> + IFF_BYPASS_SLAVE = 1 << 28, > I wonder, why you don't follow the existing coding style... Also, please > add these to into the comment above. To avoid checkpatch warnings. If it is OK to ignore these warnings, I can switch back to the existing coding style to be consistent. > > >> };...
2018 Apr 18
4
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...>> >> > > > IFF_PHONY_HEADROOM = 1<<24, >> >> > > > IFF_MACSEC = 1<<25, >> >> > > > IFF_NO_RX_HANDLER = 1<<26, >> >> > > > + IFF_BYPASS = 1 << 27, >> >> > > > + IFF_BYPASS_SLAVE = 1 << 28, >> >> > > I wonder, why you don't follow the existing coding style... Also, please >> >> > > add these to into the comment above. >> >> > To avoid checkpatch warnings. If it is OK to ignore these warnings, I can switch back &g...
2018 Apr 18
4
[RFC PATCH net-next v6 2/4] net: Introduce generic bypass module
...>> >> > > > IFF_PHONY_HEADROOM = 1<<24, >> >> > > > IFF_MACSEC = 1<<25, >> >> > > > IFF_NO_RX_HANDLER = 1<<26, >> >> > > > + IFF_BYPASS = 1 << 27, >> >> > > > + IFF_BYPASS_SLAVE = 1 << 28, >> >> > > I wonder, why you don't follow the existing coding style... Also, please >> >> > > add these to into the comment above. >> >> > To avoid checkpatch warnings. If it is OK to ignore these warnings, I can switch back &g...
2018 Apr 10
6
[RFC PATCH net-next v6 0/4] Enable virtio_net to act as a backup for a passthru device
...ps://marc.info/?l=linux-virtualization&m=151189725224231&w=2 v6 RFC: Simplified virtio_net changes by moving all the ndo_ops of the bypass_netdev and create/destroy of bypass_netdev to 'bypass' module. avoided 2 phase registration(driver + instances). introduced IFF_BYPASS/IFF_BYPASS_SLAVE dev->priv_flags replaced mutex with a spinlock v5 RFC: Based on Jiri's comments, moved the common functionality to a 'bypass' module so that the same notifier and event handlers to handle child register/unregister/link change events can be shared between virtio_net and ne...
2018 Apr 06
1
[RFC PATCH net-next v5 2/4] net: Introduce generic bypass module
...err = %d)\n", >+ bypass_netdev->name, ret); >+ goto upper_link_failed; >+ } >+ >+ child_netdev->flags |= IFF_SLAVE; Don't reuse IFF_SLAVE. That is bonding-specific thing. I know that netvsc uses it, it is wrong. Please rather introduce: IFF_BYPASS for master and IFF_BYPASS_SLAVE for slaves. >+ >+ if (netif_running(bypass_netdev)) { >+ ret = dev_open(child_netdev); >+ if (ret && (ret != -EBUSY)) { >+ netdev_err(bypass_netdev, >+ "Opening child %s failed ret:%d\n", >+ child_netdev->name, ret); >+ goto err_int...
2018 May 24
11
[PATCH net-next v12 0/5] Enable virtio_net to act as a standby for a passthru device
...on VF if it is registered as primary. (stephen) - minor bugfixes v6 RFC: Simplified virtio_net changes by moving all the ndo_ops of the bypass_netdev and create/destroy of bypass_netdev to 'bypass' module. avoided 2 phase registration(driver + instances). introduced IFF_BYPASS/IFF_BYPASS_SLAVE dev->priv_flags replaced mutex with a spinlock v5 RFC: Based on Jiri's comments, moved the common functionality to a 'bypass' module so that the same notifier and event handlers to handle child register/unregister/link change events can be shared between virtio_net and ne...
2018 Apr 25
5
[PATCH net-next v8 0/4] Enable virtio_net to act as a standby for a passthru device
...on VF if it is registered as primary. (stephen) - minor bugfixes v6 RFC: Simplified virtio_net changes by moving all the ndo_ops of the bypass_netdev and create/destroy of bypass_netdev to 'bypass' module. avoided 2 phase registration(driver + instances). introduced IFF_BYPASS/IFF_BYPASS_SLAVE dev->priv_flags replaced mutex with a spinlock v5 RFC: Based on Jiri's comments, moved the common functionality to a 'bypass' module so that the same notifier and event handlers to handle child register/unregister/link change events can be shared between virtio_net and ne...
2018 May 07
9
[PATCH net-next v10 0/4] Enable virtio_net to act as a standby for a passthru device
...on VF if it is registered as primary. (stephen) - minor bugfixes v6 RFC: Simplified virtio_net changes by moving all the ndo_ops of the bypass_netdev and create/destroy of bypass_netdev to 'bypass' module. avoided 2 phase registration(driver + instances). introduced IFF_BYPASS/IFF_BYPASS_SLAVE dev->priv_flags replaced mutex with a spinlock v5 RFC: Based on Jiri's comments, moved the common functionality to a 'bypass' module so that the same notifier and event handlers to handle child register/unregister/link change events can be shared between virtio_net and ne...
2018 May 22
7
[PATCH net-next v11 0/5] Enable virtio_net to act as a standby for a passthru device
...on VF if it is registered as primary. (stephen) - minor bugfixes v6 RFC: Simplified virtio_net changes by moving all the ndo_ops of the bypass_netdev and create/destroy of bypass_netdev to 'bypass' module. avoided 2 phase registration(driver + instances). introduced IFF_BYPASS/IFF_BYPASS_SLAVE dev->priv_flags replaced mutex with a spinlock v5 RFC: Based on Jiri's comments, moved the common functionality to a 'bypass' module so that the same notifier and event handlers to handle child register/unregister/link change events can be shared between virtio_net and ne...
2018 Apr 05
6
[RFC PATCH net-next v5 0/4] Enable virtio_net to act as a backup 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_BACKUP that can be used
2018 Apr 20
13
[PATCH net-next v7 0/4] Enable virtio_net to act as a standby for a passthru device
...on VF if it is registered as primary. (stephen) - minor bugfixes v6 RFC: Simplified virtio_net changes by moving all the ndo_ops of the bypass_netdev and create/destroy of bypass_netdev to 'bypass' module. avoided 2 phase registration(driver + instances). introduced IFF_BYPASS/IFF_BYPASS_SLAVE dev->priv_flags replaced mutex with a spinlock v5 RFC: Based on Jiri's comments, moved the common functionality to a 'bypass' module so that the same notifier and event handlers to handle child register/unregister/link change events can be shared between virtio_net and ne...