From: Rick Jones <rick.jones2@hp.com>
To: linux-wireless@vger.kernel.org
Subject: Question about netperf terminology in the RTL8192SE and 802.11n problem thread
Date: Thu, 08 Sep 2011 16:54:32 -0700 [thread overview]
Message-ID: <4E6955B8.4000900@hp.com> (raw)
Hi -
From time to time I web search for instances of netperf usage, and came
across http://www.spinics.net/lists/linux-wireless/msg76387.html which
has verbiage like:
> TCP_MAERTS TX Test: 47.33 53.94 55.19 44.24 57.74 55.44 53.74 54.63 47.87 57.82
> TCP_MAERTS RX Test: 66.02 69.79 67.70 52.15 82.56 80.30 79.43 80.98 76.26 71.34
> Results: TX: max 57.82, min 44.24. Mean 52.79(4.42)
> RX: max 82.56, min 52.15. Mean 72.65(8.85)
>
> TCP_STREAM TX Test: 71.83 80.44 72.88 26.11 40.85 58.70 58.49 58.96 59.52 59.35
> TCP_STREAM RX Test: 46.41 52.64 43.85 48.44 52.15 49.66 52.81 50.61 43.18 52.93
> Results: TX: max 80.44, min 26.11. Mean 58.71(14.93)
> RX: max 52.93, min 43.18. Mean 49.27(3.51)
>
> TCP_SENDFILE TX Test: 57.86 55.94 55.21 56.13 56.70 61.71 56.85 54.68 55.04 51.30
> TCP_SENDFILE RX Test: 37.82 47.51 41.61 42.88 45.37 35.11 45.09 40.11 46.48 22.86
> Results: TX: max 61.71, min 51.30. Mean 56.14(2.50)
> RX: max 47.51, min 22.86. Mean 40.48(6.96)
in it. Seeing separate TX and RX lines for netperf TCP tests is
unfamiliar to me and I was wondering if someone (Stephan?) could explain
the split? Netperf itself tends to emit only the one figure for a
transfer rate (measured up at the socket level). (Modulo some of the
recentish omni output selectors anyway, though for a TCP transfer test
they would/should be very very similar...)
thanks, and happy benchmarking,
rick jones
next reply other threads:[~2011-09-09 0:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 23:54 Rick Jones [this message]
2011-09-09 0:53 ` Question about netperf terminology in the RTL8192SE and 802.11n problem thread Larry Finger
2011-09-09 16:28 ` Rick Jones
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=4E6955B8.4000900@hp.com \
--to=rick.jones2@hp.com \
--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 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.