LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Laurent Lagrange" <lagrange@fr.oleane.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: RE: Gianfar is slower  than fcc_enet on MPC8541 ???
Date: Thu, 23 Feb 2006 18:28:40 +0100	[thread overview]
Message-ID: <000001c6389e$980f0ff0$5201a8c0@GEG2400> (raw)
In-Reply-To: <000701c6389b$49e30960$5201a8c0@GEG2400>

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@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.
 

       reply	other threads:[~2006-02-23 17:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000701c6389b$49e30960$5201a8c0@GEG2400>
2006-02-23 17:28 ` Laurent Lagrange [this message]
2006-02-23 20:08   ` Gianfar is slower than fcc_enet on MPC8541 ??? Andy Fleming
2006-02-27 10:03     ` Laurent Lagrange
2006-02-14 15:26 Laurent Lagrange
2006-02-14 15:28 ` Pantelis Antoniou
2006-02-14 16:14   ` Laurent Lagrange
2006-02-14 16:17     ` Pantelis Antoniou
2006-02-14 16:42       ` Vitaly Bordug
2006-02-14 17:36 ` Andy Fleming

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000001c6389e$980f0ff0$5201a8c0@GEG2400' \
    --to=lagrange@fr.oleane.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox