From: Mathias Kresin <dev@kresin.me>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Daniel Golle <daniel@makrotopia.org>,
Enrico Mioso <mrkiko.rs@gmail.com>,
Tom Psyborg <pozega.tomislav@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes.berg@intel.com>,
Arnd Bergmann <arnd@arndb.de>, John Crispin <john@phrozen.org>,
Felix Fietkau <nbd@nbd.name>, Jamie Stuart <jamie@onebillion.org>
Subject: Re: ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue...?
Date: Tue, 27 Mar 2018 09:46:36 +0200 [thread overview]
Message-ID: <24f8f4a2-b355-a1b3-d07a-940fc1e50fcc@kresin.me> (raw)
In-Reply-To: <20180326103551.GA2069@redhat.com>
26.03.2018 12:35, Stanislaw Gruszka:
> Hi Mathias
>
>> sorry for the delayed testing. I had to create a new test setup
>> first, fought with buggy hardware and was busy with other stuff.
>
> Thanks for doing it.
>
>> The two attached patches are causing a performance regression for me again:
>>
>> OpenWrt head (forced HT40, 100Mbit wired interface)
>>
>> wireless (iperf client) to wired (iperf server)
>> Interval Transfer Bitrate Retr
>> 0.00-60.00 sec 584 MBytes 81.6 Mbits/sec 666 sender
>> 0.00-60.00 sec 584 MBytes 81.6 Mbits/sec receiver
>>
>> wired (iperf client) to wireless (iperf server)
>> Interval Transfer Bitrate Retr
>> 0.00-60.00 sec 620 MBytes 86.7 Mbits/sec 33 sender
>> 0.00-60.00 sec 617 MBytes 86.2 Mbits/sec receiver
>>
>>
>>
>> OpenWrt head (forced HT40, 100Mbit wired interface)
>> + rt2800_change_rx_ampdu_factor.patch
>> + rt2800_change_ba_size.patch
>>
>> wireless (iperf client) to wired (iperf server)
>> Interval Transfer Bitrate Retr
>> 0.00-60.00 sec 356 MBytes 49.8 Mbits/sec 6 sender
>> 0.00-60.00 sec 356 MBytes 49.7 Mbits/sec receiver
>>
>> wired (iperf client) to wireless (iperf server)
>> Interval Transfer Bitrate Retr
>> 0.00-60.00 sec 627 MBytes 87.7 Mbits/sec 5 sender
>> 0.00-60.00 sec 626 MBytes 87.5 Mbits/sec receiver
>>
>>
>> Due to the regression I haven't tested your ampdu_density patch so
>> far. Let me hear if you want to see more tests done.
>
> Could you test just RX AMPDU patches, i.e.
>
> rt2800_change_rx_ampdu_factor.patch
> rt2800_change_rx_ampdu_density.patch
>
> I have somewhat positive results on RX performance on some devices
> with those. Perhaps you could confirm that :-)
This time I've done the test with HT20 only, to not annoy my neighbours.
The test setup is the following:
ath9k (STA) <=> (AP) o2 Box 6431 (RJ45) <=> desktop
With the patches applied the bandwidth is somewhat around 10 MBit/sec
lower. Even if I was able to reliable reproduce it, I'm not sure if it
is within the measuring tolerance.
OpenWrt head
mkresin@desktop ~ $ iperf3 -c 192.168.1.156
Connecting to host 192.168.1.156, port 5201
Interval Transfer Bandwidth Retr
0.00-10.00 sec 89.5 MBytes 75.0 Mbits/sec 1 sender
0.00-10.00 sec 88.2 MBytes 74.0 Mbits/sec receiver
mkresin@desktop ~ $ iperf3 -c 192.168.1.156 -R
Connecting to host 192.168.1.156, port 5201
Reverse mode, remote host 192.168.1.156 is sending
Interval Transfer Bandwidth Retr
0.00-10.00 sec 70.8 MBytes 59.4 Mbits/sec 0 sender
0.00-10.00 sec 70.5 MBytes 59.1 Mbits/sec receiver
OpenWrt head
+ rt2800_change_rx_ampdu_factor.patch
+ rt2800_change_rx_ampdu_density.patch
mkresin@desktop ~ $ iperf3 -c 192.168.1.156
Connecting to host 192.168.1.156, port 5201
Interval Transfer Bandwidth Retr
0.00-10.00 sec 78.2 MBytes 65.6 Mbits/sec 0 sender
0.00-10.00 sec 77.1 MBytes 64.7 Mbits/sec receiver
mkresin@desktop ~ $ iperf3 -c 192.168.1.156 -R
Connecting to host 192.168.1.156, port 5201
Reverse mode, remote host 192.168.1.156 is sending
Interval Transfer Bandwidth Retr
0.00-10.00 sec 51.8 MBytes 43.5 Mbits/sec 1 sender
0.00-10.00 sec 51.7 MBytes 43.3 Mbits/sec receiver
Mathias
next prev parent reply other threads:[~2018-03-27 7:49 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 20:51 ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue...? Enrico Mioso
2017-12-13 15:20 ` Stanislaw Gruszka
2017-12-16 18:33 ` Enrico Mioso
2017-12-18 15:21 ` Stanislaw Gruszka
2017-12-19 12:27 ` Stanislaw Gruszka
2017-12-19 12:39 ` Enrico Mioso
2017-12-19 12:43 ` Enrico Mioso
2017-12-19 12:54 ` Stanislaw Gruszka
2017-12-19 13:25 ` Enrico Mioso
2017-12-20 17:49 ` Enrico Mioso
2017-12-21 14:25 ` Stanislaw Gruszka
2017-12-24 12:19 ` Enrico Mioso
2018-01-03 11:35 ` Stanislaw Gruszka
2018-01-03 14:04 ` Enrico Mioso
[not found] ` <CAKR_QVLRwAA0NJSarX46J4A8XSp8h5SuTEtSBQ4ydpEPh_-aUw@mail.gmail.com>
2018-01-22 5:45 ` Enrico Mioso
2018-01-23 13:22 ` Stanislaw Gruszka
2018-01-24 5:14 ` Enrico Mioso
2018-01-24 8:18 ` Enrico Mioso
2018-01-24 10:03 ` Stanislaw Gruszka
2018-03-01 15:30 ` Daniel Golle
2018-03-02 19:13 ` Enrico Mioso
2018-03-07 12:27 ` Stanislaw Gruszka
2018-03-07 12:29 ` Stanislaw Gruszka
2018-03-23 7:51 ` Mathias Kresin
2018-03-26 10:35 ` Stanislaw Gruszka
2018-03-27 7:46 ` Mathias Kresin [this message]
2018-03-27 17:18 ` Stanislaw Gruszka
2018-03-27 17:43 ` Daniel Golle
2018-03-28 4:14 ` Enrico Mioso
[not found] ` <CAOt++SeSQ2j1KuVkbqt77LfznXN7JV0Lx5O8d7-m2VBrz8=85g@mail.gmail.com>
2018-03-29 5:13 ` Enrico Mioso
2018-03-30 14:41 ` Enrico Mioso
2018-03-30 14:44 ` Enrico Mioso
[not found] ` <MWHPR02MB3326233159B021143D7278F5D4A10@MWHPR02MB3326.namprd02.prod.outlook.com>
2018-03-30 17:33 ` Enrico Mioso
[not found] ` <CAOt++SeLh_NxcmM=YEMQSv4y9PabS_dT7k4yTxUiqXbac-=iUQ@mail.gmail.com>
2018-04-17 13:55 ` Enrico Mioso
2018-04-17 13:56 ` Jamie Stuart
2018-04-17 13:57 ` Enrico Mioso
2018-04-17 19:42 ` Stanislaw Gruszka
[not found] ` <CAOt++SeNt=4RUTvAR1y_WjC=a-YyYa3YBSmoAmv+7uK71U+3+A@mail.gmail.com>
2018-05-28 12:50 ` Stanislaw Gruszka
2018-05-28 13:54 ` Daniel Golle
2018-08-15 11:40 ` Stanislaw Gruszka
2018-08-15 22:35 ` Daniel Golle
2018-08-16 11:01 ` Stanislaw Gruszka
[not found] ` <DM5PR02MB365669D5E9F2DE20DAE4CB7AD43E0@DM5PR02MB3656.namprd02.prod.outlook.com>
2018-08-18 16:08 ` Daniel Golle
2018-08-20 12:20 ` Stanislaw Gruszka
2018-08-24 13:02 ` Stanislaw Gruszka
2018-03-28 18:13 ` Stanislaw Gruszka
2018-03-07 15:47 ` Jamie Stuart
2018-03-07 23:30 ` Enrico Mioso
2018-03-07 23:31 ` Enrico Mioso
2018-03-08 9:39 ` Stanislaw Gruszka
2018-03-08 14:28 ` Enrico Mioso
2018-01-23 13:20 ` Stanislaw Gruszka
2017-12-26 17:20 ` Enrico Mioso
2018-01-03 11:45 ` Stanislaw Gruszka
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=24f8f4a2-b355-a1b3-d07a-940fc1e50fcc@kresin.me \
--to=dev@kresin.me \
--cc=arnd@arndb.de \
--cc=daniel@makrotopia.org \
--cc=jamie@onebillion.org \
--cc=johannes.berg@intel.com \
--cc=john@phrozen.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mrkiko.rs@gmail.com \
--cc=nbd@nbd.name \
--cc=pozega.tomislav@gmail.com \
--cc=sgruszka@redhat.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 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.