Peter Memishian wrote:
> > Does "autopush" fit in there, even? (I don't know how this will be
> > used, so its a real question.)
>
> The "autopush" tunable is there to allow people to interpose STREAMS
> modules like they currently do with /etc/iu.ap. See the UV design
> document for details and rationale.
>
Right. But do we think this will be a common usage?
> > I'm sort of thinking that show-linkprop should be our ndd-like
> > replacement inteface, and that the couple of other properties (mtu,
> > maybe the zone) belong in the show-<linktype> output.
>
> My stance depends what "ndd-like" ends up meaning -- but if it
> approximates any definition of "dumping ground for poorly-thought
> out knobs", then I'm opposed ;-)
>
Well, *hopefully* the knobs will be better thought out, more consistent,
and fewer. But at some level, it is possible that some drivers will use
this to export their current crappy parameters without considering what
the norm is.
The e1000g driver is a good example of this in its kstats... it dumps a
bunch of kstats, which are duplicates of others that are already
exported, using different names. As long as we allow for extendability
(which is really important!) we can hardly guarantee against stupidity
in device drivers.
I'm quite sure that NSN will continue to support a dumping ground of
obscure and poorly thought out knobs in their drivers going forward...
because they don't know any better and the practice has become
institutional there... thanks largely to that bastardization called cassini.
Whether they do it via Brussels or some other ill-conceived framework
remains to be seen.
- Garrett
