1 <!-- Copyright (C) 2003 Red Hat, Inc. -->
2 <!-- This material may be distributed only subject to the terms -->
3 <!-- and conditions set forth in the Open Publication License, v1.0 -->
4 <!-- or later (the latest version is presently available at -->
5 <!-- http://www.opencontent.org/openpub/). -->
6 <!-- Distribution of the work or derivative of the work in any -->
7 <!-- standard (paper) book form is prohibited unless prior -->
8 <!-- permission is obtained from the copyright holder. -->
12 >Performance Test</TITLE
13 ><meta name="MSSmartTagsPreventParsing" content="TRUE">
16 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
19 TITLE="eCos Reference Manual"
20 HREF="ecos-ref.html"><LINK
22 TITLE="Tests and Demonstrations"
23 HREF="net-common-tests-and-demonstrations.html"><LINK
25 TITLE="Standalone Tests"
26 HREF="net-common-standalone-tests.html"><LINK
28 TITLE="Interactive Tests"
29 HREF="net-common-interactive-tests.html"></HEAD
40 SUMMARY="Header navigation table"
49 >eCos Reference Manual</TH
57 HREF="net-common-standalone-tests.html"
65 >Chapter 36. Tests and Demonstrations</TD
71 HREF="net-common-interactive-tests.html"
85 NAME="NET-COMMON-PERFORMANCE-TEST">Performance Test</H1
93 CLASS="PROGRAMLISTING"
100 > - data forwarding program for performance test</PRE
109 part of the standard performance test we use. The other parts are
117 To make these (under LINUX) cd to the tests source directory in
118 the eCos repository and type “<TT
120 >make -f make.linux</TT
122 this should build <TT
130 >The LINUX program “<TT
134 data to the target. On the target, “<TT
138 it onwards to “<TT
142 on LINUX. So the target must receive and send on all the data that <TT
146 it; the time taken for this is measured and the data rate is calculated.</P
148 >To invoke the test, first start <TT
152 the target board and wait for it to become quiescent - it will report
153 work to calibrate a CPU load which can be used to simulate real
154 operating conditions for the stack.</P
156 >Then on your LINUX machine, in one terminal window, invoke <TT
160 it the IP address (or hostname) of one interface of the target board.
161 For example “<TT
163 >tcp_sink 10.130.39.66</TT
169 will print something like “<TT
172 from 10.130.39.13:1143</TT
177 correctly invoked.</P
179 >Next, in another LINUX terminal window, invoke <TT
183 giving it the IP address (or hostname) of an interface of the target
184 board, and optionally a background load to apply to the target while
185 the test runs. For example, “<TT
189 >” to run the test with no
190 additional target CPU load, or “<TT
194 >” to load it up to 85% used.
195 The target load must be a multiple of 5. <TT
199 the target will print something like “<TT
202 connection from 194.130.39.13:1144</TT
204 tcp_source is correctly invoked.</P
206 >You can connect tcp_sink to one target interface
207 and tcp_source to another, or both to the same interface.
208 Similarly, you can run <TT
215 the same LINUX machine or different ones. TCP/IP and ARP
216 look after them finding one another, as intended.</P
224 CLASS="PROGRAMLISTING"
231 > - network characterization master
238 > - network characterization slave</PRE
243 >These tests talk to each other to measure network performance.
244 They can each run on either a test target or a LINUX host computer
245 given some customization to your local environment. As provided, <TT
249 run on the test target, and <TT
253 be run on a LINUX host, and be given the test target's
254 IP address or hostname.</P
256 >The tests print network performance for various packet sizes
257 over UDP and TCP, versus various additional CPU loads on the target.</P
266 CLASS="PROGRAMLISTING"
285 are additional forms which support both IPv4 and IPv6 addressing.</P
292 SUMMARY="Footer navigation table"
303 HREF="net-common-standalone-tests.html"
321 HREF="net-common-interactive-tests.html"
331 >Standalone Tests</TD
337 HREF="net-common-tests-and-demonstrations.html"
345 >Interactive Tests</TD