From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: netperf and endianness
Date: Thu, 07 Jun 2012 18:16:14 -0700 [thread overview]
Message-ID: <4FD1525E.5020707@hp.com> (raw)
In-Reply-To: <20120607.180948.471478622905736125.davem@davemloft.net>
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
next prev parent reply other threads:[~2012-06-08 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 1:09 netperf and endianness David Miller
2012-06-08 1:16 ` Rick Jones [this message]
2012-06-08 1:20 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FD1525E.5020707@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.