[brussels-dev] Re: [networking-discuss] Brussels high-level design document

[Peter Memishian]

 > > Okay.  While I understand what you've written at the top of page 10, there 
 > > are still questions in my mind.  How does the software know whether or not 
 > > a given property is currently in effect, or won't be in effect until 
 > > something else is done at a later time?  How will the administrator know 
 > > what to do to cause the properties to take effect if it's not immediate?  
 > > Are the conditions to cause a given property to take effect the same for 
 > > every driver which supports that property?
 > 
 > The conditions to cause a given property to be deferrred
 > are entirely dependant on the way the driver itself is
 > implemented. For example, it's possible that the driver implementation
 > is incapable of changing mtu after it is started because, for instance,
 > the mtu setting determines tx/rx buffer/ring allocation. In such a
 > situation, it is the driver's responsibility to emit a log message
 > saying when the change will be effective (e.g., the next stop/start
 > pair). The dladm/gldv3 framework itself would not interfere with the
 > behavior.

While I can understand that from an implementation standpoint, from a
usability standpoint I don't think a log message goes far enough.  The
person running the dladm set-linkprop subcommand needs the feedback.

-- 
meem