Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Isaac Konikoff <isaac.konikoff@gmail.com>
To: Pete Heist <peteheist@gmail.com>
Cc: Bob McMahon <bob.mcmahon@broadcom.com>,
	make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Flent test hardware
Date: Mon, 6 Nov 2017 12:15:51 -0800	[thread overview]
Message-ID: <CA+wRhHGFGypZ3e2E9AFZEB4UdQKjbMvhS-_a+yx_0pssWPRgag@mail.gmail.com> (raw)
In-Reply-To: <95AE4A18-0329-42FA-91E2-9EFF356FD8C9@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3189 bytes --]

You can run flent/iperf/netperf client and server on the same box using a
candelatech kernel and then bind to specific interfaces.

http://candelatech.com/private/downloads/r5.3.6/ct4.9.29+.x64.tar.gz
guest/guest

flent example:
eth1 192.168.1.2 to DUT(AP LAN side)
wlan0 192.168.1.3 to DUT(AP wireless)

netserver
flent -H 192.168.1.3 --local-bind 192.168.1.2 --swap-up-down -x
tcp_download -l 120


iperf example:
eth1 192.168.86.103
wlan0 192.168.86.101

iperf upload test
iperf -s -B 192.168.86.103 -i10
iperf -c 192.168.86.103 -B 192.168.86.101 -i10 -t120

iperf download test
iperf -s -B 192.168.86.101 -i10
iperf -c 192.168.86.101 -B 192.168.86.103 -i10 -t120


On Sun, Nov 5, 2017 at 5:57 AM, Pete Heist <peteheist@gmail.com> wrote:

>
> On Nov 5, 2017, at 2:42 AM, Bob McMahon <bob.mcmahon@broadcom.com> wrote:
>
> I have some brix with realtek and run ptpd installed with fedora 25.
> The corrections are in the 25 microsecond range, though there are
> anomalies.  These are used for wifi DUTs that go into RF enclosures.
>
> [root@hera ~]# tail -n 1 /var/log/ptpd2.stats
> 2017-11-04 18:33:46.723476, slv, 0cc47afffea87386(unknown)/1,
> 0.000000000, -0.000018381,  0.000000000, -0.000018463, 1528.032750001, S,
> 0.000000000, 0, -0.000018988, 1403, 1576, 17, -0.000018463,  0.000000000
>
> For LAN/WAN traffic, I tend to use the intel quad server adapters in a
> supermicro mb desktop with 8 or more real cores.  (I think the data center
> class machines are worth it.)
>
>
> Thanks for the info. I was wondering how large the PTP error would be with
> software timestamps, and I see it’s not bad for most purposes.
>
> Which Realtek Linux driver does your brix use, and is it stable? The r8169
> driver’s BQL support was reverted at some point and it doesn’t look like
> that has changed.
>
> I trust that the extra cores can help, particularly for tests with high
> flow counts, but my project budget won’t allow it, and used hardware is too
> much to think about at the moment.
>
> Do you (or anyone) know of any problems with running the Flent client and
> server on the same box? In the case of the Proliant Microserver, the
> Broadcom 5720 adapter should have separate PCI data paths for each NIC. I
> guess the bottleneck will still mainly be the CPU. To get some idea of
> what's possible on my current hardware, I tried running rrul_be_nflows
> tests with the Flent client and server on the same box, through its local
> adapter (with MTU set to 1500) with my current Mac Mini (2.26 GHz Core2 Duo
> P7550). I know that doesn’t predict how it will work over Ethernet, but
> it’s a start.
>
> https://docs.google.com/spreadsheets/d/1MVxGsreiGKNXhfkMIheNFrH_
> GVllFfiH9RU5ws5l_aY/edit#gid=1583696271
>
> Although total throughput is pretty good for a low-end CPU, I’m not sure
> I’d trust the results above 64/64 flows. 256/256 flows was an epic fail,
> but I won’t be doing that kind of test.
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>

[-- Attachment #2: Type: text/html, Size: 4579 bytes --]

  parent reply	other threads:[~2017-11-06 20:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-04 13:33 Pete Heist
2017-11-04 15:06 ` Sebastian Moeller
2017-11-04 16:33   ` Pete Heist
2017-11-04 17:25     ` Sebastian Moeller
2017-11-04 18:45       ` Pete Heist
2017-11-05  1:42 ` Bob McMahon
2017-11-05 12:13   ` Jonathan Morton
2017-11-05 14:23     ` Pete Heist
     [not found]       ` <CAJq5cE0nkn+iDP9NuU2aoSk_G+2cxkZYShj9PfK5u=Fr7fTrLA@mail.gmail.com>
     [not found]         ` <CAJq5cE13M=fmyh2oQ5UxFCOcoPhZ2nOPEkqRWcT-UdGT60=ezA@mail.gmail.com>
     [not found]           ` <CAJq5cE1KQ+K9x7k+bnuFvqyNhjsg6mSn_CU4b0h8S1bwo5SXOg@mail.gmail.com>
     [not found]             ` <CAJq5cE2Tk_TAHES+7O28MjryG-nYHRNJ5OB9WjsCXGSfEgORog@mail.gmail.com>
     [not found]               ` <CAJq5cE0xkhbXYZ4c1+-9FmKOv1_DFFMJh8hqa-W8jEx+K_xTFg@mail.gmail.com>
2017-11-05 16:24                 ` Jonathan Morton
2017-11-05 17:39                   ` Pete Heist
2017-11-05 18:08                     ` Jonathan Morton
2017-11-05 18:42                       ` Pete Heist
2017-11-05 20:15                         ` Jonathan Morton
2017-11-07  0:32                           ` Pete Heist
2017-11-05 13:57   ` Pete Heist
2017-11-05 19:42     ` Bob McMahon
2017-11-05 21:41       ` Pete Heist
2017-11-06 20:15     ` Isaac Konikoff [this message]
2017-11-06 21:29       ` Bob McMahon
2017-11-07  0:39 ` Dave Taht
2017-11-07  1:37   ` Pete Heist
2017-11-07 10:21     ` Pete Heist
2017-11-08  4:46       ` 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=CA+wRhHGFGypZ3e2E9AFZEB4UdQKjbMvhS-_a+yx_0pssWPRgag@mail.gmail.com \
    --to=isaac.konikoff@gmail.com \
    --cc=bob.mcmahon@broadcom.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=peteheist@gmail.com \
    /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