From: Rick Jones <rick.jones2@hp.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Question about netperf terminology in the RTL8192SE and 802.11n problem thread
Date: Fri, 09 Sep 2011 09:28:58 -0700 [thread overview]
Message-ID: <4E6A3ECA.9010809@hp.com> (raw)
In-Reply-To: <4E696378.3060005@lwfinger.net>
> Those numbers are from my tests. The TX numbers are the standard netperf
> output and give the rate from my test laptop to a server that is wired
> to the AP/router. Those are the numbers that you are used to.
>
> The RX numbers are obtained by starting a server on my laptop and
> ssh'ing a netperf command to the machine that was the server in the TX
> tests, i.e. I am measuring the TX rate from the former server, or the RX
> rate for the laptop. My script does 10 samples of each and calculates
> the mean and standard deviation.
Thanks. If I have interpreted your answer correctly what you call
TCP_STREAM RX should be the same as TCP_MAERTS TX and vice versa
(modulo having the same -s, -S, -m and -M values or system defaults
anyway) Ie
system-A> netperf -H system-B -t TCP_MAERTS ...
should be the same as
system-A> ssh system-B netperf -H system-A -t TCP_STREAM
I put the TCP_MAERTS test into netperf specifically to help people avoid
having to ssh :)
happy benchmarking,
rick jones
PS, if I or anyone else ever gets around to implementing the sendfile
functionality in the "omni" tests, then they should also provide what we
might call a TCP_ELIFDNES test - the netserver side calling sendfile()
to send data to the netperf side.
prev parent reply other threads:[~2011-09-09 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 23:54 Question about netperf terminology in the RTL8192SE and 802.11n problem thread Rick Jones
2011-09-09 0:53 ` Larry Finger
2011-09-09 16:28 ` Rick Jones [this message]
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=4E6A3ECA.9010809@hp.com \
--to=rick.jones2@hp.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@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 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).