| To: | fubar@xxxxxxxxxx, bonding-devel@xxxxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [PATCH 2.6.12-rc2 0/17] bonding: sysfs interface... |
| From: | Radheka Godse <radheka.godse@xxxxxxxxx> |
| Date: | Fri, 8 Apr 2005 16:15:24 -0700 (PDT) |
| Cc: | netdev@xxxxxxxxxxx |
| Replyto: | "Radheka Godse" <radheka.godse@intel.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
|
This patch set implements the sysfs interface for bonding and has a couple bug fixes. We have done a full test pass and consider these patches ready for inclusion upstream. We have submitted them to bonding-devel several times and have incorporated feedback and fixes all known issues. The interface is pretty simple. Here are some notes on how it could be used: The file /sys/class/net/bonding_masters contains the names of all the
active bonds. To add or remove bonds, write a whitespace-delimited list of
interface names to this file. For example:
echo "bond1 bond2 bond3" > /sys/class/net/bonding_masters
will create three bonds with the given names. If any other
bonds exist, they will be deleted.
echo "bond0 bond2 bond3" > /sys/class/net/bonding_masters
would then create bond0 and remove bond1.For each bond, there is a directory /sys/class/net/<bondname>/bonding. In this directory are a number of files which control the bond. The names of these files match the existing module parameters and do the same things. The slaves file contains a whitespace-delimited list of interface names, which are slaves to the bond. This file behaves much the same as the "bonding_masters" file; just write a list of your desired interfaces to this file. Likewise, the arp_targets file contains a whitespace-delimited list of IP addresses and should be written to in a similar fashion. The other files contain single values(numeric and/or mnemonic), except for stat, which duplicates the slave information in the proc file. Some caveats: - slaves can only be assigned when the interface is up - mode can only be changed when the interface is down Warnings and status messages will be logged and can be viewed with dmesg. Example: modprobe bonding echo "bond0 bond1" > /sys/class/net/bonding_masters echo "6" > /sys/class/net/bond0/bonding/mode echo "1000" > /sys/class/net/bond0/bonding/miimon ifconfig bond0 192.168.0.1 echo "eth0 eth1" > /sys/class/net/bond0/bonding/slaves # bond0 is now ready to use echo "1" > /sys/class/net/bond1/bonding/mode # ... and so on for bond1
- Mitch Williams - Radheka Godse |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] RTNETLINK: Protocol family wildcard dumping for routing rules, jamal |
|---|---|
| Next by Date: | [PATCH 2.6.12-rc2 1/17] bonding: make some functions not static, Radheka Godse |
| Previous by Thread: | [PATCH] RTNETLINK: Protocol family wildcard dumping for routing rules, Thomas Graf |
| Next by Thread: | Re: [PATCH 2.6.12-rc2 0/17] bonding: sysfs interface..., Stephen Hemminger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |