Messages in this thread | | | Date | Tue, 14 Aug 2012 12:18:52 +0200 | From | Jiri Pirko <> | Subject | Re: [patch net-next 01/16] net: introduce upper device lists |
| |
Tue, Aug 14, 2012 at 11:02:33AM CEST, xiyou.wangcong@gmail.com wrote: >On 08/13/2012 11:27 PM, Jiri Pirko wrote: >>This lists are supposed to serve for storing pointers to all upper devices. >>Eventually it will replace dev->master pointer which is used for >>bonding, bridge, team but it cannot be used for vlan, macvlan where >>there might be multiple "masters" present. >> >>New upper device list resolves this limitation. Also, the information >>stored in lists is used for preventing looping setups like >>"bond->somethingelse->samebond" > >Hi, Jiri, > >I have some difficulty to understand this patch description, so take >bridged bonding as an example, IIUC, both the bridge dev and bonding >dev will be in the upper dev list of eth0 and eth1? And br0 will be >in the upper dev list of bond0 too?
No. Only direct upper device is in the list.
> >I think it would be nice to describe the hierarchy after your patches.
Hierarchy is the same after.
> >Thanks! >
| |