search for: ifla_mast

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

Did you mean: ifla_max
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...now which ones to skip and which one is > >the master? Right now userspace seems to assume whatever does not have > >IFF_SLAVE should be looked at. Are you saying that's not the right thing > > Why do you say so? What do you mean by "looked at"? Certainly not. > IFLA_MASTER is the attribute that should be looked at, nothing else. > > > >to do and userspace should be fixed? What should userspace do in > >your opinion that will be forward compatible with future kernels? > > > >> > >> >we don't set IFF_SLAVE existing...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...now which ones to skip and which one is > >the master? Right now userspace seems to assume whatever does not have > >IFF_SLAVE should be looked at. Are you saying that's not the right thing > > Why do you say so? What do you mean by "looked at"? Certainly not. > IFLA_MASTER is the attribute that should be looked at, nothing else. > > > >to do and userspace should be fixed? What should userspace do in > >your opinion that will be forward compatible with future kernels? > > > >> > >> >we don't set IFF_SLAVE existing...
2018 May 22
0
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...ip and which one is >> >the master? Right now userspace seems to assume whatever does not have >> >IFF_SLAVE should be looked at. Are you saying that's not the right thing >> >> Why do you say so? What do you mean by "looked at"? Certainly not. >> IFLA_MASTER is the attribute that should be looked at, nothing else. >> >> >> >to do and userspace should be fixed? What should userspace do in >> >your opinion that will be forward compatible with future kernels? >> > >> >> >> >> >we don...
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
...ould existing userspace know which ones to skip and which one is >the master? Right now userspace seems to assume whatever does not have >IFF_SLAVE should be looked at. Are you saying that's not the right thing Why do you say so? What do you mean by "looked at"? Certainly not. IFLA_MASTER is the attribute that should be looked at, nothing else. >to do and userspace should be fixed? What should userspace do in >your opinion that will be forward compatible with future kernels? > >> >> >we don't set IFF_SLAVE existing userspace tries to use the lowerdev...