From: Roman Yeryomin <leroi.lists@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net,
"codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: [Make-wifi-fast] iperf3 udp flood behavior at higher rates
Date: Wed, 4 May 2016 11:13:10 +0300 [thread overview]
Message-ID: <CACiydbL6QaER-zrP5ZBRe-x5PLOoU7goAnquzGHVXTpt_g+STg@mail.gmail.com> (raw)
In-Reply-To: <CACiydbJGpyak1jCm+eqG=xez4wP4AFciYf5DvQCu4-8E7A_Xyw@mail.gmail.com>
On 4 May 2016 at 11:02, Roman Yeryomin <leroi.lists@gmail.com> wrote:
> On 3 May 2016 at 02:18, Dave Taht <dave.taht@gmail.com> wrote:
>> to fork the fq_codel_drop discussion a bit...
>>
>> I have up and running two new boxes[1] that are my hope to be able to
>> test ath10k/ath9k hardware with, for this test, using one in the
>> middle as a router and a nuc i3 box as the server, all ports pure
>> ethernet... there's a switch in the way, too.
>>
>> On tcp via netperf I get expected ~940 mbits.
>>
>> On udp via iperf3 (again, all pure ethernet) - in neither case below
>> am I seeing any drops in the qdisc itself anywhere on the path, yet am
>> only achieving 500mbit.
>
> That's interesting, I have no problems with UDP over ethernet.
> What about TCP with iperf3?
>
Also what version of iperf3 are you using?
Regards,
Roman
prev parent reply other threads:[~2016-05-04 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 23:18 Dave Taht
2016-05-02 23:27 ` [Make-wifi-fast] [Codel] " Rick Jones
2016-05-03 0:07 ` Dave Taht
2016-05-04 8:02 ` [Make-wifi-fast] " Roman Yeryomin
2016-05-04 8:13 ` Roman Yeryomin [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
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=CACiydbL6QaER-zrP5ZBRe-x5PLOoU7goAnquzGHVXTpt_g+STg@mail.gmail.com \
--to=leroi.lists@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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