Garrett D'Amore wrote:
[EMAIL PROTECTED] wrote:
On (06/18/07 11:35), [EMAIL PROTECTED] wrote:
A link speed of "1000" is meaningless, plus it does not seem
to scale down to modem speed. Either report the full number
(10000000, 10000000000) or abbreviate it meaingfullly:
10M, 10G, etc - the default output from "zfs list" is an
example of how this can be done:
right, that was just tentative output. It should be abbreviated by the
appropriate {M,G,..} clarifications as you suggest.
The very idea of directly setting the link-speed and link-duplex is
one that I'm uncomfortable with. This hides important details, such
as whether the mode is forced, or is it an 802.3u negotiated speed?
I'm sure that solving this is just a simple matter of code...
It also removes quite a bit of control. For example, it may be
worthwhile to support the idea of autonegotiation, but disallow
certain configurations.
Good idea.
I hate the fact that folks feel the need to regularly force these link
parameters, but that's a different problem. I do think that as long
as we are offering control, it needs to be full control ... i.e. by
directly allowing one to configure the MII anar bits. (via
adv_cap_100fdx, etc.)
But it lets you work around instances when there are autoneg.
issues that prevent it from working, whether it be noisey cable
or bad bad hardware (switch/nic) at the other end.
I'd suggest having a command line option specific to
returning extended output, so you can have:
# dladm describe link_speed bge1
capabilities: 10M, 100M, 1G
possible: 10M, 100M
man page: bge(7)
blah blah blah blah...
hm. So you are suggesting that we should have a new command line
option. I have no preferences myself- I'd like to hear other thoughts..
It should probably dladm help.... to be consistent with other
utilities. See the "zoneadm help" command for more ideas.
Yes, that'd work too.
Darren
_______________________________________________
networking-discuss mailing list
[email protected]
