tree 915df4930f8ec48fc49d9b7249ada89d0559e307
parent 197d27ac767fed37228d21499ec118046cd486d4
parent 64d1be0fccbed41f1447872b954a03da363f9f15
author Bruce A. Mah <bmah@es.net> 1538159052 -0700
committer Bruce A. Mah <bmah@es.net> 1538159052 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQEzBAABCgAdFiEE+Fo4IENp9xo01E6DSYSRCoyq7ooFAluucpwACgkQSYSRCoyq
 7oq8jAf/YeyyUsD8XkbgDyG7yyShCcLcgle2XQVVutQZfBCNtNOeJhXf2xSBVrmY
 BjcMcYBVRWchxeglqxzhSrY7opigWv5yF9nBpdHIhZzKsXl6c0RWLN0My+bx4DbZ
 Q5wmeM99r/v20xHogaicCBb3ZZs3VM6sCEW/Zhx92K7UlWXFdRiwA4UmmIQnuY7O
 /CKC4V4T8tYgUGfuQ7ThCO3OK7wQStiYb4PI8ypja9PgrrmEn9a0pAcdiEqYAm4+
 /HxV9k16+ml3Ah4bc33NppfK9XVPlDpFe4OiMClqldO+ygl0QBDl/9fgCgWfmxhf
 6Ws34TF9P+gc58rgwslJO8Tgb9iDfw==
 =9bqY
 -----END PGP SIGNATURE-----

Add portable time abstraction (#738).  Fixes #253.

From author's notes (@ben-foxmore):

The current usage of gettimeofday causes issues for us when performing
tests shortly after restarting a system. In our setup, this occurs
often as we restart the system before each test to ensure reliable
results. We already maintain our own version of iperf for some subtle
changes, but this change feels like it might be useful to upstream.
(It's also a reasonable size change, so we'd prefer not maintain it
with each new version of iperf.)

It uses clock_gettime on systems that have it available, and falls
back to gettimeofday when it's not. These two options use different
structures for storing time - clock_gettime uses timespec, and
gettimeofday uses timeval. To provide abstraction to which one is
available, a separate iperf_time struct is defined to store time.

timespec has nanosecond accuracy, while timeval only has microseconds.
For the purposes of iperf, I don't think nanosecond accuracy is
neccesary, so iperf_time only uses microseconds, throwing away any
additional accuracy. Currently I have used the MONOTONIC clock, as I
think we only need a consistent time interval measure.