> Going with the trend of 'one-discussion thread per week', we would like > to start another discussion on 'select IP tunables' that would be > 'initially' supported by /ipadm/ to begin with. > > At the link below we have listed the names of the tunables, it's scope > (Global or per interface) and definition of the tunable. > > http://cr.opensolaris.org/~girishmg/ipadm_prop.htm
I'd argue ip_addr_per_if is a bug given that the number of IP interfaces on the system is not bounded. Why are we carrying this tunable forward? More generally, a lot of those things look very low-level and some appear to just be available as possible workarounds for broken software (e.g., ip_lso_outbound). I think this an abuse of the properties mechanism, which really should provide the administrator the ability to fine-tune the configuration for e.g. their site policies and needs. Also, I trust that you will not be taking these properties as-is. For instance, it's cleaner to have a single echo-reply tunable that can be set to one or more values like "broadcast" than to have a sea of boolean tunables. > We wanted to know if we have defined the 'scope' of the tunable correctly? See above. -- meem
