Peter Memishian wrote:
> > Ah. See I'm thinking probably a layer down. In other words, I think
> > the properties need to exist. How they are presented, is a different
> > matter entirely.
> >
> > But, for what it is worth, for a typical 1G device, the list of modes
> > will be quite a bit larger:
> >
> > CAPABLE
> >
> > 10M Half, 10M Full, 100M Half, 100M Full, 1G Half, 1G Full
>
> That wouldn't look much worse -- e.g.:
>
> LINK DUPLEX CAPABLE ADV PEERADV
> bge0 half 10M,100M,1G 10M,100M,1G 10M,100M
> bge0 full 10M,100M,1G 10M,100M,1G 10M,100M
>
> > And then you get into *pause* and *master* negotiated bits as well. It
> > gets really hard to simplify this well.
>
> Yeah, I'm not sure where those would go. But it might be worth some
> thought before falling back on ye olde 2 dozen knobs.
>
>
Hmm... maybe. But the reality is that under normal circumstances users
*shouldn't* be touching these. The values need to be accessible for
sites that still insist on doing the stupid thing. But we really really
should not be encouraging users to do this tuning.
So maybe the nice friendly presentation doesn't need to be here. Maybe
it doesn't need to be in the "default" output at all. (Whatever that
means.)
AFAICT, the sites that tune these values *usually* have some harebrained
idea that turning off autonegotiation and forcing a fixed speed/duplex
setting is a good idea.
MAYBE, we can provide a short cut for these users in the UI... e.g.
"force-link-speed-duplex" magic property or somesuch.
For example, the output could show:
LINK SPEED DUPLEX MODE
bge0 1G full autonegotiated
hme0 100M half forced
Users who want the full control, as well as the full output, could
access the properties directly.
Thank God they finally required full-duplex and autonegotiation for 10G.
Thoughts?
-- Garrett
