Lines Matching refs:netperf
3 @setfilename netperf.info
9 netperf benchmark.
14 per the terms of the netperf source license, a copy of which can be
15 found in the file @file{COPYING} of the basic netperf distribution.
40 * Introduction:: An introduction to netperf - what it
42 * Installing Netperf:: How to go about installing netperf.
87 While not every revision of netperf will work on every platform
88 listed, the intention is that at least some version of netperf will
106 here. While it is often used by them, netperf is NOT supported via any
108 to make enhancements and modifications to netperf to suit your
110 netperf copyright. If you feel so inclined, you can send your changes
112 @email{netperf-feedback@@netperf.org,netperf-feedback} for possible
113 inclusion into subsequent versions of netperf.
115 It is the Contributing Editor's belief that the netperf license walks
122 The @email{netperf-talk@@netperf.org,netperf-talk} mailing list is
123 available to discuss the care and feeding of netperf with others who
125 netperf-talk mailing list is a closed list (to deal with spam) and you
127 @email{netperf-talk-request@@netperf.org,netperf-talk-request}.
139 netperf parameters. If you wish to set both parameters to separate
196 netperf <global> -- <test-specific>
208 styles of netperf installation. The first runs the netperf server
238 Gzipped tar files of netperf sources can be retrieved via
239 @uref{ftp://ftp.netperf.org/netperf,anonymous FTP}
242 @uref{ftp://ftp.netperf.org/netperf/experimental,experimental} subdirectory.
246 @uref{http://www.netperf.org/, NetperfPage}
248 The bits corresponding to each discrete release of netperf are
249 @uref{http://www.netperf.org/svn/netperf2/tags,tagged} for retrieval
252 @uref{http://www.netperf.org/svn/netperf2/tags/netperf-2.6.0,netperf
253 2.6.0}. Those wishing to be on the bleeding edge of netperf
255 @uref{http://www.netperf.org/svn/netperf2/trunk,top of trunk}. When
260 download netperf bits. These may be simple mirrors of the main
261 netperf site, or they may be local variants on netperf. As with
266 As a general rule, binaries of netperf and netserver are not
267 distributed from ftp.netperf.org. From time to time a kind soul or
268 souls has packaged netperf as a Debian package available via the
275 Once you have downloaded the tar file of netperf sources onto your
276 system(s), it is necessary to unpack the tar file, cd to the netperf
281 gzcat netperf-<version>.tar.gz | tar xf -
282 cd netperf-<version>
298 If the netperf configure script does not know how to automagically
302 that area, feel free to contact @email{netperf-feedback@@netperf.org}.
315 Starting with version 2.5.0, netperf began migrating most of the
316 ``classic'' netperf tests found in @file{src/nettest_bsd.c} to the
326 @email{netperf-talk@@netperf.org} or
327 @email{netperf-feedback@@netperf.org}. If that is unsuccessful, you
332 Starting with version 2.5.0, netperf includes the ``burst mode''
335 @email{netperf-talk@@netperf.org} or
336 @email{netperf-feedback@@netperf.org}. If that is unsuccessful, you
341 command with a CFLAGS and/or LIBS variable as the netperf configure
352 @code{--enable-intervals=yes} to give netperf the ability to ``pace''
353 its _STREAM tests and @code{--enable-histogram=yes} to have netperf
358 of a netperf TCP_RR test will be of the individual transaction times:
360 netperf -t TCP_RR -H lag -v 2
397 $ src/netperf -D 1.35 -H tardy.hpl.hp.com -f M
422 Those familiar with this option in earlier versions of netperf will
437 effect an automagic editing of the necessary files to have netperf
450 If the compilation of netperf or netserver happens to fail, feel free
451 to contact @email{netperf-feedback@@netperf.org} or join and ask in
452 @email{netperf-talk@@netperf.org}. However, it is quite important
460 Basically, once netperf is installed and netserver is configured as a
463 netperf
467 $ netperf
484 two executables - netperf and netserver. Generally you will only
485 execute the netperf program, with the netserver program being invoked
489 When you execute netperf it will establish a ``control connection'' to
501 control connection and combined with netperf's result for display to
525 CPU utilization in netperf is reported as a value between 0 and 100%
527 utilization, netperf will report a metric called a @dfn{service
543 indicate which mechanism was used on each of the local (netperf) and
550 The CPU utilization measurement mechanism was unknown to netperf or
551 netperf/netserver was not compiled to include CPU utilization
591 in interrupt. Since the mechanisms overlap, netperf goes through some
625 Other mechanisms included in netperf in the past have included using
633 netperf 2.4.0 and later.
643 when the system is running netperf and the ratio is used to compute
646 In the past, netperf included some mechanisms that only reported CPU
648 removed from netperf versions 2.4.0 and later because they are
668 mpstat are often based on the same mechanisms used by netperf.
677 The CPU utilization mechanisms used by netperf are ``inline'' in that
678 they are run by the same netperf or netserver process as is running
690 should not really trust CPU utilization figures reported by netperf or
695 on netperf _RR tests - path-lengths and overheads can be a significant
705 available in the netperf and netserver binaries. Essentially, it is
706 an expanded version of the usage information displayed by netperf or
719 Revision 1.8 of netperf introduced enough new functionality to overrun
727 affect nearly any and every test type of netperf. The second type are
736 netperf <global> -- <test-specific>
740 netperf <global>
744 netperf -- <test-specific>
773 This option is only present when netperf has been configure with
782 (see -P) output of netperf.
807 file @file{/tmp/netperf.debug}. [Default: no debugging output]
811 This option is only available when netperf is configured with
812 --enable-demo=yes. When set, it will cause netperf to emit periodic
843 netperf removed that restriction, creating a temporary file as
849 This option causes netperf to display its ``global'' usage string and
859 will set the name of the remote system to ``linger'' and tells netperf to
902 asks netperf to be 99% confident that the measured mean values for
908 If classic netperf test calculates that the desired confidence
913 netperf -H tardy.cup -i 3 -I 99,5
931 In the example above we see that netperf did not meet the desired
939 will not result in netperf emitting a warning. To verify the hitting,
944 remain in a ``migrated'' classic netperf test.
956 whichever comes first. A classic or migrated netperf test will not
975 This option instructs netperf to keep additional timing statistics
1005 microseconds. Added in netperf 2.5.0.
1026 @option{-i} the total length of the netperf test will be somewhere
1035 when you wish to make sure that the netperf control and data
1037 is trying to run netperf through those evil, end-to-end breaking
1045 This option tells netperf how many CPUs it should ass-u-me are active
1046 on the system running netperf. In particular, this is used for the
1048 On certain systems, netperf is able to determine the number of CPU's
1049 automagically. This option will override any number netperf might be
1053 running netserver. When netperf/netserver cannot automagically
1057 As it is almost universally possible for netperf/netserver to
1060 future release of netperf.
1064 This option tells netperf to forgo establishing a control
1065 connection. This makes it is possible to run some limited netperf
1084 size and the like via the netperf command line. Nor is it possible to
1097 Added in netperf 2.4.3.
1107 will cause the buffers passed to the local (netperf) send and receive
1120 netperf the port number at which it should expect the remote netserver
1122 optionspec will request netperf to bind to that local port number
1127 tells netperf that the remote netserver is listening on port 12345 and
1134 causes netperf to bind to the local port number 32109 before
1138 is looking to run netperf through those evil, end-to-end breaking
1152 This option will cause netperf to sleep @samp{<seconds>} before
1154 useful in situations where one wishes to start a great many netperf
1164 attempt will be made on the netperf side of all tests, and will be
1173 This option is used to tell netperf which test you wish to run. As of
1193 Not all tests are always compiled into netperf. In particular, the
1195 netperf when configured with
1206 affinity of netperf and/or netserver.
1208 netperf -T 1
1210 will bind both netperf and netserver to ``CPU 1'' on their respective
1213 netperf -T 1,
1215 will bind just netperf to ``CPU 1'' and will leave netserver unbound.
1217 netperf -T ,2
1219 will leave netperf unbound and will bind netserver to ``CPU 2.''
1221 netperf -T 1,2
1223 will bind netperf to ``CPU 1'' and netserver to ``CPU 2.''
1231 This option controls how verbose netperf will be in its output, and is
1242 If the verbosity level is set to ``1'' then the ``normal'' netperf
1249 each transaction if netperf was configured with
1260 This option displays the netperf version and then exits.
1262 Added in netperf 2.4.4.
1266 If netperf was configured with @option{--enable-intervals=yes} then
1275 some benchmarks, netperf does not continuously send or receive from a
1310 network. The classic netperf convention for a bulk data transfer test
1337 A bulk-transfer test can be CPU bound even when netperf reports less
1341 of a netperf _STREAM test cannot make use of much more than the power
1342 of one CPU. Exceptions to this generally occur when netperf and/or
1381 netperf was running. In such situations something along the lines of:
1384 netperf -t TCP_mumble...
1406 or @option{-k} output selction option and netperf will report the
1493 This option sets the local (netperf) send and receive socket buffer
1576 The TCP_STREAM test is the default test in netperf. It is quite
1578 netperf to the system running netserver. While time spent
1581 the end of the test is. This is how netperf knows that all the data
1595 netperf does not perform any explicit flush operations. Setting
1602 netperf does not validate command-line options to enforce that.
1632 $ netperf -H lag
1659 netperf. The global command-line @option{-F} option is ignored for
1668 $ netperf -H lag -t TCP_MAERTS -- -s 128K -S 128K
1689 netperf the platform's @code{sendfile()} call instead of calling
1707 specified, netperf will create a temporary file, which it will delete
1717 $ netperf -H lag -F ../src/netperf -t TCP_SENDFILE -- -s 128K -S 128K
1726 $ netperf -H lag -F /boot/vmlinuz-2.6.8-1-686 -t TCP_SENDFILE -- -s 128K -S 128K
1747 and neither does netperf. However, if you wish, you can configure
1748 netperf with @code{--enable-intervals=yes} to enable the global
1765 $ netperf -t UDP_STREAM -H 192.168.2.125 -- -m 32768
1776 The first line of numbers are statistics from the sending (netperf)
1782 socket buffer size (@option{-s} option) netperf will likely abort with
1786 netperf -t UDP_STREAM -H 192.168.2.125
1797 $ netperf -t UDP_STREAM -H 192.168.2.125 -- -m 65000 -S 32768
1823 made by netperf XTI tests.
1825 The XTI_TCP_STREAM test is only present if netperf was configured with
1836 made by netperf XTI tests.
1838 The XTI_UDP_STREAM test is only present if netperf was configured with
1852 The SCTP_STREAM test is only present if netperf was configured with
1893 The DLCO_STREAM test is only present if netperf was configured with
1906 and reassembly available and netperf does not presume to provide one.
1911 The DLCL_STREAM test is only present if netperf was configured with
1928 The STREAM_STREAM test is only present if netperf was configured with
1944 The DG_STREAM test is only present if netperf was configured with
1961 a time test such as those found by default in netperf, is particularly
1968 for a netperf _RR test.
1977 version 2.5.0 (actually slightly before) netperf still does not do the
1979 classic netperf test, or includes the appropriate @ref{Omni Output
1996 important as netperf generally only has one transaction outstanding at
2004 systems, particularly if one CPU binds the netperf and netserver
2092 This option sets the local (netperf) send and receive socket buffer
2103 Will request the local send (netperf) and receive socket buffer sizes
2202 netperf -t TCP_RR -H 192.168.2.125
2246 happening, netperf will by default select its own client port numbers
2249 second. The size of the client port space used by netperf can be
2252 maximum (second value) port numbers used by netperf at the client end.
2278 In fact, the TCP_CRR test was added to netperf to simulate just that.
2299 netperf does not add anything for that either. This means that if
2310 The netperf side of a UDP_RR test will call @code{connect()} on its
2322 $ netperf -T 1 -H 192.168.1.213 -t UDP_RR -c -C
2335 loading. The @option{-T} option was used to make sure netperf and
2413 use when one wants to measure aggregate performance because netperf
2418 There are a few ways to measure aggregate performance with netperf.
2419 The first is to run multiple, concurrent netperf tests and can be
2420 applied to any of the netperf tests. The second is to configure
2421 netperf with @code{--enable-burst} and is applicable to the TCP_RR
2435 wants to measure aggregate performance because netperf has no support
2440 necessary to run netperf. The skew error can be minimized by making
2448 netperf -t TCP_STREAM -H tardy.cup.hp.com -i 10 -P 0 &
2454 concurrent netperf will iterate 10 times thanks to the @option{-i}
2472 netperf -t TCP_STREAM -H $hosts -i 10 -P 0 &
2478 If you see warnings about netperf not achieving the confidence
2489 netperf -t TCP_STREAM -H tardy.cup.hp.com -i 10 -P 0 -c -C &
2512 @b{NOTE: It is very important to remember that netperf is calculating
2514 (those last two columns in the output above) each netperf assumes it
2516 concurrent tests the service demands reported by netperf will be
2527 netperf -t TCP_STREAM -H tardy.cup.hp.com -B "this is test $i" -i 10 -P 0 &
2550 other issues to consider when running concurrent netperf tests.
2565 remember that each concurrent netperf instance is calculating
2567 netperf assumes it is the only thing running on the system. This
2569 netperf @b{will be wrong}. One has to compute service demands for
2575 rather than netperf commands. This introduces more skew error, which
2577 One possibility is to actually run three consecutive netperf tests on
2580 netperfs started is less than the length of the first netperf command
2596 To have burst-mode functionality present in netperf. This enables a
2600 Normally, netperf will attempt to ramp-up the number of outstanding
2604 any) is smaller at the time than what netperf wants to have
2612 just a single instance of netperf, increasing the burst size can
2619 netperf -v 0 -t TCP_RR -B "-b $b" -H hpcpc108 -P 0 -- -b $b
2650 netperf -v 0 -t TCP_RR -B "-b $b -D" -H hpcpc108 -P 0 -- -b $b -D
2675 concurrent netperf tests. This would then be an ``aggregate of
2682 netperf -H hpcpc108 -v 0 -P 0 -i 10 -B "aggregate $i -b 8 -D" -t TCP_RR -- -b 8 -D &
2692 Since each netperf did hit the confidence intervals, we can be
2704 netperf -H 192.168.2.108 -l 60 -v 0 -P 0 -B "aggregate $i -b 8 -D" -t TCP_RR -- -b 8 -D &
2743 netperf was reporting very well.
2755 netperf -l 60 -H 192.168.2.108 -v 0 -P 0 -B "aggregate $i -b 8 -D" -t TCP_RR -- -b 8 -D & done
2794 and compile netperf to enable netperf to emit ``interim results'' at
2797 output of netperf will then look something like
2800 $ src/netperf -D 1.25
2850 knowledge of how long it takes to get netperf tests started and/or
2855 has been nor is universally true. For that reason netperf tries to
2859 netperf tries to guess how many units of work will be performed over
2861 completed will netperf check the time. If the reporting interval has
2862 passed, netperf will emit an ``interim result.'' If the interval has
2863 not passed, netperf will update its estimate for units and continue.
2865 After a bit of thought one can see that if things ``speed-up'' netperf
2867 netperf may be late with an ``interim result.'' Here is an example of
2870 when another netperf (not shown) is started we see things slowing down
2871 and netperf not hitting the interval as desired.
2873 $ src/netperf -D 2 -H tardy.hpl.hp.com -l 20
2893 improve the netperf's honoring the interval but one should not
2902 There are two ways to use netperf to measure the performance of
2903 bidirectional transfer. The first is to run concurrent netperf tests
2904 from the command line. The second is to configure netperf with
2910 instance, using the concurrent netperf test mechanism means that
2926 If we had two hosts Fred and Ethel, we could simply run a netperf
2928 concurrent netperf TCP_STREAM test on Ethel pointing at Fred, but
2929 since there are no mechanisms to synchronize netperf tests and we
2941 netperf -H 192.168.2.108 -t TCP_STREAM -B "outbound" -i 10 -P 0 -v 0 \
2943 netperf -H 192.168.2.108 -t TCP_MAERTS -B "inbound" -i 10 -P 0 -v 0 \
2957 relative to the system on which we were running netperf. Of course
2969 netperf -H 192.168.1.3 -t omni -l 10 -P 0 -- \
2971 netperf -H 192.168.1.3 -t omni -l 10 -P 0 -- \
2996 netperf -f m -t TCP_RR -H 192.168.1.3 -v 2 -- -b 6 -r 32K -S 256K -S 256K
3025 versions of netperf might attempt to do this automagically, but there
3039 the global @option{-T} option has been used to bind netperf/netserver
3065 Beginning with version 2.5.0, netperf begins a migration to the
3068 is to make it easier for netperf to support multiple protocols and
3080 and remake netperf. Remaking netserver is optional because even in
3095 cause netperf to use the code in @file{src/nettest_omni.c} and in
3108 This option sets the direction of the test relative to the netperf
3114 Any of which will cause netperf to send to the netserver.
3116 Any of which will cause netserver to send to netperf.
3136 $ netperf -t omni -- -d rr -k "THROUGHPUT,THROUGHPUT_UNITS"
3151 $ netperf -t omni -- -d rr -o "THROUGHPUT,THROUGHPUT_UNITS"
3163 look quite similar to classic netperf output:
3165 $ netperf -t omni -- -d rr -O "THROUGHPUT,THROUGHPUT_UNITS"
3187 to netperf include:
3211 This can set the send size for either or both of the netperf and
3216 sets only the netperf-side send size to 32768 bytes, and or's-in
3226 sets the netperf side send size to 16284 bytes, the netserver side
3230 This can set the receive size for either or both of the netperf and
3240 sets only the netperf side receive size to 32768 bytes and or's-in
3245 sets the netserver side receive size to 16384 bytes and the netperf
3260 $ netperf
3290 $ netperf -t tcp_rr -- -k THROUGHPUT,THROUGHPUT_UNITS
3297 $ netperf -t tcp_rr
3322 ``classic'' netperf output, is inspired by it. Multiple lines have no
3349 inspired by classic netperf output. The format will be the @samp{human
3355 option netperf will select a default based on the characteristics of the
3360 semi-colon-separated list. If none of those checks match, netperf will then
3385 This will display the data flow direction relative to the netperf
3398 This will display the local (netperf) send socket buffer size (aka
3401 This will display the local (netperf) send socket buffer size
3406 This will display the local (netperf) send socket buffer size
3412 This will display the local (netperf) receive socket buffer size (aka
3415 This will display the local (netperf) receive socket buffer size
3420 This will display the local (netperf) receive socket buffer size
3454 This will display the size of the buffers netperf passed in any
3458 This will display the size of the buffers netperf passed in any
3470 This will display the size of the requests netperf sent in a
3477 measured by netperf. Units: 0 to 100 percent.
3480 as measured by netperf. Only supported by netcpu_procstat. Units: 0 to
3484 as measured by netperf. Only supported by netcpu_procstat. Units: 0 to
3488 during the test as measured by netperf. Only supported by
3492 test as measured by netperf. Only supported by netcpu_procstat. Units:
3496 test as measured by netperf. Only supported by netcpu_procstat. Units:
3499 This will display the method used by netperf to measure CPU
3503 unit of work, as measured by netperf. Units: microseconds of CPU
3551 This will display the number of test iterations netperf undertook,
3562 achieved for overall CPU utilization on the system running netperf
3591 data connection during the test as determined by netperf. A value of
3611 The throughput as measured by netperf for the successful ``send''
3616 The throughput as measured by netperf for the successful ``receive''
3631 The CPU to which netperf was bound, if at all, during the test. A
3632 value of -1 means that netperf was not explicitly bound to a CPU
3635 The number of CPUs (cores, threads) detected by netperf. Units: CPU count.
3638 measured by netperf. This can be used to see if any one CPU of a
3643 by netperf. Units: CPU ID.
3646 netperf. Assumes all processors in the system (as perceived by
3647 netperf) on which netperf is running are the same model. Units: Text
3649 The frequency of the processor(s) on the system running netperf, at
3650 the time netperf made the call. Assumes that all processors present
3651 in the system running netperf are running at the same
3655 value of -1 means that netperf was not explicitly bound to a CPU
3679 The port ID/service name to which the data socket created by netperf
3683 The name/address to which the data socket created by netperf was
3687 The address family to which the data socket created by netperf was
3702 The number of successful ``send'' calls made by netperf against its
3705 The number of successful ``receive'' calls made by netperf against its
3708 The average number of bytes per ``receive'' call made by netperf
3711 The average number of bytes per ``send'' call made by netperf against
3714 The number of bytes successfully sent by netperf through its data
3717 The number of bytes successfully received by netperf through its data
3720 The sum of bytes sent and received by netperf through its data
3723 The offset from the alignment of the buffers passed by netperf in its
3727 The offset from the alignment of the buffers passed by netperf in its
3731 The alignment of the buffers passed by netperf in its ``send'' calls
3735 The alignment of the buffers passed by netperf in its ``receive''
3739 The ``width'' of the ring of buffers through which netperf cycles as
3742 the data socket is created. Can be used to make netperf more processor
3745 The ``width'' of the ring of buffers through which netperf cycles as
3748 at the time the data socket is created. Can be used to make netperf
3751 The number of bytes to ``dirty'' (write to) before netperf makes a
3754 command prior to building netperf. Units: Bytes.
3756 The number of bytes to ``dirty'' (write to) before netperf makes a
3759 prior to building netperf. Units: Bytes.
3761 The number of bytes netperf should read ``cleanly'' before making a
3764 prior to building netperf. Clean reads start were dirty writes ended.
3768 delay'' (eg TCP_NODELAY) option on the data socket used by netperf was
3773 netperf as requested via the test-specific @option{-C} option. 1 means
3794 netserver rather than netperf.
3797 netperf was running. Units: ASCII Text
3799 The model name of the system on which netperf was running. Units:
3803 netperf was running. Units: ASCII Text
3805 The version number of the OS running on the system on which netperf
3808 The machine architecture of the machine on which netperf was
3816 netserver rather than netperf.
3819 connection went on the system running netperf. Example: eth0. Units:
3823 on the data connection went on the system running netperf. Units:
3828 on the data connection went on the system running netperf. Units:
3834 netperf. Units: Hexadecimal IDs as might be found in a @file{pci.ids}
3840 netperf. Units: Hexadecimal IDs as might be found in a @file{pci.ids}
3846 netperf. Units: ASCII Text.
3850 system running netperf. Units: ASCII Text.
3854 system running netperf. Units: ASCII Text.
3857 on the data connection went on the system running netperf. Units:
3861 on the data connection went on the system running netperf. Units:
3874 netserver rather than netperf.
3877 transactions) were attempted by netperf. Specified by the
3880 netperf. Units: Microseconds (though specified by default in
3884 the test) which were attempted by netperf each LOCAL_INTERVAL_USECS
3887 command prior to building netperf. Units: number of operations per burst.
3893 netperf. Units: Microseconds (though specified by default in
3897 the test) which were attempted by netperf each LOCAL_INTERVAL_USECS
3900 command prior to building netperf. Units: number of operations per burst.
3918 generated automagically by netperf, or passed to netperf via an omni
3924 netperf side when the global @option{-j} option was specified. Units:
3929 netperf side when the global @option{-j} option was specified. Units:
3934 netperf side when the global @option{-j} option was specified. Units:
3939 netperf side when the global @option{-j} option was specified. Units:
3944 netperf side when the global @option{-j} option was specified. Units:
3949 netperf side when the global @option{-j} option was specified. Units:
3954 netperf side when the global @option{-j} option was specified. Units:
3957 The full command line used when invoking netperf. Units: ASCII Text.
3966 Apart from the typical performance tests, netperf contains some tests
3979 Some of the CPU utilization measurement mechanisms of netperf work by
3982 system is running a netperf test. The ratio of those rates is used to
3985 This means that netperf must know the rate at which the counter
3987 know the rate, netperf will measure it before starting a data transfer
3989 remote systems, and if repeated for each netperf test would make taking
3992 Thus, the netperf CPU utilization options @option{-c} and and
3995 performed. To determine the idle rate, netperf can be used to run
4000 use that in subsequent netperf commands:
4003 LOC_RATE=`netperf -t LOC_CPU`
4004 REM_RATE=`netperf -H <remote> -t REM_CPU`
4005 netperf -H <remote> -c $LOC_RATE -C $REM_RATE ... -- ...
4007 netperf -H <remote> -c $LOC_RATE -C $REM_RATE ... -- ...
4010 If you are going to use netperf to measure aggregate results, it is
4012 values first to avoid issues with some of the aggregate netperf tests
4015 important to remember that any one instance of netperf does not know
4016 about the other instances of netperf. It will report global CPU
4019 utilization reported by netperf in an aggregate test, but you have to
4025 Beginning with version 2.5.0 netperf can generate Universally Unique
4029 $ netperf -t UUID
4037 aggregate netperf test. Say, for instance if they were inserted into
4050 was generally unlikely and netperf's ignoring of the second and later
4068 netperf tests _may_ try to be more sophisticated in their parsing of
4070 @email{netperf-feedback@@netperf.org} would of course be most welcome
4085 enhancements to netperf, by all means do so. If you wish to add a new
4086 ``suite'' of tests to netperf the general idea is to:
4096 Edit @file{src/netperf.c}, @file{netsh.c}, and @file{netserver.c} as
4111 @email{netperf-feedback@@netperf.org} or perhaps
4112 @email{netperf-talk@@netperf.org}. If the consensus is positive, then
4114 @email{netperf-feedback@@netperf.org} is the next step. From that
4122 Netperf4 is the shorthand name given to version 4.X.X of netperf.
4124 netperf, but it is a descendant of netperf so the netperf name is
4126 egg-laying-woolly-milk-pig version of netperf :) The more respectful
4127 way to describe it is to say it is the version of netperf with support
4133 @uref{http://www.netperf.org/cgi-bin/mailman/listinfo/netperf-dev,netperf-dev}
4135 @uref{http://www.netperf.org/svn/netperf4/trunk,current sources}.