Lines Matching refs:test

44           can test TCP, UDP, or SCTP throughput.  To perform an iperf3  test  the
83           The initial TCP connection is used to exchange test parameters, control
84           the start and end of the test, and to exchange test results.   This  is
85           sometimes  referred  to  as  the "control connection".  The actual test
90           Normally, the test data is sent from the client to the server, and mea-
101           start  of the test, amount of data transferred during the interval, and
107           At  the  end of the test is a set of statistics that shows (at least as
108           much as possible) a summary of the test as seen by both the sender  and
114           test by specifying the --get-server-output flag.
119           known after the test has finished, no JSON output will be emitted until
120           the end of the test.
123           used  to  set the parameters of a test.  They are given in the "GENERAL
157                  server's affinity for just that one test, using the n,m form  of
194                  receiver will halt a test if no data is received from the sender
226                  set a limit on the server side, which will cause a test to abort
227                  if  the  client specifies a test of more than n bits per second,
254                  default,  a test consists of sending data from the client to the
300                  test.  Only available on platforms  supporting  the  SO_MAX_PAC-
334                  reverse the direction of a test, so that the server  sends  data
338                  test  in  both  directions  (normal  and reverse), with both the
398                  Omit the first n seconds of the test, to skip past the TCP slow-
422                  Use 64-bit counters in UDP test packets.  The use of this option
431                  might  help  to test and reveal problems in networking gear with
443                  actively  when  the  test is run.  Note, the password to use can