diff options
author | Jay Vosburgh <fubar@us.ibm.com> | 2008-06-13 18:12:04 -0700 |
---|---|---|
committer | Jeff Garzik <jgarzik@redhat.com> | 2008-06-18 00:00:04 -0400 |
commit | b8a9787eddb0e4665f31dd1d64584732b2b5d051 (patch) | |
tree | 08b7537e70b6a96bc04d231d31ccd644e1387e62 /Documentation/networking/bonding.txt | |
parent | b59f9f74c4c0a569398f08c34a877f1b7b457496 (diff) | |
download | op-kernel-dev-b8a9787eddb0e4665f31dd1d64584732b2b5d051.zip op-kernel-dev-b8a9787eddb0e4665f31dd1d64584732b2b5d051.tar.gz |
bonding: Allow setting max_bonds to zero
Permit bonding to function rationally if max_bonds is set to
zero. This will load the module, but create no master devices (which can
be created via sysfs).
Requires some change to bond_create_sysfs; currently, the
netdev sysfs directory is determined from the first bonding device created,
but this is no longer possible. Instead, an interface from net/core is
created to create and destroy files in net_class.
Based on a patch submitted by Phil Oester <kernel@linuxaces.com>.
Modified by Jay Vosburgh to fix the sysfs issue mentioned above and to
update the documentation.
Signed-off-by: Phil Oester <kernel@linuxace.com>
Signed-off-by: Jay Vosburgh <fubar@us.ibm.com>
Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
Diffstat (limited to 'Documentation/networking/bonding.txt')
-rw-r--r-- | Documentation/networking/bonding.txt | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/networking/bonding.txt b/Documentation/networking/bonding.txt index 370b7da..7fa7fe7 100644 --- a/Documentation/networking/bonding.txt +++ b/Documentation/networking/bonding.txt @@ -376,7 +376,8 @@ max_bonds Specifies the number of bonding devices to create for this instance of the bonding driver. E.g., if max_bonds is 3, and the bonding driver is not already loaded, then bond0, bond1 - and bond2 will be created. The default value is 1. + and bond2 will be created. The default value is 1. Specifying + a value of 0 will load bonding, but will not create any devices. miimon |