Gianfar is slower than fcc_enet on MPC8541 ???
Laurent Lagrange
lagrange at fr.oleane.com
Fri Feb 24 04:28:40 EST 2006
Hi everybody,
Sorry to reply so late. I was out of office.
I tried the below Andy's idea. It works fine.
It is my TCP clients which now slow the traffic.
But I don't know why the default timeouts are so high.
If the traffic is high, the timeout does not fire.
If the traffic is low, the timeout seems too long (???).
Thanks all for your ideas and works.
Best regards
Laurent
> De la part de Andy Fleming
> Envoye : mar. 14 fevrier 2006 18:37
> A : Laurent Lagrange
> Cc : linuxppc-embedded at ozlabs.org
> Objet : Re: Gianfar is slower than fcc_enet on MPC8541 ???
>
> My guess is that you are measuring latency. By default, interrupt
> coalescing is on, and used to be set to very poor default
> values. In drivers/net/gianfar.h, change the defaults to look like this:
>
> #define DEFAULT_TX_COALESCE 1
> #define DEFAULT_TXCOUNT 16
> #define DEFAULT_TXTIME 4
>
> #define DEFAULT_RX_COALESCE 1
> #define DEFAULT_RXCOUNT 16
> #define DEFAULT_RXTIME 4
>
> The problem was that the timeout was quite long, so a small number of
> packets would have to wait a whole millisecond (or more!) to get
> processed. While it wouldn't affect bandwidth tests, which send many
> packets, it would affect a simple test like ping.
>
> If you don't feel like recompiling the kernel, you can use ethtool to
> change the timeout values.
More information about the Linuxppc-embedded
mailing list