search for: iff_team_port

...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 private > >> flag. I don't see no reason to break this pattern here. > > > >Other masters are s...

...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 private > >> flag. I don't see no reason to break this pattern here. > > > >Other masters are s...

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

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

...= 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 set up automatically >by kernel. So the bar is higher, we need an interface that existing >userspace...

...CH = 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 > > > >> >> > >> >> In private >> >> flag. I don't see no reason to bre...

three drivers updated, but this can be used in many others. v1->v2: %s/LIFE/LIVE Jiri Pirko (4): net: introduce new priv_flag indicating iface capable of change mac when running virtio_net: use IFF_LIVE_ADDR_CHANGE priv_flag team: use IFF_LIVE_ADDR_CHANGE priv_flag dummy: use IFF_LIVE_ADDR_CHANGE priv_flag drivers/net/dummy.c | 15 ++------------- drivers/net/team/team.c

three drivers updated, but this can be used in many others. v1->v2: %s/LIFE/LIVE Jiri Pirko (4): net: introduce new priv_flag indicating iface capable of change mac when running virtio_net: use IFF_LIVE_ADDR_CHANGE priv_flag team: use IFF_LIVE_ADDR_CHANGE priv_flag dummy: use IFF_LIVE_ADDR_CHANGE priv_flag drivers/net/dummy.c | 15 ++------------- drivers/net/team/team.c

three drivers updated, but this can be used in many others. Jiri Pirko (4): net: introduce new priv_flag indicating iface capable of change mac when running virtio_net: use IFF_LIFE_ADDR_CHANGE priv_flag team: use IFF_LIFE_ADDR_CHANGE priv_flag dummy: use IFF_LIFE_ADDR_CHANGE priv_flag drivers/net/dummy.c | 15 ++------------- drivers/net/team/team.c | 9 +++++----

three drivers updated, but this can be used in many others. Jiri Pirko (4): net: introduce new priv_flag indicating iface capable of change mac when running virtio_net: use IFF_LIFE_ADDR_CHANGE priv_flag team: use IFF_LIFE_ADDR_CHANGE priv_flag dummy: use IFF_LIFE_ADDR_CHANGE priv_flag drivers/net/dummy.c | 15 ++------------- drivers/net/team/team.c | 9 +++++----