search for: iff_slave

Displaying 20 results from an estimated 55 matches for "iff_slave".

2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...;> > > >> >> >This should be part of the common "failover" code. > >> >> > > >> >> > >> >> Also note that in the current patchset you use IFF_FAILOVER flag for > >> >> master, yet for the slave you use IFF_SLAVE. That is wrong. > >> >> IFF_FAILOVER_SLAVE should be used. > >> > > >> >Or drop IFF_FAILOVER_SLAVE and set both IFF_FAILOVER and IFF_SLAVE? > >> > >> No. IFF_SLAVE is for bonding. > > > >What breaks if we reuse it for failover? &...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...;> > > >> >> >This should be part of the common "failover" code. > >> >> > > >> >> > >> >> Also note that in the current patchset you use IFF_FAILOVER flag for > >> >> master, yet for the slave you use IFF_SLAVE. That is wrong. > >> >> IFF_FAILOVER_SLAVE should be used. > >> > > >> >Or drop IFF_FAILOVER_SLAVE and set both IFF_FAILOVER and IFF_SLAVE? > >> > >> No. IFF_SLAVE is for bonding. > > > >What breaks if we reuse it for failover? &...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...t;This should be part of the common "failover" code. > >> >> >> > > >> >> >> > >> >> >> Also note that in the current patchset you use IFF_FAILOVER flag for > >> >> >> master, yet for the slave you use IFF_SLAVE. That is wrong. > >> >> >> IFF_FAILOVER_SLAVE should be used. > >> >> > > >> >> >Or drop IFF_FAILOVER_SLAVE and set both IFF_FAILOVER and IFF_SLAVE? > >> >> > >> >> No. IFF_SLAVE is for bonding. > >> &g...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...t;This should be part of the common "failover" code. > >> >> >> > > >> >> >> > >> >> >> Also note that in the current patchset you use IFF_FAILOVER flag for > >> >> >> master, yet for the slave you use IFF_SLAVE. That is wrong. > >> >> >> IFF_FAILOVER_SLAVE should be used. > >> >> > > >> >> >Or drop IFF_FAILOVER_SLAVE and set both IFF_FAILOVER and IFF_SLAVE? > >> >> > >> >> No. IFF_SLAVE is for bonding. > >> &g...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
..., this is still done in netvsc. Why? > >> > > >> >This should be part of the common "failover" code. > >> > > >> > >> Also note that in the current patchset you use IFF_FAILOVER flag for > >> master, yet for the slave you use IFF_SLAVE. That is wrong. > >> IFF_FAILOVER_SLAVE should be used. > > > >Or drop IFF_FAILOVER_SLAVE and set both IFF_FAILOVER and IFF_SLAVE? > > No. IFF_SLAVE is for bonding. What breaks if we reuse it for failover? -- MST
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
..., this is still done in netvsc. Why? > >> > > >> >This should be part of the common "failover" code. > >> > > >> > >> Also note that in the current patchset you use IFF_FAILOVER flag for > >> master, yet for the slave you use IFF_SLAVE. That is wrong. > >> IFF_FAILOVER_SLAVE should be used. > > > >Or drop IFF_FAILOVER_SLAVE and set both IFF_FAILOVER and IFF_SLAVE? > > No. IFF_SLAVE is for bonding. What breaks if we reuse it for failover? -- MST
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
..."failover" code. > >> >> >> >> > > >> >> >> >> > >> >> >> >> Also note that in the current patchset you use IFF_FAILOVER flag for > >> >> >> >> master, yet for the slave you use IFF_SLAVE. That is wrong. > >> >> >> >> IFF_FAILOVER_SLAVE should be used. > >> >> >> > > >> >> >> >Or drop IFF_FAILOVER_SLAVE and set both IFF_FAILOVER and IFF_SLAVE? > >> >> >> > >> >> >> N...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
..."failover" code. > >> >> >> >> > > >> >> >> >> > >> >> >> >> Also note that in the current patchset you use IFF_FAILOVER flag for > >> >> >> >> master, yet for the slave you use IFF_SLAVE. That is wrong. > >> >> >> >> IFF_FAILOVER_SLAVE should be used. > >> >> >> > > >> >> >> >Or drop IFF_FAILOVER_SLAVE and set both IFF_FAILOVER and IFF_SLAVE? > >> >> >> > >> >> >> N...
2018 May 22
0
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...part of the common "failover" code. >> >> >> >> > >> >> >> >> >> >> >> >> Also note that in the current patchset you use IFF_FAILOVER flag for >> >> >> >> master, yet for the slave you use IFF_SLAVE. That is wrong. >> >> >> >> IFF_FAILOVER_SLAVE should be used. >> >> >> > >> >> >> >Or drop IFF_FAILOVER_SLAVE and set both IFF_FAILOVER and IFF_SLAVE? >> >> >> >> >> >> No. IFF_SLAVE is for bondi...
2018 May 22
0
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...uot; code. >> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> Also note that in the current patchset you use IFF_FAILOVER flag for >> >> >> >> >> master, yet for the slave you use IFF_SLAVE. That is wrong. >> >> >> >> >> IFF_FAILOVER_SLAVE should be used. >> >> >> >> > >> >> >> >> >Or drop IFF_FAILOVER_SLAVE and set both IFF_FAILOVER and IFF_SLAVE? >> >> >> >> >> >>...
2018 May 22
0
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...>> >> >This should be part of the common "failover" code. >> >> >> > >> >> >> >> >> >> Also note that in the current patchset you use IFF_FAILOVER flag for >> >> >> master, yet for the slave you use IFF_SLAVE. That is wrong. >> >> >> IFF_FAILOVER_SLAVE should be used. >> >> > >> >> >Or drop IFF_FAILOVER_SLAVE and set both IFF_FAILOVER and IFF_SLAVE? >> >> >> >> No. IFF_SLAVE is for bonding. >> > >> >What breaks if...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
..._upper_dev_link() etc > >(netvsc_vf_join()). Now, this is still done in netvsc. Why? > > > >This should be part of the common "failover" code. > > > > Also note that in the current patchset you use IFF_FAILOVER flag for > master, yet for the slave you use IFF_SLAVE. That is wrong. > IFF_FAILOVER_SLAVE should be used. Or drop IFF_FAILOVER_SLAVE and set both IFF_FAILOVER and IFF_SLAVE? -- MST
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
..._upper_dev_link() etc > >(netvsc_vf_join()). Now, this is still done in netvsc. Why? > > > >This should be part of the common "failover" code. > > > > Also note that in the current patchset you use IFF_FAILOVER flag for > master, yet for the slave you use IFF_SLAVE. That is wrong. > IFF_FAILOVER_SLAVE should be used. Or drop IFF_FAILOVER_SLAVE and set both IFF_FAILOVER and IFF_SLAVE? -- MST
2018 May 31
1
[PATCH net-next v12 1/5] net: Introduce generic failover module
...IFF_FAILOVER_SLAVE = 1<<28, > >> }; > > Why is FAILOVER any different than other master/slave relationships. > > I don't think you need to take up precious netdev flag bits for this. > > These are netdev priv flags. > Jiri says that IFF_MASTER/IFF_SLAVE are bonding specific flags and cannot be used > with other failover mechanisms. Team also doesn't use this flags and it has its own > priv_flags. > This change breaks userspace. We already have worked with partners to ignore devices marked as IFF_SLAVE, and IFF_SLAVE is visible to us...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...to move some of the code from net_failover.c to generic >>>> failover.c in future if Stephen is ok with it. >>>> >>>> >>>>> Also note that in the current patchset you use IFF_FAILOVER flag for >>>>> master, yet for the slave you use IFF_SLAVE. That is wrong. >>>>> IFF_FAILOVER_SLAVE should be used. >>>> Not sure which code you are referring to.? I only set IFF_FAILOVER_SLAVE >>>> in patch 3. >>> The existing netvsc driver. >> We really can't change netvsc's flags now, even if...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...to move some of the code from net_failover.c to generic >>>> failover.c in future if Stephen is ok with it. >>>> >>>> >>>>> Also note that in the current patchset you use IFF_FAILOVER flag for >>>>> master, yet for the slave you use IFF_SLAVE. That is wrong. >>>>> IFF_FAILOVER_SLAVE should be used. >>>> Not sure which code you are referring to.? I only set IFF_FAILOVER_SLAVE >>>> in patch 3. >>> The existing netvsc driver. >> We really can't change netvsc's flags now, even if...
2018 May 25
3
[PATCH net-next v12 1/5] net: Introduce generic failover module
On Thu, 24 May 2018 09:55:13 -0700 Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h > index 03ed492c4e14..0f4ba52b641d 100644 > --- a/include/linux/netdevice.h > +++ b/include/linux/netdevice.h > @@ -1421,6 +1421,8 @@ struct net_device_ops { > *
2018 May 25
3
[PATCH net-next v12 1/5] net: Introduce generic failover module
On Thu, 24 May 2018 09:55:13 -0700 Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h > index 03ed492c4e14..0f4ba52b641d 100644 > --- a/include/linux/netdevice.h > +++ b/include/linux/netdevice.h > @@ -1421,6 +1421,8 @@ struct net_device_ops { > *
2018 May 22
0
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...netvsc. Why? >> >> > >> >> >This should be part of the common "failover" code. >> >> > >> >> >> >> Also note that in the current patchset you use IFF_FAILOVER flag for >> >> master, yet for the slave you use IFF_SLAVE. That is wrong. >> >> IFF_FAILOVER_SLAVE should be used. >> > >> >Or drop IFF_FAILOVER_SLAVE and set both IFF_FAILOVER and IFF_SLAVE? >> >> No. IFF_SLAVE is for bonding. > >What breaks if we reuse it for failover? This is exposed to userspace. IFF_S...
2018 May 22
2
Shepherd request (P83): Multipath TCP: Present Use Cases and an Upstream Future
...ould be possible to move some of the code from net_failover.c to generic > >failover.c in future if Stephen is ok with it. > > > > > >> > > >> Also note that in the current patchset you use IFF_FAILOVER flag for > >> master, yet for the slave you use IFF_SLAVE. That is wrong. > >> IFF_FAILOVER_SLAVE should be used. > > > >Not sure which code you are referring to.? I only set IFF_FAILOVER_SLAVE > >in patch 3. > > The existing netvsc driver. We really can't change netvsc's flags now, even if it's interface is...