bonding: Allow setting max_bonds to zero
authorJay Vosburgh <fubar@us.ibm.com>
Sat, 14 Jun 2008 01:12:04 +0000 (18:12 -0700)
committerJeff Garzik <jgarzik@redhat.com>
Wed, 18 Jun 2008 04:00:04 +0000 (00:00 -0400)
commitb8a9787eddb0e4665f31dd1d64584732b2b5d051
tree08b7537e70b6a96bc04d231d31ccd644e1387e62
parentb59f9f74c4c0a569398f08c34a877f1b7b457496
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>
Documentation/networking/bonding.txt
drivers/net/bonding/bond_main.c
drivers/net/bonding/bond_sysfs.c
include/linux/netdevice.h
net/core/net-sysfs.c