--- bge.7d.orig Fri Sep 21 12:26:06 2007 +++ bge.7d Tue Sep 25 09:58:30 2007 @@ -81,7 +81,7 @@ o Maximum SDU is 1500 (ETHERMTU - defined in ). - o Minimum SDU is 0. + o Minimum SDU is 68. o DLSAP address length is 8. @@ -136,7 +136,6 @@ Devices bge(7D) - as the highest common denominator supported by both link partners. Because the bge device supports all modes, the effect is to select the highest throughput mode supported by @@ -143,19 +142,13 @@ the other device. Alternatively, you can set the capabilities advertised by - the bge device using ndd(1M). The driver supports a number + the bge device using dladm(1M). The driver supports a number of parameters whose names begin with adv_ (see below). Each of these parameters contains a boolean value that determines - whether the device advertises that mode of operation. The - adv_pause_cap indicates whether half/full duplex pause is - advertised to link partner. And the adv_asym_pause_cap can - be set to advertise to link partner that asymmetric pause is - desired. In addition, bge uses adv_100T4_cap to advertise - its 100T4 capability. The adv_autoneg_cap parameter controls - whether autonegotiation is performed. If adv_autoneg_cap is - set to 0, the driver forces the mode of operation selected - by the first non-zero parameter in priority order as listed - below: + whether the device advertises that mode of operation. + If adv_autoneg_cap is set to 0, the driver forces the mode of + operation selected by the first non-zero parameter in priority + order as listed below: (highest priority/greatest throughput) adv_1000fdx_cap 1000Mbps full duplex @@ -170,8 +163,8 @@ For example, to prevent the device 'bge2' from advertising gigabit capabilities, enter (as super-user): - # ndd -set /dev/bge2 adv_1000hdx_cap 0 - # ndd -set /dev/bge2 adv_1000fdx_cap 0 + # dladm set-linkprop -p adv_1000hdx_cap=0 bge2 + # dladm set-linkprop -p adv_1000fdx_cap=0 bge2 All capabilities default to enabled. Note that changing any @@ -180,52 +173,43 @@ newly changed capabilities. The current settings of the parameters may be found using - ndd -get. In addition, the driver exports the current state, - speed, duplex setting, and working mode of the link via ndd + dladm show-ether. In addition, the driver exports the current state, + speed, duplex setting, and working mode of the link via kstat parameters (these are read only and may not be changed). For example, to check link state of device bge0: - # ndd -get /dev/bge0 link_status - 1 - # ndd -get /dev/bge0 link_speed - 100 + # dladm show-ether -x bge0 + LINK PTYPE STATE AUTO SPEED-DUPLEX PAUSE + bge0 current up yes 1G-f bi + -- capable -- yes 1G-fh,100M-fh,10M-fh bi + -- adv -- yes 1G-fh bi + -- peeradv -- yes 1G-f bi + The output above indicates that the link is up and running + at 1Gbps full-duplex with its rx/tx direction pause capa- + bility. -SunOS 5.11 Last change: 14 Jun 2007 3 + To extract link state information for the same link using kstat: + # kstat bge:0:mac:link_state + module: bge instance: 0 + name: mac class: net + link_state 1 - - - -Devices bge(7D) - - - - # ndd -get /dev/bge0 link_duplex - 2 - # ndd -get /dev/bge0 link_rx_pause - 1 - # ndd -get /dev/bge0 link_tx_pause - 1 - - - The output above indicates that the link is up and running - at 100Mbps full-duplex with its rx/tx direction pause capa- - bility. In addition, the driver exports its working mode by - loop_mode. If it is set to 0, the loopback mode is disabled. - The default MTU is 1500. To enable Jumbo Frames support, you can configure the bgedriver by defining the default_mtu pro- - perty in driver.conf(4) to greater than 1500 bytes (for - example: default_mtu=9000). Note that the largest jumbo size - supported by bge is 9000 bytes. Additionally, not all bge- - derived devices currently support Jumbo Frames. The follow- - ing devices support Jumbo Frames up to 9KB: BCM5700, 5701, - 5702, 5703C, 5703S, 5704C, 5704S, 5714C, 5714S, 5715C and - 5715S. Other devices currently do not support Jumbo Frames. + perty via dladm(1m) or in driver.conf to greater than + 1500 bytes (for example: default_mtu=9000). Note that the + largest jumbo size supported by bge is 9000 bytes. + Additionally, not all bge-derived devices currently support + Jumbo Frames. The following devices support Jumbo Frames + up to 9KB: BCM5700, 5701, 5702, 5703C, 5703S, 5704C, 5704S, + 5714C, 5714S, 5715C and 5715S. Other devices currently do not + support Jumbo Frames. + FILES /kernel/drv/bge* 32-bit ELF kernel module. (x86)