search for: list_netdevice

Displaying 5 results from an estimated 5 matches for "list_netdevice".

2018 Apr 07
2
[RFC PATCH 2/3] netdev: kernel-only IFF_HIDDEN netdevice
...Linux driver model too well, but to get a device out of one class and into another, i think you need to device_del(dev). modify dev->class and then device_add(dev). However, device_add() says you are not allowed to do this. And i don't even see how this helps. Are you also not going to call list_netdevice()? Are you going to add some other list for these devices in a different class? Andrew
2018 Apr 07
2
[RFC PATCH 2/3] netdev: kernel-only IFF_HIDDEN netdevice
...Linux driver model too well, but to get a device out of one class and into another, i think you need to device_del(dev). modify dev->class and then device_add(dev). However, device_add() says you are not allowed to do this. And i don't even see how this helps. Are you also not going to call list_netdevice()? Are you going to add some other list for these devices in a different class? Andrew
2018 Apr 09
0
[RFC PATCH 2/3] netdev: kernel-only IFF_HIDDEN netdevice
...ore it's a rather big hammer approach I'd think. If there exists a better implementation than this to allow adding a separate layer of in-kernel device namespace, I'd more than welcome to hear about. > > And i don't even see how this helps. Are you also not going to call > list_netdevice()? Are you going to add some other list for these > devices in a different class? list_netdevice() is still called. I think with the current RFC patch, I've added two lists for netdevs under the kernel namespace: dev_cmpl_list and name_cmpl_hlist. As a result of that, all userspace netdevs...
2018 Apr 04
4
[RFC PATCH 2/3] netdev: kernel-only IFF_HIDDEN netdevice
From: David Ahern <dsahern at gmail.com> Date: Wed, 4 Apr 2018 11:21:54 -0600 > It is a netdev so there is no reason to have a separate ip command to > inspect it. 'ip link' is the right place. I agree on this. What I really don't understand still is the use case... really. So there are control netdevs, what exactly is the problem with that? Are we not exporting enough
2018 Apr 04
4
[RFC PATCH 2/3] netdev: kernel-only IFF_HIDDEN netdevice
From: David Ahern <dsahern at gmail.com> Date: Wed, 4 Apr 2018 11:21:54 -0600 > It is a netdev so there is no reason to have a separate ip command to > inspect it. 'ip link' is the right place. I agree on this. What I really don't understand still is the use case... really. So there are control netdevs, what exactly is the problem with that? Are we not exporting enough