Sowmini.Varadhan at Sun.COM writes:
> 3. provide per-interface prop support in ipadm and leave the "global"
> setting alone (In addition to complicating our kernel tremendously,
> I don't even see how this would work. E.g. if the "prop"
> is some thing like a rate-limit parameter, and the value is different
> for each interface, then what would the global value be?)
[...]
> None of these options is ideal, but #2 seems to make the best of
> a bad-deal. Thoughts?
I suggest a fifth possibility with two variants:
5. Leave the global variable alone. It becomes the 'default' for
newly-plumbed interfaces. Interfaces can be configured away from
that value, but the global doesn't reflect those changes.
a. The default value is just copied into the interface when the
interface is plumbed. If the default is later changed, the
already-plumbed interfaces are unaffected.
b. The interface dynamically uses the global value as long as the
local value is not configured specifically for that interface.
Once it's configured, the connection with the global value is
severed.
The advantage of (a) is it's simple to implement, but might be hard to
understand. The advantage of (b) is that it's much easier to
understand (and is strictly compatible -- up to the point where
someone uses the new per-interface tuning capability), but it's
slightly harder to implement. (With decent coding support, though, it
likely wouldn't be too awful.)
--
James Carlson, Solaris Networking <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
