From: "Laurent Lagrange" <lagrange@fr.oleane.com>
To: "'Pantelis Antoniou'" <pantelis.antoniou@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Gianfar is slower than fcc_enet on MPC8541 ???
Date: Tue, 14 Feb 2006 17:14:59 +0100 [thread overview]
Message-ID: <000201c63181$cf2c3180$5201a8c0@GEG2400> (raw)
In-Reply-To: <449c76a00602140728g3a9eb46sd70f23b894c4b96@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2386 bytes --]
Hi Pantelis,
Thanks for the express reply.
I know that what I say seems incredible. But I don't understand what NAPI
does.
My measure is very simple. I display a message on the client when 1000
exchanges are done.
I already check the ifconfig stats on the board after some seconds.
The measures seems the same with or without NAPI.
More details ?
Thanks again
Laurent
-----Message d'origine-----
De : Pantelis Antoniou [mailto:pantelis.antoniou@gmail.com]
Envoyé : mar. 14 février 2006 16:29
À : Laurent Lagrange
Cc : linuxppc-embedded@ozlabs.org
Objet : Re: Gianfar is slower than fcc_enet on MPC8541 ???
Hi Laurent,
I found that pretty hard to believe.
What are you measuring exactly?
Speed of replies? If so it's explainable since the TSECs use
NAPI.
Regards
Pantelis
On 2/14/06, Laurent Lagrange <lagrange@fr.oleane.com> wrote:
Hello,
I work on a cutom MPC8541 board with Linux 2.6.9.
The kernel activates the L1 cache (instructions and data)
and the L2 cache (entirely used as cache and not as sram).
I configure
1 FCC (FCC1),
2 TSECs with or without NAPI (no effect) but without stashing in L2
sram.
All PHYs are automatically configured in 100MB full duplex.
eth0: Gianfar Ethernet Controller Version 1.1, 00:10:cd:48:48:e0
eth0: Running with NAPI disabled
eth0: 64/64 RX/TX BD ring size
eth1: Gianfar Ethernet Controller Version 1.1, 00:10:cd:48:48:e1
eth1: Running with NAPI disabled
eth1: 64/64 RX/TX BD ring size
eth2: FCC ENET Version custom, 00:10:cd:48:48:e2
Then I launch 3 simple TCP servers, one on each ports.
From remote machines I runs 3 TCP clients.
The client sends messages of 1000 bytes,
The server receives and echoes the message
The client receives the echoed message, check the content
and sends a new message again.
The result is that the 2 TSECs are 2 times slower than the FCC.
If I run a "top" application on the board, I use less than 10% of the
CPU
Each port consumes about 1/3 of the CPU.
Any idea on how to configure the gianfar driver ?
Thanks
Laurent
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
[-- Attachment #2: Type: text/html, Size: 5369 bytes --]
next prev parent reply other threads:[~2006-02-14 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 15:26 Gianfar is slower than fcc_enet on MPC8541 ??? Laurent Lagrange
2006-02-14 15:28 ` Pantelis Antoniou
2006-02-14 16:14 ` Laurent Lagrange [this message]
2006-02-14 16:17 ` Pantelis Antoniou
2006-02-14 16:42 ` Vitaly Bordug
2006-02-14 17:36 ` Andy Fleming
[not found] <000701c6389b$49e30960$5201a8c0@GEG2400>
2006-02-23 17:28 ` Laurent Lagrange
2006-02-23 20:08 ` Andy Fleming
2006-02-27 10:03 ` Laurent Lagrange
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='000201c63181$cf2c3180$5201a8c0@GEG2400' \
--to=lagrange@fr.oleane.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=pantelis.antoniou@gmail.com \
/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