| To: | "Jeff Garzik" <jgarzik@xxxxxxxxx>, "Noam, Amir" <amir.noam@xxxxxxxxx> |
|---|---|
| Subject: | RE: [Bonding-devel] Re: [bonding] Add basic support for dynamic configuration of bond interfaces |
| From: | "Feldman, Scott" <scott.feldman@xxxxxxxxx> |
| Date: | Mon, 12 Jan 2004 17:44:14 -0800 |
| Cc: | "Jay Vosburgh" <fubar@xxxxxxxxxx>, <bonding-devel@xxxxxxxxxxxxxxxxxxxxx>, <netdev@xxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| Thread-index: | AcPX404QUetz7P+aRTSt4rJm9QEu6gBkPkYQ |
| Thread-topic: | [Bonding-devel] Re: [bonding] Add basic support for dynamic configuration of bond interfaces |
> I don't disagree with the overall goal of these patches, but
> I think we might need to pause a bit, and consider how best to
> configure, add, and remove bonding interfaces, if we are coming
> up with a new interface.
Could sysfs be used for the bonding UI? Seems like a natural fit.
Something like:
1) load bonding.o
/sys/class/net/
eth0/
eth1/
add_bond << write-only file added
2) Create a bond:
# echo "some params" >/sys/class/net/add_bond
/sys/class/net/
eth0/
eth1/
bond0/
del_bond
add_if
del_if
add_bond
3) Hook up the bond:
# echo "eth0" >/sys/class/net/bond0/add_if
# echo "eth1" >/sys/class/net/bond0/add_if
/sys/class/net/
eth0/
eth1/
bond0/
-->eth0/
-->eth1/
del_bond
add_if
del_if
new_bond
4) Delete the bond:
# echo "byebye" >/sys/class/net/bond0/del_bond
Etc. The whole kobject API is so clean, this should be trivial to code
up. Seems like VLAN and bridge modules could follow.
-scott
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [2.4] e1000 leaking pci mappings on rx errors?, Olof Johansson |
|---|---|
| Next by Date: | netdev3 posted..., Jeff Garzik |
| Previous by Thread: | [PATCH 2.6.X] SIOCSIFNAME wilcard support, Jean Tourrilhes |
| Next by Thread: | RE: [Bonding-devel] Re: [bonding] Add basic support for dynamic configuration of bond interfaces, Matt Domsch |
| Indexes: | [Date] [Thread] [Top] [All Lists] |