>>>>> "JB" == Jesse Brandeburg <[EMAIL PROTECTED]> writes:
JB> Flow control should be supported, but it is autonegotiated at link
JB> time. How do you know it isn't on?
Thanks for the response. I'm going on two pieces of information:
1) The switch indicates that flow control is not on
2) UDP NFS is horribly slow and the server sees many ICMP reassembly
timeouts.
JB> what does ethtool -d ethX show?
Without FlowControl:
ethtool -d eth0:
Receive flow control: disabled
Transmit flow control: disabled
(full output at http://www.math.uh.edu/~tibbs/ethtool.txt)
ethtool -a eth0:
Pause parameters for eth0:
Autonegotiate: on
RX: off
TX: off
mii-tool -v eth0 (I know it can't handle gigabit):
eth0: negotiated 100baseTx-FD, link ok
product info: vendor 00:50:43, model 2 rev 3
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
With FlowControl=3,3;
ethtool -d eth0:
Receive flow control: enabled
Transmit flow control: enabled
ethtool -a eth0:
Pause parameters for eth0:
Autonegotiate: on
RX: on
TX: on
mii-tool -v eth0:
eth0: negotiated 100baseTx-FD flow-control, link ok
product info: vendor 00:50:43, model 2 rev 3
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
So it looks like it's on (although I don't understand the
"capabilities" line and why it differs). But (and here's the big
deal) the switch does not recognize that flow control is on. It still
shows "None" in the "Flow Control Status" column. UDP NFS performance
is still abysmal. (Maybe I'm wrong in thinking that flow control will
help this.) By abysmal, I mean it's about thirty times slower than
when I force things to drop to 100mbit.
JB> Did you try FlowControl=3,3 (two adapters)
Actually I didn't, but I just tried and it makes no difference. I'm
only dealing with the first device, but I suppose the OS could switch
things around.
JB> This is a silly question, but is the driver UP, like with 'ip l
JB> set dev ethX up'
Yes, it's up; that's how I'm logged into the machine.
JB> As for debugging the autoneg process, there isn't much to do with
JB> that, as it is all run by hardware, we just set up registers and
JB> reset the phy.
That's what I figured. Frankly, I'm tempted to blame the switch
here. Testing under Windows (which I've yet to do) should shine more
light on this.
One other question I have: in e1000.txt the FlowControl parameter is
documented as using the EEPROM for default values. Does anyone where
in the ethtool -e output I can see the default FlowControl values? I
don't have the fortitude to poke around there, but I'm willing to try
if someone can tell me what bytes to alter.
- J<
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
