[Top] [All Lists]

Re: [bonding] Add basic support for dynamic configuration of bond interf

To: Amir Noam <amir.noam@xxxxxxxxx>
Subject: Re: [bonding] Add basic support for dynamic configuration of bond interfaces
From: jamal <hadi@xxxxxxxxxx>
Date: 11 Jan 2004 13:30:51 -0500
Cc: Jeff Garzik <jgarzik@xxxxxxxxx>, bonding-devel@xxxxxxxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <200401111628.07930.amir.noam@xxxxxxxxx>
Organization: jamalopolis
References: <E6F7D288B394A64585E67497E5126BA601F991D1@xxxxxxxxxxxxxxxxxxxxxxx> <200401111628.07930.amir.noam@xxxxxxxxx>
Reply-to: hadi@xxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
On Sun, 2004-01-11 at 09:28, Amir Noam wrote:

> > I would suggest a simple character device (misc_register), and let
> > the userland application configure settings unrelated to a single
> > object.
> I was trying to follow the example of several other network modules 
> (e.g. vlan, dlci, bridge) that use a socket level ioctl hook to 
> handle such deviceless commands.
> Do you think that a char device is preferrable, given that other 
> similar modules use a socket ioctl hook?

I think a netlink interface would be the better alternative.
The L2C netlink socket protocol would be appropriate for bonding
at least for 2.6.x. Bridging, VLAN should also move to this.


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