sowmini.varadhan at sun.com wrote:
> A couple of observations pertaining to the libnwam header changes
> proposed in
> http://cr.grommit.com/~jbeck/renee-nwam1-ln2/
>
> - NWAM is considering the mtu as a configurable property, but it should
> be clarified that this is just the IP mtu (set via SIOCSLIFMTU) and
> not the driver mtu (which would have to be modified separately to
> configure Jumbo Frames). In order to modify the latter via NWAM,
> the changes being implemented by the Brussels project will be needed.
>
Once Brussels is available, it would be _really_ nice if IP could
inquire, and modify the underlying MTU. I.e. administrators should only
have to configure a single MTU.
Just a thought.
-- Garrett
> - At least for the near future, we will have two daemons: nwamd and
> linkmgmtd, that both do some sort of "setprop" for configuring link
> properties. It also looks like the definition of what is a link
> property is subjective: NWAM does not configure link speed/duplex
> etc., but does look at mtu, whereas linkmgmtd's focus appears to be
> link-aggregations.
>
> Having 2 daemons that do very similar property management makes
> things a bit hairy for a project like Brussels: there are now two
> setprop functions that will need to be examined to see if they
> need to leverage from Brussels enhancements.
>
> I realize that the two projects are approaching the problem from
> different ends of the stack (bottom and top) but one hopes that
> the two paths will meet somehwere in the future.
>
> --Sowmini
>
> _______________________________________________
> nwam-discuss mailing list
> nwam-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/nwam-discuss
>
