OpenSS7
SS7 for the
Common Man
© Copyright 1997-2007 OpenSS7 Corporation All Rights Reserved.
Last modified: Sat, 21 Jul 2007 19:34:31 GMT
Home TopIndex FirstPrev Next LastMore Download Info FAQ Mail  Home -> Documentation -> Man Pages -> Manual Page
Quick Links

Download

SCTP

SIGTRAN

SS7

Hardware

STREAMS

Asterisk

Related

Package

Manual

FAQ

Man Pages

Applications

SS7 Stack

ISDN Stack

SIGTRAN Stack

VoIP Stack

MG Stack

SS7/ISDN Devices

IP Transport

Embedded Systems

OS

Documentation

FAQ

SIGTRAN

Design

Conformance

Performance

References

Man Pages

Manuals

Papers

Home

Overview

Status

Documentation

Resources

About

News

Description: Manual Page

Keywords: ss7 ss7/ip ss7 over ip ss7 mtp ss7 sccp ss7 tcap sigtran mtp sccp tcap openss7 acb56 linux telephony pstn linux telephony linux nebs linux compactpci


NETPERF

Section: The OpenSS7 Project User Commands (1L)
Updated: Tue, 17 Oct 2017 17:15:49 GMT
Index Return to Main Contents

NAME

netperf - a network performance benchmark

SYNOPSIS

netperf [-tTESTNAME] [global-test-options] [-- [test-specific-options]]
netperf -h,--help
netperf [-tTESTNAME] [-a[LOC-SND-ALIGN][,][LOC-RCV-ALIGN]] [-A[REM-SND-ALIGN][,][REM-RCV-ALIGN]] [-c[LOC-RATE]] [-C[REM-RATE]] [-d] [-f{G|M|K|g|m|k}] [-FFILL-FILE] [-HREMOTE-HOST] [-iMAX,MIN] [-ILEVEL[,WIDTH]] [-lTESTLEN] [-nNUM-CPUS] [-o[LOC-SND-OFFSET][,][LOC-RCV-OFFSET]] [-O[REM-SND-OFFSET][,][REM-RCV-OFFSET]] [-pPORTNUM] [-P{0|1}] [-vVERBOSITY] [--[test-specific-options]]
netperf -tsocket-test [global-test-options] [-- [-CDVz]
[-bBURST-SIZE] [-I[LOC-IP-ADDR[:LOC-IP-ADDR]*][,[REM-IP-ADDR][:REM-IP-ADDR]*]] [-mLOC-MSG-SIZE] [-MREM-MSG-SIZE] [-p[MIN-PORTNUM][,][MAX-PORTNUM]] [-P[LOC-PORTNUM][,][REM-PORTNUM]] [-r[REQ-SIZE][,][RSP-SIZE]] [-s[LOC-SNDBUF][,][LOC-RCVBUF]] [-S[REM-SNDBUF][,][REM-RCVBUF]] [-wRCV-WIDTH] [-WSND-WIDTH] ]
netperf -txti-test [global-test-options] [-- [-DV]
[-I[LOC-IP-ADDR[:LOC-IP-ADDR]*][,[REM-IP-ADDR][:REM-IP-ADDR]*]] [-mLOC-MSG-SIZE] [-MREM-MSG-SIZE] [-r[REQ-SIZE][,][RSP-SIZE]] [-s[LOC-SNDBUF][,][LOC-RCVBUF]] [-S[REM-SNDBUF][,][REM-RCVBUF]] [-wRCV-WIDTH] [-WSND-WIDTH] [-X[LOC-DEVICE][,][REM-DEVICE]] ]
netperf -tipv6-test [global-test-options] [-- [-DV]
[-HHOSTNAME] [-mLOC-MSG-SIZE] [-MREM-MSG-SIZE] [-p[MIN-PORTNUM][,][MAX-PORTNUM]] [-r[REQ-SIZE][,][RSP-SIZE]] [-s[LOC-SNDBUF][,][LOC-RCVBUF]] [-S[REM-SNDBUF][,][REM-RCVBUF]] [-wRCV-WIDTH] [-WSND-WIDTH] ]
netperf -tunix-test [global-test-options] [--
[-mLOC-MSG-SIZE] [-MREM-MSG-SIZE] [-pPATH] [-s[LOC-SNDBUF][,][LOC-RCVBUF]] [-S[REM-SNDBUF][,][REM-RCVBUF]] [-r[REQ-SIZE][,][RSP-SIZE]] ]
netperf -tdlpi-test [global-test-options] [--
[-D[LOC-DEVICE][,][REM-DEVICE]] [-mLOC-MSG-SIZE] [-MREM-MSG-SIZE] [-p[LOC-PPA][,][REM-PPA]] [-r[REQ-SIZE][,][RSP-SIZE]] [-sSAP] [-w[LOC-SND-WINDOW][,][LOC-RCV-WINDOW]] [-W[REM-SND-WINDOW][,][REM-RCV-WINDOW]] ]
netperf -tdns-test [global-test-options] [--
[-fFILENAME] [-HHOSTNAME] ]
netperf -tatm-test [global-test-options] [--
[atm-options]]
netperf -thippi-test [global-test-options] [--
[hippi-options]]
netperf -tlwp-test [global-test-options] [--
[lwp-options]]

DESCRIPTION

netperf
is a benchmark that can be used to measure various aspects of networking performance. Currently, its focus is on bulk data transfer and request/response performance using SCTP, TCP or UDP, and the Berkeley Sockets interface. In addition, tests for XTI[1], DLPI[2], and Unix Domain Sockets, tests for IPv6 may be conditionally compiled-in.

TESTS

netperf perfoms the following tests:

Test NameAPIProtocolTest

SCTP_STREAMSocketsSCTPSTREAM
SCTP_MAERTSMAERTS
SCTP_SENDFILESENDFILE


SCTP_RRRR
SCTP_NBRRNBRR
SCTP_CRRCRR
SCTP_TRRTRR
SCTP_CCCC



TCP_STREAMTCPSTREAM
TCP_MAERTSMAERTS
TCP_SENDFILESENDFILE


TCP_RRRR
TCP_NBRRNBRR
TCP_CRRCRR
TCP_TRRTRR
TCP_CCCC



UDP_STREAMUDPSTREAM


UDP_RRRR




XTI_SCTP_STREAMXTISCTPSTREAM


XTI_SCTP_RRRR
XTI_SCTP_CRRCRR
XTI_SCTP_TRRTRR
XTI_SCTP_CCCC



XTI_TCP_STREAMTCPSTREAM


XTI_TCP_RRRR
XTI_TCP_CRRCRR
XTI_TCP_CCCC



XTI_UDP_STREAMUDPSTREAM


XTI_UDP_RRRR




SCTPIPV6_STREAMIPv6 SocketsSCTPSTREAM


SCTPIPV6_RRRR
SCTPIPV6_CRRCRR
SCTPIPV6_TRRTRR



TCPIPV6_STREAMTCPSTREAM


TCPIPV6_RRRR
TCPIPV6_CRRCRR
TCPIPV6_TRRTRR



UDPIPV6_STREAMUDPSTREAM


UDPIPV6_RRRR




STREAM_STREAMUnix SocketsCOSTREAM


STREAM_RRRR



DG_STREAMCLSTREAM


DG_RRRR




DLCO_STREAMDLPICOSTREAM


DLCO_RRRR



DLCL_STREAMCLSTREAM


DLCL_RRRR




LOC_CPUnonenonenone
REM_CPU




PROTOCOLS

netperf tests the following protocols:

SCTPStream Control Transmission Protocol
TCPTransmission Control Protocol
UDPUser Datagram Protocol
UNIXUnix Domain (CO and CL) Protocols
ATMAsynchronous Transfer Mode
HIPPI

APPLICATION PROGRAMMING INTERFACES

netperf tests the following APIs:

BSDBSD/POSIX Sockets Interface
XTIX/Open Transport Interface (XTI/TLI) XNS 5.2 SuSv2[3]
IPV6POSIX IPv6 Sockets Interface
UNIXUnix Domain Sockets Interface
DLPIData Link Provider Interface[4]
ATMFORE ATM Interface
HiPPIHP-UX Interface

BENCHMARKING PERFORMANCE TESTS

netperf test the following benchmarks:

STREAMUnidirectional Stream Test (Client to Server)
MAERTSUnidirectional Stream Test (Server to Client)
SENDFILEUnidirectional Stream Test (BSD sendfile(2))
RRBlocking Request/Response
NBRRNon-blocking Request/Response
CRRConnect/Request/Response
TRRTransaction Request/Response
CCConnect/Close
CPUCPU Syncrhonization Tests

Unidirectional Stream Test

The most common used of netperf(1) is measuring bulk data transfer performance. This is also referred to as "stream" or "unidirectional stream" performance tests. Essentially, these tests will measure how fast one system can send data to another or how fast the other system can receive it.

There are three unidirectional stream tests peformed by netperf(1): *_STREAM tests, *_MAERTS tests and *_SENDFILE tests. *_STREAM tests connect and transfer data in the direction from client to server. *_MAERTS tests connect and transfer data in the direction from server to client. *_SENDFILE tests connect and transfer data in the direction from client to server using BSD sendfile(2).

STREAM - Unidirectional Stream Test (Client to Server)
MAERTS - Unidirectional Stream Test (Server to Client)

These tests are similar to the *_STREAM tests, except that data is send in the direction from server to client instead of the direction from client to server.

SENDFILE - Unidirectional Stream Test (BSD sendfile(2))

Request/Response Tests

Request/response performance is the second class of tests that can be investigated with netperf(1). Generally speaking, netperf(1) request/response performance is quoted as "transactions per second" for a given request and response size. A transaction is defined as the exchange of a single request and a single response. From a transaction rate, one can infer one way and round-trip average latency.

RR - Request/Response:
The Request/Response test is the simplest form of transaction performance test. The client establishes a connection to the server and then continuously exchanges Request/Response pairs. These tests are applicable to both Connection-Oriented and Connectionless protocols.
NBRR - Non-blocking Request/Response:
These tests are intended to implement the same as the RR tests, except that they use POSIX-style non-blocking sockets. These tests are applicable to both Connection-Oriented and Connectionless protocols.

It is expected that benchmarks resulting from NBRR tests will be worse than benchmarks resulting from RR tests. This is because blocking operation typcially works in the favor of the system for Request/Repsonse tests in that the system properly anticipates the next expected event in the blocking tests, whereas it does not anticipate in the non-blocking tests.

Because of this negative effect, and although it would be rather straightforward to extend other interfaces to support non-blocking Request/Response operation, only the Sockets API currently supports the NBRR tests.

Blocking and non-blocking Request/Response tests support the following common test specific options:

-r[REQ-SIZE][,][RSP-SIZE]
Specifies the request [REQ-SIZE] (or response [RSP-SIZE]) sizes. At least one of REQ-SIZE or RSP-SIZE must be specified. If there is no comma (`,') in the option argument, then the specified size applies to both the request and response size.
-s [LOC-SNDBUF][,][LOC-RCVBUF]
Sets the local send (LOC-SNDBUF) and receive (LOC-RCVBUF) buffer sizes. One of LOC-SNDBUF and LOC-RCVBUF must be specified. If no comman (`,') is present in the option argument, then the specified buffer size applies to both the local send buffer size as well as the local receive buffer size.
-S [REM-SNDBUF][,][REM-RCVBUF]
Sets the remote send (REM-SNDBUF) and receive (REM-RCVBUF) buffer sizes. One of REM-SNDBUF and REM-RCVBUF must be specified. If no comman (`,') is present in the option argument, then the specified buffer size applies to both the remote send buffer size as well as the remote receive buffer size.
CRR - Connect/Request/Response:
These tests are intended to test the performance of establishing a connection, exchanging a request/response pair, and repeating. It is expected that this would be a good starting-point for comparison of T/TCP with TCP for transactional workloads. It will also look (can look) much like the communication pattern of http for www access. The CRR tests are only applicable to connection-oriented protocols.
TRR - Transaction Request/Response:
These tests are intended to test the performance of establishing a connection, exchanging a request/response pair, and repeating. It is expected that this would be a good starting-point for comparison of T/TCP with classic TCP for transaction workloads. It will also look (can look) much like the communication pattern of http for www access. See also, however, the CRR tests above. The TRR tests are only applicable to connection-oriented protocols.

There is one significant difference between the way that the TRR tests and the CRR tests are implemented. On POSIX/BSD Sockets interface, the sendto(2) call is used instead of connect(2) and send(2). Under the STREAMS XTI API[5], data is sent with the t_connect(3) call and also with the t_accept(3) call rather than separate data transmissions.

This means that the connection is established coincident with the sending of data. Implementations of T/TCP might be able to take advantage of this. Also, the Linux implementation of TCP might also be able to take advantage of this. One system call is avoided and the calling process will block in a wait queue awaiting establishment of the connection and will be able to transfer data immediately once the connection is established.

For SCTP there might be some more significant differences. Unlike T/TCP and TCP, SCTP is able to transfer the request data with the COOKIE-ECHO and receive the response data with the COOKIE-ACK, reducing two message exchanges. When best implemented, SCTP should perform better in the TRR tests than it does in the CRR tests.

In the original netperf, the CRR and TRR tests were only implemented for TCP on the Sockets API. OpenSS7 has implemented these tests also for the SCTP protocol on the Sockets API, as well as both the SCTP and TCP protocols on the XTI API.

In addition to the common test specific options for blocking and non-blocking Response/Request tests, the CRR and TRR tests take the following common test specific options:

-p [MIN-PORTNUM][,][MAX-PORTNUM]
Specify the minimum and maximum port numbers used for the *_CRR and *_TRR tests. At least one of MIN-PORTNUM or MAX-PORTNUM must be specified. If there is no comma (`,') in the option argument, then the specified port number applies to both the minimum and maximum. This option is only applicable to SCTP and TCP tests.
CC - Connect/Close:
This test is intended to test the performance of establishing a connection, and then closing it again. This test is of somewhat arcane interest since no packets are exchanged between the user-space processes, but it will show the raw overhead of establishing an SCTP association or TCP connection. That service demand could them be compared with the sum of the service demands of a CRR and RR test and presumably there would be a discernable relationship between the tests. The CC tests are only applicable to connection-oriented protocols.

In the original netperf, the CC tests were only impleemnted for TCP on the Sockets API. OpenSS7 has implemented these tests also for the SCTP protocol on the Sockets API, as well as both the SCTP and TCP protocols on the XTI API.

CPU Synchronization Tests

LOC_CPU - Local CPU
REM_CPU - Remote CPU

OPTIONS

COMMAND OPTIONS

[-t,--testname=TESTNAME]
Specify the test to perform. Valid testnames are (but not always compiled-in):

XTI_SCTP_STREAM, XTI_SCTP_MAERTS, XTI_SCTP_RR, XTI_SCTP_CRR, XTI_SCTP_TRR, XTI_SCTP_CC, XTI_TCP_STREAM, XTI_TCP_MAERTS, XTI_TCP_RR, XTI_TCP_CRR, XTI_TCP_TRR, XTI_TCP_CC, XTI_UDP_STREAM, XTI_UDP_RR, SCTP_STREAM, SCTP_MAERTS, SCTP_RR, SCTP_CRR, SCTP_TRR, TCP_STREAM, TCP_MAERTS, TCP_RR, TCP_CRR, TCP_TRR, UDP_STREAM, UDP_RR, SCTPIPV6_STREAM, SCTPIPV6_RR SCTPIPV6_CRR, SCTPIPV6_TRR, TCPIPV6_STREAM, TCPIPV6_RR, TCPIPV6_CRR, TCPIPV6_TRR, UDPIPV6_STREAM, UDPIPV6_RR, DLCO_STREAM, DLCO_RR, DLCL_STREAM, DLCL_RR, STREAM_STREAM, STREAM_RR, DG_STREAM, DG_RR, LOC_CPU, REM_CPU.

-h,--help
Display a usage string, and exit.

GLOBAL TEST OPTIONS

Global test options are specified on the command line before the first double-dash (`--'). Not all global test options are applicable to all tests. The global test options are as follows:

-4,--ipv4
Use IPv4 for the control socket (the default).
-6,--ipv6
Use IPv6 instead of IPv4 for the control socket.
-a,--loc-align=[LOC-SND-ALIGN][,][LOC-RCV-ALIGN]
Alter the send and receive buffer alignments on the local system. At least one of LOC-SND-ALIGN or REM-SND-ALIGN must be specified. If there is no comma (`,') in the option argument, the specified value applies to both the send and receive. This defaults to 8 bytes.
-A,--rem-align=[REM-SND-ALIGN][,][REM-RCV-ALIGN]
As -a, but for the remote system. At least one of LOC-SND-ALIGN or REM-SND-ALIGN must be specified. If there is no comma (`,') in the option argument, the specified value applies to both the send and receive.
-b,--burst=BURST
Number of burst packets per interval.
-c,--loc-cpu=[LOC-RATE]
Request CPU utilization and service demand calculations for the local system. If the optional rate parameter is specified, netperf will use that instead of calculating the rate itself.
-C,--rem-cpu=[REM-RATE]
As -c, but for the remote system.
-d,--debug
Increase the quantity of debugging output displayed during a test (possibly at the expense of performance).
-D,--demo
Demo mode: not supported on Linux.
-f,--format={G|M|K|g|m|k}
Change the units of measure for *_STREAM tests. Capital letters are powers of two, lowercase are powers of ten.
-F,--filefile=FILL-FILE
Pre-fill the send buffers with data from the named file. This is intended to provide a means for avoiding buffers that are filled with data which is trivially easy to compress. A good choice for a file that should be present on any system is this manpage - netperf.man. Other files may be provided as part of the distribution.
-H,--host=REMOTE-HOST
Set the hostname (or IP address) of the remote system.
-i,--iterations=MAX,MIN
Set the maximum and minimum number of iterations when trying to reach certain confidence levels.
-I,--interval=LEVEL[,WIDTH]
Specify the confidence level (either 95 or 99 - 99 is the default) and the width of the confidence interval as a percentage (default 10)
-K,--rem-count=[REM-DIRTY][,][REM-CLEAN]
-k,--loc-count=[LOC-DIRTY][,][LOC-CLEAN]
-l,--length=TESTLEN
Specify the length of the test (default 10 seconds). A negative value sets the number of request/response transactions, or the number of bytes for a stream test.
-n,--numcpus=NUM-CPUS
Specify the number of CPU's in the system on those systems for which netperf has no way to find the number of CPU's programatically.
-o,--loc-offset=[LOC-SND-OFFSET][,][LOC-RCV-OFFSET]
Set an offset from the alignment specified with -a. At least one of LOC-SND-OFFSET or REM-SND-OFFSET must be specified. If there is no comma (`,') in the option argument, the specified offset applies to both the local and remote system.
-O,--rem-offset=[REM-SND-OFFSET][,][REM-RCV-OFFSET]
As -o, but for the remote system. At least one of LOC-RCV-OFFSET or REM-RCV-OFFSET must be specified. If there is no comma (`,') in the option argument, the specified offset applies to both the local and remote system.
-p,--port=PORTNUM
Connect to a netsetver(8) listening on the specified port, rather than using /etc/services.
-P,--print={0|1}
Show (1) or suppress (0) the test banner.
-v,--verbose=VERBOSITY
Set the verbosity level for the test (only with -P).
-V,--version
Prints version information and exits.
-w,--rate=RATE
Send packets at RATE packets per millisecond.
-W,--width=WIDTH
Width of the user space data buffer ring.
--copying
Prints copying permissions and exists.

TEST SPECIFIC OPTIONS

-h,--help
Display a usage string based on the test name set with -t, and exit.

Please consult the netperf manual Netperf: A Network Performance Benchmark (netperf.ps) for more information. Or you can join and mail to netperf-talk@netperf.org.

SOCKETS OPTIONS

These tests include * tests as follows: SCTP_*, TCP_*, UDP_*.

-t,--testname=SOCKET-TEST
Tests available for the POSIX/BSD Sockets Interface consist of the following: SCTP_STREAM, SCTP_MAERTS, SCTP_SENDFILE, SCTP_RR, SCTP_NBRR, SCTP_CRR, SCTP_TRR, SCTP_CC, TCP_STREAM, TCP_MAERTS, TCP_SENDFILE, TCP_RR, TCP_NBRR, TCP_CRR, TCP_TRR, TCP_CC, UDP_STREAM, UDP_RR. These tests use the BSD/POSIX Sockets API.

Sockets test specific options are specified on the command line following the first double-dash (`--'). Not all sockets options are applicable to all tests. The BSD/POSIX Sockets API test specific options and arguments are as follows:

-h,--help
Prints a usage statement for the specified (or default) test and exits.
-b,--burst=BURST-SIZE
specifies the initial request burst size.
-C,--cork
use option TCP_CORK, SCTP_CORK, T_TCP_CORK or T_SCTP_CORK to cork the socket or stream when preparing to send for the *_SENDFILE tests.
-D,--nodelay
-D use option TCP_NODELAY or SCTP_NODELAY to suppress the Nagle algorithm with (or without) Minshall modifications.
-I,--ipaddr=[LOC-IP-ADDR[:LOC-IP-ADDR]*][,[REM-IP-ADDR][:REM-IP-ADDR]*]
Specify the IP address(es) of the local (LOC-IP-ADDR) or remote (REM-IP-ADDR) host. These addresses are used in a request to bind(2) or t_bind(3) on the local or remote machine before the connection is established. At least one of LOC-IP-ADDR or REM-IP-ADDR must be specified. If no comma (`,') is specified in the option argument, then the IP addresses apply to both the local and remote. The default is INADDR_ANY for both the local and remote addresses.
Multiple addresses separated by a colon (`:') can be specified for transport providers that accept multiple IP addresses to the bind (such as SCTP). If multiple addresses are specified and the transport provider does not accept mutliple addresses to the bind (such as TCP), only the first address will be used and additional addresses specified after the colon (`:') are ignored.
-m,--loc-msgsize=LOC-MSG-SIZE
Specifies the amount of data sent in an individual send(2) operation. This also affects the data sent with a sendto(2) call in the request response tests.
-M,--rem-msgsize=REM-MSG-SIZE
Specifies the amount of data received in an individual recv(2) call.
-p,--portrange=[MIN-PORTNUM][,][MAX-PORTNUM]
Specify the minimum and maximum port numbers used for the *_CRR and *_TRR tests. At least one of MIN-PORTNUM or MAX-PORTNUM must be specified. If there is no comma (`,') in the option argument, then the specified port number applies to both the minimum and maximum.
-P,--portnum=[LOC-PORTNUM][,][REM-PORTNUM]
Specify the local (LOC-PORTNUM) and remote (REM-PORTNUM) data port number for the tests to allow them to run through port proxies. At least one of LOC-PORTNUM or REM-PORTNUM must be specified. If no comma (`,') is specified in the option argument, then the port number specified applies to both the local and remote port.
-r,--rrsize=[REQ-SIZE][,][RSP-SIZE]
Specifies the request (REQ-SIZE) or response (RSP-SIZE) size. At least one of REQ-SIZE or RSP-SIZE must be specified. If there is no comma (`,') in the option argument, then the specified size applies to both the requset and response size.
-s,--loc-bufsize=[LOC-SNDBUF][,][LOC-RCVBUF]
Sets the local send (LOC-SNDBUF) and receive (LOC-RCVBUF) buffer sizes. One of LOC-SNDBUF and LOC-RCVBUF must be specified. If no comman (`,') is present in the option argument, then the specified buffer size applies to both the local send buffer size as well as the local receive buffer size.
-S,--rem-bufsize=[REM-SNDBUF][,][REM-RCVBUF]
Sets the remote send (REM-SNDBUF) and receive (REM-RCVBUF) buffer sizes. One of REM-SNDBUF and REM-RCVBUF must be specified. If no comman (`,') is present in the option argument, then the specified buffer size applies to both the remote send buffer size as well as the remote receive buffer size.
-V,--copyavoid
Specify send and receive copy avoidance (HP-UX 9.0 and later only). This sets the socket options SO_SND_COPYAVOID and SO_RCV_COPYAVOID on the socket if these options are available available locally and will attempt to set them remotely.
-w,--rcv-width=RCV-WIDTH
Ignored.
-W,--snd-width=SND-WIDTH
Sets the SND-WIDTH of the user space data buffer. This will be the number of send sized buffers allocated in the *_STREAM and *_MAERTS tests. It may be enhanced to set both send and receive widths, but for now it is just the sending socket or stream in the *_STREAM and *_MAERTS tests.
-z,--dummy
Ignored.

XTI OPTIONS

These tests include XTI_* tests as follows: XTI_SCTP_*, XTI_TCP_*, XTI_UDP_*.

-t,--testname=XTI-TEST
Tests available for the X/Open Transport Interface (XTI/TLI)[6] consist of the following: XTI_SCTP_STREAM, XTI_SCTP_RR, XTI_SCTP_CRR, XTI_SCTP_TRR, XTI_SCTP_CC, XTI_TCP_STREAM, XTI_TCP_RR, XTI_TCP_CRR, XTI_TCP_TRR, XTI_TCP_CC, XTI_UDP_STREAM, XTI_UDP_RR. These tests use the X/Open Transport Interface (XTI/TLI) API[7].

XTI test specific optoins are specified on the command line following the first double-dash (`--'). Not all XTI options are applicable to all tests. The STREAMS XTI API test specific options and arguments are as follows:

-h,--help
Prints a usage statement for the specified test and exits.
-D,--nodelay
use option T_TCP_NODELAY or T_SCTP_NODELAY to suppress the Nagle algorithm with (or without) Minshall modifications.
-I,--ipaddr=[LOC-IP-ADDR[:LOC-IP-ADDR]*][,[REM-IP-ADDR][:REM-IP-ADDR]*]
Specify the IP address(es) of the local (LOC-IP-ADDR) or remote (REM-IP-ADDR) host. These addresses are used in a request to bind(2) or t_bind(3) on the local or remote machine before the connection is established. At least one of LOC-IP-ADDR or REM-IP-ADDR must be specified. If no comma (`,') is specified in the option argument, then the IP addresses apply to both the local and remote. The default is INADDR_ANY for both the local and remote addresses.
Multiple addresses separated by a colon (`:') can be specified for transport providers that accept multiple IP addresses to the bind (such as SCTP). If multiple addresses are specified and the transport provider does not accept mutliple addresses to the bind (such as TCP), only the first address will be used and additional addresses specified after the colon (`:') are ignored.
-m,--loc-msgsize=LOC-MSG-SIZE
Specifies the amount of data sent in an individual t_send(2) operation. This also affects the data sent with a t_connect(3) or t_accept(3) call in the request response tests.
-M,--rem-msgsize=REM-MSG-SIZE
Specifies the amount of data received in an individual t_rcv(3), t_listen(3), t_connect(3) or t_rcvconnect(3) call.
-r,--rrsize=[REQ-SIZE][,][RSP-SIZE]
Specifies the request (REQ-SIZE) or response (RSP-SIZE) size. At least one of REQ-SIZE or RSP-SIZE must be specified. If there is no comma (`,') in the option argument, then the specified size applies to both the request and response size.
-s,--loc-bufsize=[LOC-SNDBUF][,][LOC-RCVBUF]
Sets the local send (LOC-SNDBUF) and receive (LOC-RCVBUF) buffer sizes. One of LOC-SNDBUF and LOC-RCVBUF must be specified. If no comman (`,') is present in the option argument, then the specified buffer size applies to both the local send buffer size as well as the local receive buffer size.
-S,--rem-bufsize=[REM-SNDBUF][,][REM-RCVBUF]
Sets the remote send (REM-SNDBUF) and receive (REM-RCVBUF) buffer sizes. One of REM-SNDBUF and REM-RCVBUF must be specified. If no comman (`,') is present in the option argument, then the specified buffer size applies to both the remote send buffer size as well as the remote receive buffer size.
-V,--copyavoid
Ignored. Specify send and receive copy avoidance. This feature is not implemented for XTI_* tests.
-w,--rcv-width=RCV-WIDTH
Ignored.
-W,--snd-width=SND-WIDTH
Sets the SND-WIDTH of the user space data buffer. This will be the number of send sized buffers allocated in the *_STREAM and *_MAERTS tests. It may be enhanced to set both send and receive widths, but for now it is just the sending socket or stream in the *_STREAM and *_MAERTS tests.
-X,--devices=[LOC-DEVICE][,][REM-DEVICE]
Specifies the local (LOC-DEVICE) or remote (REM-DEVICE) device character special file of the appropriate type to open with t_open(3). At least one of LOC-DEVICE or REM-DEVICE must be specified. If there is no comma (`,') in the option argument, the specified device character special file applies to both the local and remote device file. The default device files are dependent upon the protocol tested and default as follows:

ProtocolFile

SCTP/dev/sctp
TCP/dev/tcp
UDP/dev/udp
FORE/dev/atm
DLPI/dev/dlpi
TICOTSORD/dev/ticotsord
TICOTS/dev/ticots
TICLTS/dev/ticlts

IPV6 OPTIONS

These tests include *IPV6_* tests as follows: SCTPIPV6_*, TCPIPV6_*, UDPIPV6_*.

-t,--testname=IPV6-TEST
Tests available for the POSIX/BSD IPV6 Sockets Interface consist of the following: SCTPIPV6_STREAM, SCTPIPV6_RR SCTPIPV6_CRR, SCTPIPV6_TRR, TCPIPV6_STREAM, TCPIPV6_RR, TCPIPV6_CRR, TCPIPV6_TRR, UDPIPV6_STREAM, UDPIPV6_RR. These tests use the BSD/POSIX IPv6 Sockets API.

IPv6 test specific options are specified on the command line following the first double-dash (`--'). Not all IPv6 options are applicable to all tests. The BSD/POSIX IPv6 Sockets API test specific options and arguments are as follows:

-h,--help
Prints a usage statement for the specified test and exits.
-D,--nodelay
Use option TCP_NODELAY or SCTP_NODELAY to suppress the Nagle algorithm with (or without) Minshal modifications.
-H,--hostname=HOSTNAME
Specify the remote HOSTNAME; this is separate from the global test option that controls the hostname for the control connection.
-m,--loc-msgsize=LOC-MSG-SIZE
Specifies the amount of data sent in an individual send(2) operation. This also affects the data sent with a sendto(2) call in the request response tests.
-M,--rem-msgsize=REM-MSG-SIZE
Specifies the amount of data received in an individual recv(2) call.
-p,--portrange=[MIN-PORTNUM][,][MAX-PORTNUM]
Specify the minimum and maximum port numbers used for the *_CRR and *_TRR tests. At least one of MIN-PORTNUM or MAX-PORTNUM must be specified. If there is no comma (`,') in the option argument, then the specified port number applies to both the minimum and maximum.
-r,--rrsize=[REQ-SIZE][,][RSP-SIZE]
Sets the request (REQ-SIZE) and response (RSP-SIZE) sizes. One of REQ-SIZE and RSP-SIZE must be specified. If there is no comma (`,') in the option argument, then the specified size applies to both the request and response size.
-s,--loc-bufsize=[LOC-SNDBUF][,][LOC-RCVBUF]
Sets the local send (LOC-SNDBUF) and receive (LOC-RCVBUF) buffer sizes. One of LOC-SNDBUF and LOC-RCVBUF must be specified. If no comman (`,') is present in the option argument, then the specified buffer size applies to both the local send buffer size as well as the local receive buffer size.
-S,--rem-bufsize=[REM-SNDBUF][,][REM-RCVBUF]
Sets the remote send (REM-SNDBUF) and receive (REM-RCVBUF) buffer sizes. One of REM-SNDBUF and REM-RCVBUF must be specified. If no comman (`,') is present in the option argument, then the specified buffer size applies to both the remote send buffer size as well as the remote receive buffer size.
-V,--copyavoid
Specify send and receive copy avoidance (HP-UX 9.0 and later only). This sets the socket options SO_SND_COPYAVOID and SO_RCV_COPYAVOID on the socket if these options are available available locally and will attempt to set them remotely.
-w,--rcv-width=RCV-WIDTH
Ignored.
-W,--snd-width=SND-WIDTH
Sets the SND-WIDTH of the user space data buffer. This will be the number of send sized buffers allocated in the *_STREAM and *_MAERTS tests. It may be enhanced to set both send and receive widths, but for now it is just the sending socket or stream in the *_STREAM and *_MAERTS tests.

UNIX OPTIONS

These tests include * tests as follows: STREAM_*, DG_*, LWPSTR_*, LWPDG_*.

-t,--testname=UNIX-TEST
Tests available for the POSIX/BSD Unix Domain Sockets Interface consist of the following: STREAM_STREAM, STREAM_RR, DG_STREAM, DG_RR, LWPSTR_STREAM, LWPSTR_RR, LWPDG_STREAM, LWPDG_RR. These tests use the BSD/POSIX Unix Domain Sockets API.

Unix test specific options are specified on the command line following the first double-dash (`--'). Not all Unix options are applicable to all tests. The BSD/POSIX Unix Domain Sockets API test specific options and arguments are as follows:

-h,--help
-m,--loc-msgsizeLOC-MSG-SIZE
Specifies the amount of data (in bytes) send in an individual send(2) operation. This also affects the data sent with a sendto(2) call int he request/response tests.
-M,--rem-msgsizeREM-MSG-SIZE
Sepcifies the amount of data received (in bytes) in an individual recv(2) call.
-p,--path=PATH
Specifies the path to the directory where temporary files are created. [Default: see tempnam(3)]
-s,--loc-bufsize[LOC-SNDBUF][,][LOC-RCVBUF]
Sets the local send (LOC-SNDBUF) and receive (LOC-RCVBUF) buffer sizes. One of LOC-RCVBUF and LOC-SNDBUF must be specified. If no comma (`,') is present in the option argument, then the specified buffer size applies to both the local send buffer size as well as the local receive buffer size.
-S,--rem-bufsize[REM-SNDBUF][,][REM-RCVBUF]
Sets the remote send (REM-SNDBUF) and receive (REM-RCVBUF) buffer sizes. One of REM-RCVBUF and REM-SNDBUF must be specified. If no comma (`,') is present in the option argument, then the specified buffer size applies to both the remote send buffer size as well as the remote receive buffer size.
-r,--rrsize[REQ-SIZE][,][RSP-SIZE]
Specifies the request (REQ-SIZE) or response (RSP-SIZE) size. At least one of REQ-SIZE or RSP-SIZE must be specified. If there is no comma (`,') in the option argument, then the specified size applies to both the request and response size.

DLPI OPTIONS

These tests include DLC?_* tests as follows: DLCO_*, DLCL_*.

-t,--testname=DLPI-TEST
Tests available for the DLPI Interface[8] consist of the following: DLCO_STREAM, DLCO_RR, DLCL_STREAM, DLCL_RR. These tests use the DLPI API[9].

DLPI test specific options are specified on the command line following the first double-dash (`--'). Not all DLPI options are applicable to all tests. The DLPI API test specific options are as follows:

-h,--help
Prints a usage statement for the specified test and exits.
-D,--devices=[LOC-DEVICE][,][REM-DEVICE]
Specifies the local (LOC-DEVICE) or remote (REM-DEVICE) device character special file of the appropriate type to open with open(2). At least one of LOC-DEVICE or REM-DEVICE must be specified. If there is no comma (`,') in the option argument, the specified device character special file applies to both the local and remote device file. The default device files are dependent upon the protocol tested and default as follows:

ProtocolFile

DLPI-CO/dev/dlpi_co
DLPI-CL/dev/dlpi_cl
-m,--loc-msgsize=LOC-MSG-SIZE
Specifies the amount of data sent in an individual send(2) operation. This also affects the data sent with a sendto(2) call in the request response tests.
-M,--rem-msgsize=REM-MSG-SIZE
Specifies the amount of data received in an individual recv(2) call.
-p,--ppas=[LOC-PPA][,][REM-PPA]
-r,--rrsize=[REQ-SIZE][,][RSP-SIZE]
Sets the local send (LOC-SNDBUF) and receive (LOC-RCVBUF) buffer sizes. One of LOC-SNDBUF and LOC-RCVBUF must be specified. If no comman (`,') is present in the option argument, then the specified buffer size applies to both the local send buffer size as well as the local receive buffer size.
-s,--sap=SAP
-w,--loc-window=[LOC-SND-WINDOW][,][LOC-RCV-WINDOW]
-W,--rem-window=[REM-SND-WINDOW][,][REM-RCV-WINDOW]

ATM OPTIONS

FORE_*

HIPPI OPTIONS

HIPPI_*

DNS OPTIONS

DNS_*

-h,--help
-f,--filename=FILENAME
-H,--hostname=HOSTNAME

TEST CATEGORIES

*_STREAM - Unidirectional Stream Tests
*_MAERTS - Unidirectional Stream Tests
*_RR - Request, Response Tests
*_NBRR - Non-Blocking Request, Response Test
*_CRR - Connect, Request, Response Tests
*_TRR - Transaction, Request, Response Tests
*_CC - Connect, Close Tests

SOCKETS API TESTS

The following tests utilize the X/Open XNS 5.2, SuSv2, SuSv3, POSIX 1003 Sockets interface to SCTP, TCP and UDP.

SCTP_STREAM - SCTP Unidirectional Stream Test
SCTP_MAERTS
SCTP_SENDFILE - SCTP Sendfile Test
SCTP_RR - SCTP Request/Response Test
SCTP_CRR - SCTP Connect/Request/Response Test
SCTP_CC - SCTP Connect/Close Test
SCTP_TRR
SCTP_NBRR
TCP_STREAM
TCP_MAERTS
TCP_SENDFILE
TCP_RR
TCP_CRR
TCP_CC
TCP_TRR
TCP_NBRR
UDP_STREAM
UDP_RR
STREAM_STREAM
STREAM_RR
DG_STREAM
DG_RR

LWP TESTS

LWPSTR_STREAM
LWPSTR_RR
LWPDG_STREAM
LWPDG_RR

IPV6 SOCKETS API TESTS

SCTPIPV6_STREAM
SCTPIPV6_RR
SCTPIPV6_CRR
TCPIPV6_STREAM
TCPIPV6_RR
TCPIPV6_CRR
UDPIPV6_STREAM
UDPIPV6_RR

XTI API TESTS

The following tests utilize the X/Open XNS 5.2 XTI/TLI[10] interface to SCTP, TCP and UDP.

XTI_SCTP_STREAM
XTI_SCTP_RR
XTI_TCP_STREAM
XTI_TCP_RR
XTI_UDP_STREAM
XTI_UDP_RR
XTI_CO_STREAM
XTI_CO_RR
XTI_CL_STREAM
XTI_CL_RR

DLPI TESTS

DLCO_STREAM
DLCO_RR
DLCL_STREAM
DLCL_RR

CPU TESTS

LOC_CPU
REM_CPU

FORE TESTS

FORE_STREAM
FORE_RR

HIPPI TESTS

HIPPI_STREAM
HIPPI_RR

DNS TESTS

DNS_RR

DIAGNOSTICS

When successful, netperf exits with a zero (0) exit status; when it fails, it exists with a non-zero exit status and prints a diagnostic message.

BUGS

There is a fairly large list of known defects and misfeatures in the manual. If you think you have found a bug, please send email to Rick Jones <raj@cup.hp.com>.

SEE ALSO

netserver(8)
Netperf: A Network Performance Benchmark
http://www.netperf.org/

COMPATIBILITY

netperf is compatible in all respects with the original netperf releases from HP.

CONFORMANCE

netperf does not conform to any standards.

HISTORY

netperf was developed by HP.

AUTHORS

HP Information Networks Division - Networking Performance Team.
Rick Jones<raj@cup.hp.com>

Karen ChoyHP IND

Dave Shield<daves@csc.liv.ac.uk>(man pages)

Others too numerous to mention here - see the ACKNWLDGMNTS file



Index

NAME
SYNOPSIS
DESCRIPTION
TESTS
PROTOCOLS
APPLICATION PROGRAMMING INTERFACES
BENCHMARKING PERFORMANCE TESTS
Unidirectional Stream Test
Request/Response Tests
CPU Synchronization Tests
OPTIONS
COMMAND OPTIONS
GLOBAL TEST OPTIONS
TEST SPECIFIC OPTIONS
SOCKETS OPTIONS
XTI OPTIONS
IPV6 OPTIONS
UNIX OPTIONS
DLPI OPTIONS
ATM OPTIONS
HIPPI OPTIONS
DNS OPTIONS
TEST CATEGORIES
SOCKETS API TESTS
LWP TESTS
IPV6 SOCKETS API TESTS
XTI API TESTS
DLPI TESTS
CPU TESTS
FORE TESTS
HIPPI TESTS
DNS TESTS
DIAGNOSTICS
BUGS
SEE ALSO
COMPATIBILITY
CONFORMANCE
HISTORY
AUTHORS

This document was created by man2html, using the manual pages.
Time: 17:15:49 GMT, October 17, 2017
OpenSS7
SS7 for the
Common Man
Home TopIndex FirstPrev Next LastMore Download Info FAQ Mail  Home -> Documentation -> Man Pages -> Manual Page
Last modified: Sat, 21 Jul 2007 19:34:31 GMT
© Copyright 1997-2007 OpenSS7 Corporation All Rights Reserved.