* netperf and endianness
@ 2012-06-08 1:09 David Miller
2012-06-08 1:16 ` Rick Jones
0 siblings, 1 reply; 3+ messages in thread
From: David Miller @ 2012-06-08 1:09 UTC (permalink / raw)
To: rick.jones2; +Cc: netdev
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 :-/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: netperf and endianness
2012-06-08 1:09 netperf and endianness David Miller
@ 2012-06-08 1:16 ` Rick Jones
2012-06-08 1:20 ` David Miller
0 siblings, 1 reply; 3+ messages in thread
From: Rick Jones @ 2012-06-08 1:16 UTC (permalink / raw)
To: David Miller; +Cc: netdev
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: netperf and endianness
2012-06-08 1:16 ` Rick Jones
@ 2012-06-08 1:20 ` David Miller
0 siblings, 0 replies; 3+ messages in thread
From: David Miller @ 2012-06-08 1:20 UTC (permalink / raw)
To: rick.jones2; +Cc: netdev
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!
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-06-08 1:20 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-06-08 1:09 netperf and endianness David Miller
2012-06-08 1:16 ` Rick Jones
2012-06-08 1:20 ` David Miller
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).