eXpressDSP Compliant

bf3Net
is Compliant with eXpressDSP and the
TI Algorithm Standard

Outside of
North America ?

Windmill Innovations


bf3Net TCP/IP Performance Figures

To give an impression of the system performance of the bf3Net TCP/IP Protocol Stack,
Windmill Innovations measures and publishes performance figures for reference target
hardware, grouped by Ethernet and Point-to-Point Protocol (PPP) as datalink communication layer. For a detailed description of the parameters and the measurement procedures, please click here.

Ethernet datalinks

The chart below displays the data throughputs and (program/data) memory requirements of the bf3Net TCP/IP Protocol Stack for communication through Ethernet datalinks.

 
Target Board
 Unit
Parameter F2812 NWK C5416 DSK C5510 DSK C6416 DSK DM641 DSK C6713 DSK
CPU frequency (1) 150 160 200 600 600 150 MHz
Communications interface (1) NWK WI WI WI EMAC WI -
               
Max. TCP rx throughput, no-copy - 37.7 35.2 50.6 71.9 17.4 Mbit/s
Max. TCP rx throughput, copy 2.5 17.8 19.3 33.8 48.0 11.4 Mbit/s
Max. TCP tx throughput 2.3 13.4 14.8 25.4 35.9 8.5 Mbit/s
Code efficiency - TCP rx, no-copy - 2.6 2.0 2.3 2.3 3.9 CPU cycles/bit
Code efficiency - TCP rx, copy - 5.9 4.2 3.7 3.7 6.7 CPU cycles/bit
Code efficiency - TCP tx - 7.4 5.3 4.6 4.6 8.4 CPU cycles/bit
Max. UDP tx througput - - - - 60.0 - Mbit/s
Code efficiency - UDP tx - - - - 2.4 - CPU cycles/bit
Program Memory (min.) 18.1 35.6 27.9 88.9 88.9 99.8 kByte (2)
Program Memory (max.) 30.1 61.9 49.4 50.7 50.7 57.1 kByte (2)
Data Memory (typical) 12.0 12.0 12.0 16.0 16.0 16.0 kByte (2)

(1) WI: Windmill Innovations 100BaseTx Ethernet Daughtercard; EMAC: DM64x-internal Ethernet MAC; NWK: bf3Net F2812 Networking Kit.
(2) For C2800 and C5000 platforms (word-addressable CPU) the unit is kWord.

Point-to-Point Protocol datalinks

The chart below displays the data throughputs and (program/data) memory requirements of the bf3Net TCP/IP Protocol Stack for communication through Point-to-Point Protocol (PPP) datalinks.

 
Target Board
 Unit
Parameter C5402 DSK 54CST
EVM		 C6713 DSK      
CPU frequency (1) 100 118 150       MHz
Communications interface (1) V.90 CST V.90       -
               
Max. TCP rx throughput, no-copy n.a. - -       kBytes/s
Max. TCP rx throughput, copy 4.9 - -       kBytes/s
Max. TCP tx throughput 4.9 - -       kBytes/s
Code efficiency - TCP rx, no-copy n.a. - -       CPU cycles/bit
Code efficiency - TCP rx, copy 120 - -       CPU cycles/bit
Code efficiency - TCP tx 120 - -       CPU cycles/bit
Program Memory (min.) 42.3 42.3 -       kByte (2)
Program Memory (max.) 66.6 66.6 -       kByte (2)
Data Memory (typical) 11 11 -       kByte (2)

(1) V.90: RS-232 V.90 voiceband modem; CST: 54CST on-chip modem algorithms.
(2) For C5000 platforms (word-addressable CPU) the unit is kWord.

Performance figure parameters and measurement procedures

The bf3Net performance figures are obtained as follows:

Communication Throughput:

The communication throughput figures are measured in MBit/s or kByte/s at TCP level. The following parameters are measured:

Max. TCP receive (rx) throughput, no-copy:

The mamixum no-copy TCP receive throughput is measured by sending TCP packets with TCP packet generator to a DSP target board running bf3Net, or by downloading a large file from a Microsoft Internet Information Server 5.0 on the local network. Received data is immediately discarded. While this parameter gives an impression of the maximum achievable throughput of the communications interface, it has little or no meaning for any practical purposes. Windmill Innovations provides this number as reference only.

Max. TCP receive (rx) throughput, copy:
The mamixum copy TCP receive throughput is measured by sending TCP packets with TCP packet generator to a DSP target board running bf3Net, or by downloading a large file from a Microsoft Internet Information Server 5.0 on the local network. Received data is copied to an application buffer.

Max. TCP transmit (tx) throughput:
The mamixum TCP transmit throughput is measured by sending chunks of data to an IP host on the local network. Transmitted data is copied from an application buffer.

Max. UDP transmit (tx) throughput:
The mamixum UDP transmit throughput is measured by sending UDP-datagrams to an IP host on the local network. Transmitted data is copied from an application buffer.
   
Code Efficiency Factors:

Across the entire bandwidth, the bf3Net TCP/IP Protocol Stack approximately displays a linear relationship between data throughput and processor load. This relationship is expressed numerically with the so-called code efficiency factors, in "CPU cycles per transferred bit".

Using the code efficiency factor, a faithful estimation of the CPU load at a certain TCP bitrate can be made, by multiplying the code efficiency factor with the TCP bitrate. The code efficiency figures are provided for each communication throughput parameter (see above):

Code efficiency - TCP receive (rx), no-copy:
Multiply this factor with the TCP bitrate to obtain the CPU load in a no-copy situation.

Code efficiency - TCP receive (rx), copy:
Multiply this factor with the TCP bitrate to obtain the CPU load when the received data is copied to the application buffer.

Code efficiency - TCP transmit (tx):
Multiply this factor with the TCP bitrate to obtain the CPU load when data is transmitted by the bf3Net TCP/IP Protocol Stack.

Code efficiency - UDP transmit (tx):
Multiply this factor with the UDP bitrate to obtain the CPU load when UDP datagrams are transmitted by the bf3Net TCP/IP Protocol Stack.
   
Memory Requirements:

The bf3Net TCP/IP Protocol Stack is highly modular and configurable. To give an indication of the memory requirements, the following figures are provided:

Program memory (min.):
The minimum program memory requirements (footprint) are measured in code space words and/or bytes for the minimum configuration of the bf3Net TCP/IP Protocol Stack. Typically, this means that only UDP is included as transport layer protocol, and that all other optional modules are excluded.

Program memory (max.):
The maximum program memory requirements (footprint) are measured in code space words and/or bytes for the maximum configuration of the bf3Net TCP/IP Protocol Stack. This implies that all protocol and debug modules are included.

Data memory (typical):
The amount data memory required for operation of the bf3Net TCP/IP Protocol Stack depends on the selected configuration. As a rough indication, the data memory required for a bf3Net configuration with three TCP sockets is provided in data space words and/or bytes.

   

Please contact us if you need more detailed results.
     

 

Search | Home | Site Map | News | Sales | Technical Support | Contact Info | DSP | Imaging | FPGA | FireWire | Ethernet

Traquair reserves the right to change specifications without notice.
Copyright © 2005 All Rights Reserved. All trademarks acknowledged. Report problems to the webmaster.
This site is optimized for viewing with Internet Explorer 6.0+ and Netscape 7.0+