| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <200704260727.l3Q7RVXx023976@shell0.pdx.osdl.net> Date: Thu, 26 Apr 2007 00:27:31 -0700 From: akpm@...ux-foundation.org To: davem@...emloft.net Cc: netdev@...r.kernel.org, akpm@...ux-foundation.org, Alexandra.Kossovsky@...etlabs.ru, fubar@...ibm.com, shemminger@...ux-foundation.org Subject: [patch 12/15] networking: bonding documentation fix for multiple bonding interfaces From: "Alexandra N. Kossovsky" <Alexandra.Kossovsky@...etlabs.ru> Fix bonding driver documentation for the case of multiple bonding interfaces. Signed-off-by: "Alexandra N. Kossovsky" <Alexandra.Kossovsky@...etlabs.ru> Acked-by: Jay Vosburgh <fubar@...ibm.com> Cc: Stephen Hemminger <shemminger@...l.org> Signed-off-by: Andrew Morton <akpm@...ux-foundation.org> --- Documentation/networking/bonding.txt | 35 +------------------------ 1 file changed, 2 insertions(+), 33 deletions(-) diff -puN Documentation/networking/bonding.txt~networking-bonding-documentation-fix-for-multiple-bonding-interfaces Documentation/networking/bonding.txt --- a/Documentation/networking/bonding.txt~networking-bonding-documentation-fix-for-multiple-bonding-interfaces +++ a/Documentation/networking/bonding.txt @@ -920,40 +920,9 @@ options, you may wish to use the "max_bo documented above. To create multiple bonding devices with differing options, it -is necessary to load the bonding driver multiple times. Note that -current versions of the sysconfig network initialization scripts -handle this automatically; if your distro uses these scripts, no -special action is needed. See the section Configuring Bonding -Devices, above, if you're not sure about your network initialization -scripts. - - To load multiple instances of the module, it is necessary to -specify a different name for each instance (the module loading system -requires that every loaded module, even multiple instances of the same -module, have a unique name). This is accomplished by supplying -multiple sets of bonding options in /etc/modprobe.conf, for example: - -alias bond0 bonding -options bond0 -o bond0 mode=balance-rr miimon=100 - -alias bond1 bonding -options bond1 -o bond1 mode=balance-alb miimon=50 - - will load the bonding module two times. The first instance is -named "bond0" and creates the bond0 device in balance-rr mode with an -miimon of 100. The second instance is named "bond1" and creates the -bond1 device in balance-alb mode with an miimon of 50. - - In some circumstances (typically with older distributions), -the above does not work, and the second bonding instance never sees -its options. In that case, the second options line can be substituted -as follows: - -install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \ - mode=balance-alb miimon=50 +is necessary to use bonding parameters exported by sysfs, documented +in the section below. - This may be repeated any number of times, specifying a new and -unique name in place of bond1 for each subsequent instance. 3.4 Configuring Bonding Manually via Sysfs ------------------------------------------ _ - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists