|
MTU size + 14 bytes.
"rx_jumbo_desc_cnt" parameter:
It is always advised to use a value of 15 or above for the module
parameter rx_jumbo_desc_cnt. At values lower than 15, it has been
observed that jumbo traffic causes the driver to hang.
forcing speed/duplex and the "auto_speed" parameter:
If the user tries to force a particular Speed/Duplex connection it must
be ensured that the "auto_speed" parameter is set equal to 0. The
default value for "auto_speed" is always 1 even when "line_speed" is
configured to auto-negotiate (0), as well as all other designated
speeds (10, 100, 1000). The reason for this parameter is to allow
the user to either auto-negotiate a particular speed (auto_speed=1)
or to force a particular speed (auto_speed=0). The examples below
show "auto_speed" used in the two scenarios (auto negotiation vs. forced).
The command to auto-negotiate 100Mbs/Half duplex:
#insmod bcm5700 line_speed=100 full_duplex=0 auto_speed=1
The command to force 100Mbs/Half duplex:
#insmod bcm5700 line_speed=100 full_duplex=0 auto_speed=0
Note: For SLES 9, instead of insmod, modprobe has to be used.
tx_flow_control and rx_flow_control parameters:
If the tx_flow_control parameter is set to 1, the resulting
behaviour for the pause transmit is best explained as follows
If auto_flow_control=0 and auto_speed=0, pause transmit is
enabled and not advertised. If auto_flow_control=0 and auto_speed=1
Pause transmit is always enabled and advertised gratuitously.
If both auto_flow_control and auto_speed are set to 1, then
阅读更多内容:<<上一页 · 1 · 2 · 3 · 4 · 5 · 6 · 7 · 8 · 9 · 下一页>>
|