From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Bob McMahon <bob.mcmahon@broadcom.com>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] iperf 2.0.14
Date: Fri, 24 Jan 2020 22:25:03 +0100 [thread overview]
Message-ID: <87d0b8fsy8.fsf@toke.dk> (raw)
In-Reply-To: <mailman.390.1579899149.1241.make-wifi-fast@lists.bufferbloat.net>
Bob McMahon via Make-wifi-fast <make-wifi-fast@lists.bufferbloat.net>
writes:
> From: Bob McMahon <bob.mcmahon@broadcom.com>
> Subject: iperf 2.0.14
> To: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
> Date: Fri, 24 Jan 2020 12:52:16 -0800
>
> Hi All,
>
> Just a heads up that iperf 2.0.14 <https://sourceforge.net/projects/iperf2/>
> is getting closer to a release. Feel free to suggest features that you
> might find helpful.
I have an old TODO item sitting around telling me to go over which
features we use from netperf in Flent that we don't currently use for
iperf. So thank you for the reminder; since I'm leaving for holidays
tomorrow, here is a quick overview (i.e., I haven't had time to go over
how many of these are actually missing from iperf, and how many are
there, but we're just not using them):
- We extract the following variables from netperf (-k option):
output_vars = 'THROUGHPUT,LOCAL_CONG_CONTROL,REMOTE_CONG_CONTROL,' \
'TRANSPORT_MSS,LOCAL_TRANSPORT_RETRANS,' \
'REMOTE_TRANSPORT_RETRANS,LOCAL_SOCKET_TOS,' \
'REMOTE_SOCKET_TOS,DIRECTION,ELAPSED_TIME,PROTOCOL,' \
'LOCAL_SEND_SIZE,LOCAL_RECV_SIZE,' \
'REMOTE_SEND_SIZE,REMOTE_RECV_SIZE,' \
'LOCAL_BYTES_SENT,LOCAL_BYTES_RECVD,' \
'REMOTE_BYTES_SENT,REMOTE_BYTES_RECVD'
- We pass in DUMP_TCP_INFO to netperf and capture the output (ref:
https://github.com/tohojo/flent/issues/13)
- We use the netperf features to set:
- diffserv markings
- TCP congestion control
- socket timeout
- For running the public test servers, the ability to just leave a
'netserver' instance running indefinitely and let it take care of
negotiating test setups. I don't think this works that well with
iperf?
If iperf can replicate all of that, it'll be fairly straight-forward to
make Flent backend-agnostic on the TCP test runner front. How much do
you reckon is currently missing, and what would it take to get that in? :)
-Toke
next parent reply other threads:[~2020-01-24 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.390.1579899149.1241.make-wifi-fast@lists.bufferbloat.net>
2020-01-24 21:25 ` Toke Høiland-Jørgensen [this message]
2020-01-24 23:24 ` Bob McMahon
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0b8fsy8.fsf@toke.dk \
--to=toke@redhat.com \
--cc=bob.mcmahon@broadcom.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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