netperf and endianness

netperf and endianness

[David Miller]

Rick, I tried to use netperf between my x86-64 and sparc64 systems and
nothing works.

Does netperf do it's messaging in cpu byte order only?

I don't see anything in netperf-2.5.x that translates into and out of
network byte order :-/

Re: netperf and endianness

[Rick Jones]

On 06/07/2012 06:09 PM, David Miller wrote:
>
> Rick, I tried to use netperf between my x86-64 and sparc64 systems and
> nothing works.
>
> Does netperf do it's messaging in cpu byte order only?
>
> I don't see anything in netperf-2.5.x that translates into and out of
> network byte order :-/

David -

netperf sends things in network byte order.  It is all burried in 
send/recv_request and send/recv_response (in src/netlib.c).  Over the 
years I've run netperf between different endian systems with success. 
Chances are good that there is a netperf version mismatch between the 
sides - at least 99 times out of 10 that is what is happening when 
netperf doesn't work (other than with firewalls in place).

happy benchmarking,

rick jones

Re: netperf and endianness

[David Miller]

From: Rick Jones <rick.jones2@hp.com>
Date: Thu, 07 Jun 2012 18:16:14 -0700

> netperf sends things in network byte order.  It is all burried in
> send/recv_request and send/recv_response (in src/netlib.c).

Aha, I was grepping for things like ENDIAN when I should have
grepped for htonl() :-)

> Over the years I've run netperf between different endian systems
> with success. Chances are good that there is a netperf version
> mismatch between the sides - at least 99 times out of 10 that is
> what is happening when netperf doesn't work (other than with
> firewalls in place).

Indeed, you are right.  I was trying to speak to 2.4.4 using
2.5.0 :-)

Thanks!