search for: iff_l3mdev_slave

Displaying 6 results from an estimated 6 matches for "iff_l3mdev_slave".

2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...IFF_EBRIDGE = 1<<1, > IFF_BRIDGE_PORT = 1<<9, > IFF_OPENVSWITCH = 1<<20, > IFF_OVS_DATAPATH = 1<<10, > IFF_L3MDEV_MASTER = 1<<18, > IFF_L3MDEV_SLAVE = 1<<21, > IFF_TEAM = 1<<22, > IFF_TEAM_PORT = 1<<13, > }; That's not in uapi, is it? the comment above that says: These flags are invisible to userspace > > > > >> In pri...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...IFF_EBRIDGE = 1<<1, > IFF_BRIDGE_PORT = 1<<9, > IFF_OPENVSWITCH = 1<<20, > IFF_OVS_DATAPATH = 1<<10, > IFF_L3MDEV_MASTER = 1<<18, > IFF_L3MDEV_SLAVE = 1<<21, > IFF_TEAM = 1<<22, > IFF_TEAM_PORT = 1<<13, > }; That's not in uapi, is it? the comment above that says: These flags are invisible to userspace > > > > >> In pri...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
On Tue, May 22, 2018 at 05:13:43PM +0200, Jiri Pirko wrote: > Tue, May 22, 2018 at 03:39:33PM CEST, mst at redhat.com wrote: > >On Tue, May 22, 2018 at 03:26:26PM +0200, Jiri Pirko wrote: > >> Tue, May 22, 2018 at 03:17:37PM CEST, mst at redhat.com wrote: > >> >On Tue, May 22, 2018 at 03:14:22PM +0200, Jiri Pirko wrote: > >> >> Tue, May 22, 2018 at
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
On Tue, May 22, 2018 at 05:13:43PM +0200, Jiri Pirko wrote: > Tue, May 22, 2018 at 03:39:33PM CEST, mst at redhat.com wrote: > >On Tue, May 22, 2018 at 03:26:26PM +0200, Jiri Pirko wrote: > >> Tue, May 22, 2018 at 03:17:37PM CEST, mst at redhat.com wrote: > >> >On Tue, May 22, 2018 at 03:14:22PM +0200, Jiri Pirko wrote: > >> >> Tue, May 22, 2018 at
2018 May 22
0
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...enum netdev_priv_flags { IFF_EBRIDGE = 1<<1, IFF_BRIDGE_PORT = 1<<9, IFF_OPENVSWITCH = 1<<20, IFF_OVS_DATAPATH = 1<<10, IFF_L3MDEV_MASTER = 1<<18, IFF_L3MDEV_SLAVE = 1<<21, IFF_TEAM = 1<<22, IFF_TEAM_PORT = 1<<13, }; > >> In private >> flag. I don't see no reason to break this pattern here. > >Other masters are setup from userspace, this one is...
2018 May 22
0
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...= 1<<1, >> IFF_BRIDGE_PORT = 1<<9, >> IFF_OPENVSWITCH = 1<<20, >> IFF_OVS_DATAPATH = 1<<10, >> IFF_L3MDEV_MASTER = 1<<18, >> IFF_L3MDEV_SLAVE = 1<<21, >> IFF_TEAM = 1<<22, >> IFF_TEAM_PORT = 1<<13, >> }; > >That's not in uapi, is it? the comment above that says: Correct. > >These flags are invisible to userspace...