Peter Memishian wrote:
> > > It seems a shame to clutter the dladm link property space (and thus dladm
> > > show-linkprop output) with this sea of related knobs when we could
> instead
> > > use the same syntax that dladm show-ether uses to report this information
> > > and have a single "speed-duplex" link property that takes a list -- e.g.:
> > >
> > > dladm set-linkprop -p speed-duplex=10G-f,1G-f net0
> > >
> > > It would also mean we wouldn't need to add a new property with every bump
> > > in speed.
> > >
> > > There's a bug logged on this: 6804384.
> >
> > Architecturally it may be nicer, however I think a redesign of the dladm
> > linkprops is beyond the scope of this case.
>
> I'm not asking for a redesign with this case, but the current scheme can
> and should be improved upon, and if we do that we will probably need to
> declare what's being defined here (and the other similar tunables) as
> obsolete (or just yank them entirely, depending on the perceived impact).
>
I'd suggest for a more concrete proposal from you if you want to do
that. I'm not a huge fan of the way the tunables work, but they fall
out rather naturally from the way the 802.3 MII works. They allow one
to specifically enable any set of abilities, and arbitrarily disable any
specific ones. I know that most folks never use this ability beyond
forcing a specific speed/duplex setting, but there could be some that
are doing more unusual things with them.
And, as Paul said, not this case.
However, if you want to, we can promote this case to a fast track. I
don't think that will change the fact that what you're looking for is
out of scope for this case, though.
- Garrett
