On Thursday, January 03, 2008 12:04, Jay Vosburgh wrote: >> In our startup scripts we need to be able to ensure that the >> interface name is consistent across reboots. Sometimes bond1 may be >> brought up before bond0 and it may have different options (requiring >> a different instance of the bonding driver). > > With the sysfs interface to bonding, your last statement is not > true; any number of bonding interfaces, with arbitrary names, can be > created and have their options set without loading multiple instances > of the bonding driver. > > Does your embedded system have sysfs available? If it does, > then it's to your advantage to use the sysfs API; for one thing, the > single instance of the bonding driver with all interfaces through it > should utilize fewer resources than loading the driver repeatedly. >
We do have sysfs available. I actually did not realize that it is possible to have one bonding instance and create multiple interfaces with different options. It looks like when I initially wrote this patch (~2.6.20) either this feature was not available, or the bonding documentation may have been out of date. I see now in the latest Documentation/networking/bonding.txt that this is explained clearly. Thank you for your help, I will drop the patch and move to using the sysfs method. Although I may need to patch it for our own uses to either not create bond0 on module load, or I may just run 'echo -bond0 > /sys/class/net/bonding_masters' immediately after loading the module. Jari -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
