> More Info on this is available by emailing me, unless this problem can get
> fixed, I will have to pull the linux installed servers and replace with
> FreeBSD 4.0, bacause I have tested FreeBSD and it worked out of the box at
> about the same speed talking to the Sparc, as 2 sparcs talking to each
> other, about 8-9MB/sec
I can talk to Solaris boxes fine with 2.2.x. Everything I hear sounds more
like misnegotiation of duplex and error problems even now.
> 5 packets were dropped by Linux and had to be re-transmitted. This
> contributed to about 30% of the elapsed time. Looking at the traces in
> detail, the receiver isn't using multiple ACKS to indicate a dropped
[We use multiple acks] Not having acks implies we never saw the packets
in the first place, which means they didnt get through. That indicates
that either the switch cabling card or card-driver got involved - hence
duplex issues and the like.
> Case 2)
>
> The Sun had to slow down and wait for the Linux box to empty the
> receive window 4451 times. This accounted to about 20% of the elapsed
> time. It indicates the efficiency of the Linux TCP stack is poor when
> emptying data. A faster CPU would help.
Actually its very good, but it depends on application space to be able to
handle large amounts of data fast, and that can be an application issue.
What to me is most interesting is - why did a chunk of packets go walkies.
What rev of the eepro100 driver are you using ?
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
