From: Wolfgang Denk <wd@denx.de>
To: "sun-zj" <sun-zj@tdk-tech.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: eth0 memory sqeeze
Date: Sun, 01 Feb 2004 10:30:38 +0100 [thread overview]
Message-ID: <20040201093043.CB4F6C108D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sun, 01 Feb 2004 15:17:15 +0800." <20040201072141.70E12430AB@denx.de>
In message <20040201072141.70E12430AB@denx.de> you wrote:
>
> I am using the Linux On MPC860T as your instructions. Now I want to do a
> performance test
> of PPC with linux. Our board is FADS and MPC860T.
> I use the kernel from denx website(2.4.4). the test
> program is iperf.
> When I use the iperf on PPC+linux as server, I start the iperf on PC as
> client. I choose the options -n 300M -P 120 which mean I want to open 120
> threads each one open a TCP connection and each preparing to send 300MB
> data. On PPC+linux I get the following output.
> "eth0: Memory squeeze,dropping packet"
> "__alloc_pages: 0-order allocation failed (gfp=0x20/0)
> I guess that the data to be processed exceeds the capabilities of PPC+linux.
No, it does not exceed the capabilities of Linux or PowerPC, but that
of your specific system.
> I wonder whether this could be solved by Linux ???
Add more memory to your system.
Best regards,
Wolfgang Denk
--
See us @ Embedded World, Nuremberg, Feb 17 - 19, Hall 12.0 Booth 440
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Bus error -- driver executed.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2004-02-01 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040201072141.70E12430AB@denx.de>
2004-02-01 9:30 ` Wolfgang Denk [this message]
2004-02-01 7:17 eth0 memory sqeeze sun-zj
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=20040201093043.CB4F6C108D@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=sun-zj@tdk-tech.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;
as well as URLs for NNTP newsgroup(s).