From: Stanislaw Gruszka <stf_xl@wp.pl>
To: "Daniel Similä" <dsimila82@hotmail.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: mt76x0u. Unusable performance while compiling stuff.
Date: Fri, 3 Jan 2020 13:18:50 +0100 [thread overview]
Message-ID: <20200103121849.GA2832@wp.pl> (raw)
In-Reply-To: <270ccb561149f7af3596470b3f9bb2ec@wp.pl>
(cc linux-wireless & Lorenzo)
On Fri, Jan 03, 2020 at 12:19:20AM +0000, Daniel Similä wrote:
> Bus 001 Device 005: ID 148f:761a Ralink Technology, Corp. MT7610U ("Archer T2U" 2.4G+5G WLAN Adapter
>
> Driver is mt76x0u
> Wifi is 5GHz ~260Mb
>
> while doing:
> nice make -j16
>
> Pinging my router goes from:
> ping _gateway
> PING _gateway (192.168.0.1) 56(84) bytes of data.
> 64 bytes from _gateway (192.168.0.1): icmp_seq=1 ttl=64 time=1.20 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=2 ttl=64 time=1.02 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=3 ttl=64 time=2.12 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=4 ttl=64 time=1.32 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=5 ttl=64 time=2.04 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=6 ttl=64 time=1.31 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=7 ttl=64 time=1.71 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=8 ttl=64 time=0.903 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=9 ttl=64 time=1.00 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=10 ttl=64 time=1.42 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=11 ttl=64 time=1.15 ms
>
> to unusable:
>
> ping _gateway
> PING _gateway (192.168.0.1) 56(84) bytes of data.
> 64 bytes from _gateway (192.168.0.1): icmp_seq=1 ttl=64 time=167 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=3 ttl=64 time=306 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=4 ttl=64 time=255 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=6 ttl=64 time=253 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=8 ttl=64 time=84.7 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=9 ttl=64 time=522 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=10 ttl=64 time=211 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=11 ttl=64 time=304 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=15 ttl=64 time=2825 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=16 ttl=64 time=1812 ms
> 64 bytes from _gateway (192.168.0.1): icmp_seq=17 ttl=64 time=799 ms
>
> Running kernel 5.4.6-arch3-1
> CPU is Amd 2700X and ram is 16GB
I think this should be fixed by 5.5 commit:
commit 284efb473ef5f02a7f2c13fdf8d516ecc589bdf1
Author: Lorenzo Bianconi <lorenzo@kernel.org>
Date: Mon Oct 28 17:38:05 2019 +0100
mt76: mt76u: rely on a dedicated stats workqueue
and if it indeed fixes the problem, this commit should be requested
to stable.
Stanislaw
next parent reply other threads:[~2020-01-03 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <270ccb561149f7af3596470b3f9bb2ec@wp.pl>
2020-01-03 12:18 ` Stanislaw Gruszka [this message]
[not found] ` <b335da869c0ae7d859a27ec4a26d8c35@wp.pl>
2020-01-03 16:19 ` mt76x0u. Unusable performance while compiling stuff 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=20200103121849.GA2832@wp.pl \
--to=stf_xl@wp.pl \
--cc=dsimila82@hotmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi83@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 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.