TTCP on Embedded Planets EP5200

Joel Sherrill joel.sherrill at oarcorp.com
Thu Jul 12 19:15:23 UTC 2007


Hi,

I searched the RTEMS archives and no one seems
to have posted ttcp numbers in a long time.
So I thought I would give Thomas Doerfler a
public pat on the back for the truly
splendid performance I measured from his
driver.

This was on a dedicated network with the
host being a 2.0 Ghz dual core laptop running
Fedora 7.  The target was an EP5200 which is
a 400 Mhz MPC5200B with an on-CPU NIC.

 >>> ttcp -t -s 192.168.1.210
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001  tcp  -> 
192.168.1.210
ttcp-t: socket
ttcp-t: connect
ttcp-t: 16777216 bytes in 1.58 real seconds = 10385.86 KB/sec +++
ttcp-t: 2048 I/O calls, msec/call = 0.79, calls/sec = 1298.23
ttcp-t: 0.0user 1.5sys 0:01real 100% 0i+0d 0maxrss 0+0pf 0+0csw
 >>> ttcp -r -s
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001  tcp
ttcp-r: socket
ttcp-r: accept from 192.168.1.210
ttcp-r: 16777216 bytes in 1.78 real seconds = 9194.86 KB/sec +++
ttcp-r: 3499 I/O calls, msec/call = 0.52, calls/sec = 1963.67

Notice it could receive data at 94.91% of the theoretical
max and transmit at the theoretical limit of 100BaseT.

This is with the default settings of ttcp so larger buffers
might pull up the RX time.  It is also possible that the
laptop Fedora side is limited to that TX speed.  The numbers
are good enough that it really isn't worth worrying about
though. :)

Good job Thomas!!!

--joel



More information about the users mailing list