[ovs-discuss] [PATCH 00/20] Implement abstract interfaces to network devices

Ben Pfaff blp at nicira.com
Tue Jul 28 21:51:00 UTC 2009

Jesse Gross <jesse at nicira.com> writes:

> Ben Pfaff wrote:
>>> Some of the netdevs may want to use the config file, so it would be
>>> useful to have a reconfigure call in the netdev interface.
>> My gut reaction is that that would be a mistake, at least at this
>> point.  If the netdevs need configuration then I think we should
>> add an interface to netdev_*() for doing that instead of letting
>> them read the configuration willy-nilly.
>> But I don't know what kind of configuration you have in mind.
>> Can you give an example?
> I'm thinking of configuration that is specific to a certain type of
> device so it wouldn't necessarily be appropriate to add to the netdev
> interface.  For example, a Unix domain socket netdev might have a
> bunch of parameters such as socket name, permissions, etc., that only
> it would really use and understand.

My thought was that this kind of parameter should be given in the
name, e.g. "unix:/tmp/foo,mode=660,owner=daemon,group=root".

More information about the discuss mailing list