netdev
[Top] [All Lists]

RE: [Bonding-devel] Re: [bonding] Add basic support for dynamic configur

To: Matt Domsch <Matt_Domsch@xxxxxxxx>
Subject: RE: [Bonding-devel] Re: [bonding] Add basic support for dynamic configuration of bond interfaces
From: jamal <hadi@xxxxxxxxxx>
Date: 13 Jan 2004 09:17:20 -0500
Cc: "Feldman, Scott" <scott.feldman@xxxxxxxxx>, Jeff Garzik <jgarzik@xxxxxxxxx>, "Noam, Amir" <amir.noam@xxxxxxxxx>, Jay Vosburgh <fubar@xxxxxxxxxx>, bonding-devel@xxxxxxxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.44.0401122032480.6491-100000@humbolt.us.dell.com>
Organization: jamalopolis
References: <Pine.LNX.4.44.0401122032480.6491-100000@humbolt.us.dell.com>
Reply-to: hadi@xxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
I think this would be fine if you have some simple policy
maybe upto 5 variables. Its simplicty gives it a lot of value.
However, once you start getting into more demanding setups with lotsa
table based configs this is quickly going to turn into a configuration
nightmare. What we should shoot for with netlink is to make it
as stoopid-proof as well - although not too stoopid proof to be
dangerous.  

cheers,
jamal

On Mon, 2004-01-12 at 21:34, Matt Domsch wrote:
> > Could sysfs be used for the bonding UI?  Seems like a natural fit.
> > Something like:
> > # echo "some params" >/sys/class/net/add_bond
> > # echo "byebye" >/sys/class/net/bond0/del_bond
> 
> FWIW, this is exactly what we're doing with the efivars module to create 
> and destroy EFI Variables now, and appears to be a sane approach.
> 
> Thanks,
> Matt


<Prev in Thread] Current Thread [Next in Thread>