Re: Iperf & 10 Gbit/s
In the next major version of Iperf we will have the autoconf script
defining any 64 bit type to int64_t and it will be used appropriately. The
shift from double to int on UDPRate was due to bidirectional testing and
the need for a platform independant representation of numbers (aka
floating point does not fly the wire very well). We can/will change that
to a 64 bit value as well in the future. Sorry for any inconvience.
Kevin
On Mon, 2 Jun 2003, Hans Blom wrote:
> Hello,
>
> To make Iperf also useful with 10 Gbit/s connections, Integer
> calculation should definitely be performed with 64 bit Integers. As has
> been reported before, in "lib/headers.h" there should be checked if the
> type "long long" could also be used for "max_size_t" and not only
> "int64_t". In the versions we use, we modified "lib/headers.h" to use
> "long long" when "HAVE_INT64_T" has been defined, but an autoconfig
> check for that would be much more convenient.
>
> Typical also a variable / struct element as "mUDPRate" for UDP shaping
> and connected calculations should be in 64 bit Integer or Double.
> Therefore, the changing of the type of "mUDPRate" from "double" in
> V. 1.6.5 into "int" in "V. 1.7.0" is really no improvement. It forces us
> to use still V. 1.6.5.
>
> Would it be possible to use in the next (sub)versions of Iperf
> 64 bit Integer or Double calculations when required?
>
> Kind regards,
> Hans
>