All of lore.kernel.org
 help / color / mirror / Atom feed
From: jaypee@hotpop.com
To: Clem Taylor <clem.taylor@gmail.com>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re: Au1550 ethernet throughput low
Date: Fri, 15 Jul 2005 08:21:38 +0000	[thread overview]
Message-ID: <1121415711l.5178l.3l@cavan> (raw)
In-Reply-To: <ecb4efd1050714171318ce81aa@mail.gmail.com> (from clem.taylor@gmail.com on Fri Jul 15 01:13:29 2005)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On 15/07/05 01:13:29, Clem Taylor wrote:
> The source I'm using originated from http://www.linux-mips.org/. It
> was checked out from the head of
> ':pserver:cvs@ftp.linux-mips.org:/home/cvs' on 2005.03.18. At the time
> of checkout, the linux-mips tree was missing a 2.6.11 tag. The closest
> tag was linux_2_6_11_rc5, but the code is 2.6.11.

Mine was checked out at the latest was 2.6.11 rc3.

> Yeah, UDP is running at near line rate, but it does consume a bunch of
> CPU. I'm running our 1550s at 492MHz, but I have to run the memory at
> 123MHz (DDR). I just ran the test again, here's what ttcp said:
> 

Same here expect memory is at 166

> udp recv on au1550
> ttcp -u -r -s -n 16384 -l 32768 -A 32768 -v -b 262144 -f M
> ttcp-r: buflen=32768, nbuf=16384, align=32768/0, port=5001,
> sockbufsize=262144  udp
> ttcp-r: 536608768 bytes in 44.72 real seconds = 11.44 MB/sec +++
> ttcp-r: 536608768 bytes in 17.41 CPU seconds = 29.39 MB/cpu sec
> ttcp-r: 16378 I/O calls, msec/call = 2.80, calls/sec = 366.21
> ttcp-r: 0.1user 17.2sys 0:44real 38% 0i+0d 0maxrss 0+7pf 16344+13csw
> 

That looks ok though (Well it would be good enough for my application).

Yours is using ~30% cpu to send 100Mbps.
Mine is using 100% to send 66Mbps.

I've just checked out and  merged the latest CVS.
There were a few compile problems but I'll iron them out today and see  
if that solves the problem. It is encouraging that someone has this
working though.

Thanks again

- -- 
mailto:jaypee@hotpop.com
http://www.jaypee.org.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFC13IfZDxnKy3oOpYRAtrpAKDXFwbVpxD0c4g6aWvknTrzYddLMQCdFmvP
m8mDpiQYKerMjxJr9YhH/lg=
=qDeX
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-07-15  8:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-13 16:00 Au1550 ethernet throughput low jaypee
2005-07-14 15:02 ` Matej Kupljen
2005-07-14 15:06   ` Pete Popov
2005-07-14 15:15   ` jaypee
2005-07-15  0:13     ` Clem Taylor
2005-07-15  8:21       ` jaypee [this message]
2005-07-15  9:17         ` Bruno Randolf
2005-07-18  9:57           ` jaypee
2005-07-18 12:56             ` Dan Malek
2005-07-18 13:41               ` jaypee
     [not found]             ` <ecb4efd105071809082628bb27@mail.gmail.com>
2005-07-18 17:25               ` jaypee
  -- strict thread matches above, loose matches on Subject: below --
2005-07-14  5:02 Singh, Ajay
2005-07-14  5:02 ` Singh, Ajay
2005-07-14 13:52 ` jaypee

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=1121415711l.5178l.3l@cavan \
    --to=jaypee@hotpop.com \
    --cc=clem.taylor@gmail.com \
    --cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.