* Throughput weirdness on 9984
@ 2016-09-02 21:11 Alexis Green
2016-09-02 21:51 ` Ben Greear
0 siblings, 1 reply; 4+ messages in thread
From: Alexis Green @ 2016-09-02 21:11 UTC (permalink / raw)
To: ath10k
Hello,
As I was working with ath10k drivers, I have discovered that only CT
firmware/driver combination is able to report tx_info to mac80211
layer. I've built latest LEDE image for my hardware (Netgear Nighthawk
X4S R7800) with both ath10k-ct driver from Ben and CT firmware. This
combination of software provides the data I need, however, the
throughput is severely limited :/
All tests are performed between two of these devices in mesh mode with
no encryption. Here are some of the iperf results:
NODE 1 (QCA) ----- NODE 2 (CT)
Iperf server on NODE 2
Connecting to host 192.168.1.2, port 5201
[ 4] local 192.168.1.1 port 41058 connected to 192.168.1.2 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 5.97 MBytes 50.0 Mbits/sec 0 242 KBytes
[ 4] 1.00-2.00 sec 6.75 MBytes 56.6 Mbits/sec 0 454 KBytes
[ 4] 2.00-3.00 sec 7.03 MBytes 58.9 Mbits/sec 0 734 KBytes
[ 4] 3.00-4.00 sec 6.60 MBytes 55.4 Mbits/sec 0 973 KBytes
[ 4] 4.00-5.00 sec 6.83 MBytes 57.3 Mbits/sec 0 1.13 MBytes
[ 4] 5.00-6.00 sec 6.36 MBytes 53.3 Mbits/sec 0 1.39 MBytes
[ 4] 6.00-7.00 sec 6.73 MBytes 56.6 Mbits/sec 0 1.65 MBytes
[ 4] 7.00-8.00 sec 6.54 MBytes 54.9 Mbits/sec 0 1.76 MBytes
[ 4] 8.00-9.00 sec 6.50 MBytes 54.4 Mbits/sec 0 1.76 MBytes
[ 4] 9.00-10.00 sec 6.74 MBytes 56.5 Mbits/sec 0 1.76 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 66.0 MBytes 55.4 Mbits/sec 0 sender
[ 4] 0.00-10.00 sec 65.3 MBytes 54.8 Mbits/sec receiver
----------------------------------------------------------------------------
NODE 1 (QCA) ----- NODE 2 (QCA)
Iperf server on NODE 2
Connecting to host 192.168.1.2, port 5201
[ 4] local 192.168.1.1 port 58770 connected to 192.168.1.2 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 22.9 MBytes 191 Mbits/sec 0 157 KBytes
[ 4] 1.00-2.02 sec 26.3 MBytes 217 Mbits/sec 0 296 KBytes
[ 4] 2.02-3.05 sec 30.7 MBytes 251 Mbits/sec 0 622 KBytes
[ 4] 3.05-4.02 sec 30.0 MBytes 260 Mbits/sec 0 930 KBytes
[ 4] 4.02-5.02 sec 33.9 MBytes 283 Mbits/sec 0 930 KBytes
[ 4] 5.02-6.04 sec 32.5 MBytes 269 Mbits/sec 0 1.00 MBytes
[ 4] 6.04-7.02 sec 36.2 MBytes 310 Mbits/sec 0 1.11 MBytes
[ 4] 7.02-8.06 sec 38.6 MBytes 312 Mbits/sec 0 1.28 MBytes
[ 4] 8.06-9.01 sec 34.9 MBytes 307 Mbits/sec 0 1.42 MBytes
[ 4] 9.01-10.04 sec 37.3 MBytes 304 Mbits/sec 0 1.49 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.04 sec 323 MBytes 270 Mbits/sec 0 sender
[ 4] 0.00-10.04 sec 322 MBytes 269 Mbits/sec receiver
-----------------------------------------------------------------------------
NODE 1 (CT) ----- NODE 2 (QCA)
Iperf server on NODE 2
Connecting to host 192.168.1.2, port 5201
[ 4] local 192.168.1.1 port 36820 connected to 192.168.1.2 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 2.09 MBytes 17.5 Mbits/sec 0 22.6 KBytes
[ 4] 1.00-2.00 sec 1.16 MBytes 9.71 Mbits/sec 0 22.6 KBytes
[ 4] 2.00-3.00 sec 1.12 MBytes 9.43 Mbits/sec 0 22.6 KBytes
[ 4] 3.00-4.00 sec 1.13 MBytes 9.45 Mbits/sec 0 22.6 KBytes
[ 4] 4.00-5.00 sec 1.12 MBytes 9.38 Mbits/sec 0 22.6 KBytes
[ 4] 5.00-6.00 sec 1.12 MBytes 9.36 Mbits/sec 0 22.6 KBytes
[ 4] 6.00-7.00 sec 1.16 MBytes 9.73 Mbits/sec 0 22.6 KBytes
[ 4] 7.00-8.00 sec 1.16 MBytes 9.71 Mbits/sec 0 22.6 KBytes
[ 4] 8.00-9.00 sec 1.13 MBytes 9.48 Mbits/sec 0 22.6 KBytes
[ 4] 9.00-10.00 sec 1.12 MBytes 9.41 Mbits/sec 0 22.6 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 12.3 MBytes 10.3 Mbits/sec 0 sender
[ 4] 0.00-10.00 sec 12.3 MBytes 10.3 Mbits/sec receiver
-----------------------------------------------------------------------------
NODE 1 (CT) ----- NODE 2 (CT)
Iperf server on NODE 2
*Unable to establish peering until I add monitor mode devices on both sides.*
Connecting to host 192.168.1.2, port 5201
[ 4] local 192.168.1.1 port 41328 connected to 192.168.1.2 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 1.51 MBytes 12.7 Mbits/sec 0 31.1 KBytes
[ 4] 1.00-2.00 sec 1.47 MBytes 12.4 Mbits/sec 0 31.1 KBytes
[ 4] 2.00-3.00 sec 1.46 MBytes 12.2 Mbits/sec 0 31.1 KBytes
[ 4] 3.00-4.00 sec 1.49 MBytes 12.5 Mbits/sec 0 31.1 KBytes
[ 4] 4.00-5.00 sec 1.55 MBytes 13.0 Mbits/sec 0 31.1 KBytes
[ 4] 5.00-6.00 sec 1.49 MBytes 12.5 Mbits/sec 0 31.1 KBytes
[ 4] 6.00-7.00 sec 1.59 MBytes 13.3 Mbits/sec 0 31.1 KBytes
[ 4] 7.00-8.00 sec 1.36 MBytes 11.4 Mbits/sec 0 31.1 KBytes
[ 4] 8.00-9.00 sec 1.77 MBytes 14.9 Mbits/sec 0 48.1 KBytes
[ 4] 9.00-10.00 sec 2.92 MBytes 24.5 Mbits/sec 0 48.1 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 16.6 MBytes 13.9 Mbits/sec 0 sender
[ 4] 0.00-10.00 sec 16.5 MBytes 13.9 Mbits/sec receiver
Another strange thing I noticed was inability to mesh two devices
running CT firmware until I created monitor mode devices - this leads
me to believe that there's some kind of filtering bug.
I've tried several different CT firmware versions -
http://www.candelatech.com/downloads/ath10k-9984-10-4/ath10k-fw-beta/firmware-5-ct-full-community.bin
http://www.candelatech.com/downloads/ath10k-9984-10-4/firmware-5-ct-full-community-7.bin-lede.001
http://www.candelatech.com/downloads/ath10k-9984-10-4/firmware-5-ct-full-community-7.bin-lede.004
- all of them behave in similar ways.
P.S. Both devices are running in VHT80 mode on channel 36 and
generally report very good connection (-30dBm-ish).
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Throughput weirdness on 9984
2016-09-02 21:11 Throughput weirdness on 9984 Alexis Green
@ 2016-09-02 21:51 ` Ben Greear
2016-09-02 22:14 ` Alexis Green
0 siblings, 1 reply; 4+ messages in thread
From: Ben Greear @ 2016-09-02 21:51 UTC (permalink / raw)
To: Alexis Green, ath10k
On 09/02/2016 02:11 PM, Alexis Green wrote:
> Hello,
>
> As I was working with ath10k drivers, I have discovered that only CT
> firmware/driver combination is able to report tx_info to mac80211
> layer. I've built latest LEDE image for my hardware (Netgear Nighthawk
> X4S R7800) with both ath10k-ct driver from Ben and CT firmware. This
> combination of software provides the data I need, however, the
> throughput is severely limited :/
>
> All tests are performed between two of these devices in mesh mode with
> no encryption. Here are some of the iperf results:
I have not actually tested mesh-mode on my firmware, so maybe I caused
regressions related to that.
If you use AP + STA config, is throughput better?
What about IBSS?
What tx/rx rates is CT firmware actually reporting? Maybe it is not
enabling HT/VHT for some reason?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Throughput weirdness on 9984
2016-09-02 21:51 ` Ben Greear
@ 2016-09-02 22:14 ` Alexis Green
2016-09-02 22:52 ` Ben Greear
0 siblings, 1 reply; 4+ messages in thread
From: Alexis Green @ 2016-09-02 22:14 UTC (permalink / raw)
To: Ben Greear; +Cc: ath10k
I just ran run AP + STA mode and it appears to behave the same way.
Also, as far as reported rates, it appears that the rates are similar.
------------------------
CT - 10.4.3-ct-fW-007-71d92ff
QCA - 10.4-3.2-00072
AP running CT, STA running QCA:
Station dump on AP device:
Station 00:34:56:78:24:24 (on wlan0)
inactive time: 4590 ms
rx bytes: 37230937
rx packets: 24305
tx bytes: 1049354
tx packets: 12201
tx retries: 0
tx failed: 0
signal: -36 dBm
signal avg: -34 dBm
tx bitrate: 1404.0 MBit/s VHT-MCS 8 80MHz VHT-NSS 4
rx bitrate: 1733.3 MBit/s VHT-MCS 9 80MHz short GI VHT-NSS 4
authorized: yes
authenticated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
connected time: 41 seconds
Station dump on STA:
Station 00:34:56:78:fe:fe (on wlan0)
inactive time: 88780 ms
rx bytes: 1275608
rx packets: 14647
tx bytes: 37230967
tx packets: 24305
tx retries: 0
tx failed: 0
signal: -25 dBm
signal avg: -26 dBm
tx bitrate: 6.0 MBit/s
rx bitrate: 1560.0 MBit/s VHT-MCS 8 80MHz short GI VHT-NSS 4
authorized: yes
authenticated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
connected time: 126 seconds
iperf output
Connecting to host 192.168.1.2, port 5201
[ 4] local 192.168.1.1 port 48788 connected to 192.168.1.2 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 3.19 MBytes 26.7 Mbits/sec 0 35.4 KBytes
[ 4] 1.00-2.00 sec 3.31 MBytes 27.8 Mbits/sec 0 35.4 KBytes
[ 4] 2.00-3.00 sec 3.31 MBytes 27.8 Mbits/sec 0 35.4 KBytes
[ 4] 3.00-4.00 sec 3.27 MBytes 27.4 Mbits/sec 0 35.4 KBytes
[ 4] 4.00-5.00 sec 3.48 MBytes 29.2 Mbits/sec 0 35.4 KBytes
[ 4] 5.00-6.00 sec 3.28 MBytes 27.5 Mbits/sec 0 35.4 KBytes
[ 4] 6.00-7.00 sec 3.31 MBytes 27.8 Mbits/sec 0 35.4 KBytes
[ 4] 7.00-8.00 sec 3.32 MBytes 27.9 Mbits/sec 0 35.4 KBytes
[ 4] 8.00-9.00 sec 3.59 MBytes 30.1 Mbits/sec 0 35.4 KBytes
[ 4] 9.00-10.00 sec 3.49 MBytes 29.3 Mbits/sec 0 35.4 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 33.5 MBytes 28.1 Mbits/sec 0 sender
[ 4] 0.00-10.00 sec 33.5 MBytes 28.1 Mbits/sec receiver
------------------------------------------------
AP running QCA, STA running CT:
Station dump on AP:
Station 00:34:56:78:00:00 (on wlan0)
inactive time: 8470 ms
rx bytes: 31376541
rx packets: 20483
tx bytes: 898358
tx packets: 10451
tx retries: 0
tx failed: 0
signal: -33 dBm
signal avg: -33 dBm
tx bitrate: 6.0 MBit/s
rx bitrate: 1560.0 MBit/s VHT-MCS 8 80MHz short GI VHT-NSS 4
authorized: yes
authenticated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
connected time: 178 seconds
Station dump on STA:
Station 00:34:56:78:1d:1d (on wlan0)
inactive time: 4260 ms
rx bytes: 1209897
rx packets: 13819
tx bytes: 31376571
tx packets: 20483
tx retries: 0
tx failed: 0
signal: -25 dBm
signal avg: -25 dBm
tx bitrate: 1404.0 MBit/s VHT-MCS 8 80MHz VHT-NSS 4
rx bitrate: 1733.3 MBit/s VHT-MCS 9 80MHz short GI VHT-NSS 4
authorized: yes
authenticated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
connected time: 174 seconds
iperf output:
Connecting to host 192.168.1.2, port 5201
[ 4] local 192.168.1.1 port 58162 connected to 192.168.1.2 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 2.13 MBytes 17.9 Mbits/sec 0 32.5 KBytes
[ 4] 1.00-2.00 sec 2.45 MBytes 20.6 Mbits/sec 0 33.9 KBytes
[ 4] 2.00-3.00 sec 2.97 MBytes 24.9 Mbits/sec 0 38.2 KBytes
[ 4] 3.00-4.00 sec 2.93 MBytes 24.6 Mbits/sec 0 52.3 KBytes
[ 4] 4.00-5.00 sec 2.96 MBytes 24.8 Mbits/sec 0 73.5 KBytes
[ 4] 5.00-6.00 sec 3.01 MBytes 25.2 Mbits/sec 0 115 KBytes
[ 4] 6.00-7.00 sec 3.01 MBytes 25.3 Mbits/sec 0 168 KBytes
[ 4] 7.00-8.00 sec 3.02 MBytes 25.3 Mbits/sec 0 242 KBytes
[ 4] 8.00-9.00 sec 3.20 MBytes 26.9 Mbits/sec 0 335 KBytes
[ 4] 9.00-10.00 sec 3.36 MBytes 28.1 Mbits/sec 0 462 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 29.0 MBytes 24.3 Mbits/sec 0 sender
[ 4] 0.00-10.00 sec 28.2 MBytes 23.6 Mbits/sec receiver
-------------------------------------------------
Both devices running QCA:
Station dump on AP:
Station 00:34:56:78:05:05 (on wlan0)
inactive time: 7460 ms
rx bytes: 358469390
rx packets: 233800
tx bytes: 6435927
tx packets: 74855
tx retries: 0
tx failed: 0
signal: -33 dBm
signal avg: -33 dBm
tx bitrate: 6.0 MBit/s
rx bitrate: 1560.0 MBit/s VHT-MCS 8 80MHz short GI VHT-NSS 4
authorized: yes
authenticated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
connected time: 115 seconds
Station dump on STA:
Station 00:34:56:78:09:09 (on wlan0)
inactive time: 3590 ms
rx bytes: 6633321
rx packets: 76989
tx bytes: 358469420
tx packets: 233800
tx retries: 0
tx failed: 0
signal: -27 dBm
signal avg: -25 dBm
tx bitrate: 6.0 MBit/s
rx bitrate: 1733.3 MBit/s VHT-MCS 9 80MHz short GI VHT-NSS 4
authorized: yes
authenticated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
connected time: 111 seconds
iperf output:
Connecting to host 192.168.1.2, port 5201
[ 4] local 192.168.1.1 port 47046 connected to 192.168.1.2 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 24.3 MBytes 203 Mbits/sec 0 129 KBytes
[ 4] 1.00-2.00 sec 27.2 MBytes 228 Mbits/sec 0 153 KBytes
[ 4] 2.00-3.00 sec 25.3 MBytes 213 Mbits/sec 0 168 KBytes
[ 4] 3.00-4.00 sec 26.2 MBytes 220 Mbits/sec 0 168 KBytes
[ 4] 4.00-5.00 sec 26.1 MBytes 219 Mbits/sec 0 262 KBytes
[ 4] 5.00-6.01 sec 35.3 MBytes 294 Mbits/sec 0 843 KBytes
[ 4] 6.01-7.01 sec 41.7 MBytes 351 Mbits/sec 0 1.29 MBytes
[ 4] 7.01-8.01 sec 37.3 MBytes 311 Mbits/sec 0 1.62 MBytes
[ 4] 8.01-9.00 sec 40.3 MBytes 342 Mbits/sec 0 1.88 MBytes
[ 4] 9.00-10.01 sec 41.0 MBytes 340 Mbits/sec 0 1.88 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.01 sec 325 MBytes 272 Mbits/sec 0 sender
[ 4] 0.00-10.01 sec 322 MBytes 270 Mbits/sec receiver
Hope this helps,
Alexis
On Fri, Sep 2, 2016 at 2:51 PM, Ben Greear <greearb@candelatech.com> wrote:
> On 09/02/2016 02:11 PM, Alexis Green wrote:
>>
>> Hello,
>>
>> As I was working with ath10k drivers, I have discovered that only CT
>> firmware/driver combination is able to report tx_info to mac80211
>> layer. I've built latest LEDE image for my hardware (Netgear Nighthawk
>> X4S R7800) with both ath10k-ct driver from Ben and CT firmware. This
>> combination of software provides the data I need, however, the
>> throughput is severely limited :/
>>
>> All tests are performed between two of these devices in mesh mode with
>> no encryption. Here are some of the iperf results:
>
>
> I have not actually tested mesh-mode on my firmware, so maybe I caused
> regressions related to that.
>
> If you use AP + STA config, is throughput better?
>
> What about IBSS?
>
> What tx/rx rates is CT firmware actually reporting? Maybe it is not
> enabling HT/VHT for some reason?
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb@candelatech.com>
> Candela Technologies Inc http://www.candelatech.com
>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Throughput weirdness on 9984
2016-09-02 22:14 ` Alexis Green
@ 2016-09-02 22:52 ` Ben Greear
0 siblings, 0 replies; 4+ messages in thread
From: Ben Greear @ 2016-09-02 22:52 UTC (permalink / raw)
To: Alexis Green; +Cc: ath10k
On 09/02/2016 03:14 PM, Alexis Green wrote:
> I just ran run AP + STA mode and it appears to behave the same way.
> Also, as far as reported rates, it appears that the rates are similar.
I just ran a quick test with 9984 as STA and a 9880 3x3 AP, over-the-air, UDP
Download about 550Mbps, Upload about 350Mbps.
I'm using a different compile than what is in LEDE, will send it to you
directly.
Could also be that for whatever reason connecting to a non 9984 AP 'fixes' things.
I don't have two functional 9984 systems to test against at this point, but should
have something soon.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-09-02 23:06 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-09-02 21:11 Throughput weirdness on 9984 Alexis Green
2016-09-02 21:51 ` Ben Greear
2016-09-02 22:14 ` Alexis Green
2016-09-02 22:52 ` Ben Greear
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.