From: "Laurent Lagrange" <lagrange@fr.oleane.com>
To: "'Andy Fleming'" <afleming@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Gianfar is slower than fcc_enet on MPC8541 ???
Date: Mon, 27 Feb 2006 11:03:20 +0100 [thread overview]
Message-ID: <002601c63b85$0b2e9850$5201a8c0@GEG2400> (raw)
In-Reply-To: <9A05AF34-3A14-4D64-9EDF-81D7C3C315FE@freescale.com>
Hello Andy,
> The answer there is simple: stupidity!
The word is too hard, just say forgetting :-)
Thanks again
Laurent
> -----Message d'origine-----
> De : Andy Fleming [mailto:afleming@freescale.com]
> Envoye : jeu. 23 fevrier 2006 21:08
> A : Laurent Lagrange
> Cc : linuxppc-embedded@ozlabs.org; vbordug@ru.mvista.com;
> pantelis.antoniou@gmail.com
> Objet : Re: Gianfar is slower than fcc_enet on MPC8541 ???
>
>
>
> On Feb 23, 2006, at 11:28, Laurent Lagrange wrote:
>
> > Hi everybody,
> >
> > 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 (???).
>
> The answer there is simple: stupidity! :) I just didn't carefully
> test the values for performance when I chose them. I probably also
> did the math wrong, because I was more concerned about seeing if it
> worked at all. It's also possible it got set that way to see a
> measurable difference to prove it was working, and then got left as
> the default. Rest assured, there was not a deliberate reason. We
> submitted a patch once this performance issue was discovered.
>
>
>
>
>
next prev parent reply other threads:[~2006-02-27 9:57 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 ` Gianfar is slower than fcc_enet on MPC8541 ??? Laurent Lagrange
2006-02-23 20:08 ` Andy Fleming
2006-02-27 10:03 ` Laurent Lagrange [this message]
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='002601c63b85$0b2e9850$5201a8c0@GEG2400' \
--to=lagrange@fr.oleane.com \
--cc=afleming@freescale.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;
as well as URLs for NNTP newsgroup(s).