LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lada Podivin <lada.podivin@gmail.com>
To: LiuMing <eemingliu@hotmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: ppc405ex + gigabit ethernet
Date: Wed, 1 Jul 2009 13:24:41 +0200	[thread overview]
Message-ID: <e35801cc0907010424l66a7c4dem6f3f363c3b194ff4@mail.gmail.com> (raw)
In-Reply-To: <COL107-W41E84129BE81739BC96295B22E0@phx.gbl>

[-- Attachment #1: Type: text/plain, Size: 2167 bytes --]

Thank you for your reply!
Yes, I agree the CPU is the bottleneck. But I have performed more tests with
the netperf tool and results seem strange to me. If I send 800 B of data,
the resulting speed is aproximately 100 Kb/s. On the other hand, If I try to
send 32KB chunk of data with jumbo frames turned on, resulting speed is
about 600 Kb/s (300-400 without jumbo frames). My ppc405ex runs at 600 MHz.

So it seems that it is definetely better idea to call sendto() less
frequently with bigger amounts of data, than to call it more often with
smaler amounts. Is it because smaller data means more frequent user
space/kernel space switching? Or is it network related issue?

Thanks!

Best,
Lada

2009/7/1 LiuMing <eemingliu@hotmail.com>

>  Hi,
> According to our experience on PPC405 + Gigabit Enet, your result is
> already very reasonable. For UDP transmission, it can be around 400 Kb/s
> because of the CPU bottleneck (in our case 300 MHz ppc405). If you want
> to further improve it, a faster CPU is needed to process the TCP/IP stack,
> or you may buy commercial TCP/IP stack rather than using the free Linux one.
>
>
> BR
> Ming
>
> ------------------------------
> Date: Tue, 30 Jun 2009 15:58:53 +0200
> Subject: ppc405ex + gigabit ethernet
> From: lada.podivin@gmail.com
> To: linuxppc-dev@ozlabs.org
>
>
> Hi,
>
> I benchmarked performance of my network, which contains ppc405EX (Kilauea
> board, kernel 2.6.30 from Denx) connected with a linux desktop via gigabit
> ethernet. I used the netperf tool:
>
> netperf -t UDP_STREAM -H 192.168.1.1 -- -m 32768
>
> So I was sending UDP packets to the desktop. The resulting speed was about
> 370 Kb/s. I tried to send the packets to several different computers - with
> the same result. So the ppc board is the bottleneck in this case.
>
> Is there any possibility to improve the gigabit capabilities of the
> ppc405EX? Is there anyone who achieved a better performance with ppc4xx
> boards?
>
> Thanks!
>
> Best,
> Lada Podivin
>
>
> ------------------------------
> 立刻下载 MSN 保护盾,保障 MSN 安全稳定! 现在就下载! <http://im.live.cn/safe/>
>

[-- Attachment #2: Type: text/html, Size: 2645 bytes --]

  reply	other threads:[~2009-07-01 11:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 13:58 ppc405ex + gigabit ethernet Lada Podivin
2009-07-01 10:19 ` LiuMing
2009-07-01 11:24   ` Lada Podivin [this message]
2009-07-01 12:56     ` Lada Podivin
2009-07-01 13:26     ` john.p.price
2009-07-02 17:50     ` LiuMing
2009-07-03  8:22       ` Lada Podivin
2009-07-01 13:25   ` Cote, Sylvain
2009-07-03  9:09     ` Lada Podivin
2009-07-06 16:56       ` Feng Kan
2009-07-01 12:37 ` Detlev Zundel

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=e35801cc0907010424l66a7c4dem6f3f363c3b194ff4@mail.gmail.com \
    --to=lada.podivin@gmail.com \
    --cc=eemingliu@hotmail.com \
    --cc=linuxppc-dev@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