From mboxrd@z Thu Jan 1 00:00:00 1970 From: bruce m beach Date: Wed, 31 Aug 2016 21:01:58 -0700 Subject: [ath9k-devel] ath9k_htc kernel driver regression affecting throughput In-Reply-To: References: <1472153242.25699.0@smtp.gmail.com> <1472596968.4898.0@smtp.gmail.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org Oleksij I managed to boot 4.7.2 and got on an AP. The signal strange was around -67 db which about par for this connection. Download speed was about 290kb/s a little bit slow but it is raining, so It seems that 4828I'm getting a mostly normal connection. The only anonaly is 1 retry : not so bad 4828 of misc which is very unusual These numbers are coming from /proc/net/wireless Bruce On 8/31/16, Oleksij Rempel wrote: > Am 31.08.2016 um 05:52 schrieb bruce m beach: >>> I'm starting to get concerned that it will never get fixed, especially >>> since >>> I can't seem to convince anybody that it's real or that it's a problem. >>> I've >>> got wireshark installed and I can watch the signal gum up quickly with >>> malformed packages, dup awks, spurious retransmissions, and terminations, >>> but >>> I don't know how to translate that into identifying the problem in the >>> driver/module. >> >> I tried to boot linux-4.7.2 to try to see if I have the same problem but >> the >> video is broken on samsung exynos (again) so I can't do anything until >> the video is fixed, unless there is someway to backport 4.7.x or 4.4.x >> to 4.2.2 ( anybody? ) Meanwile have you tried getting a really good >> wireless >> link within the immediate vicinity of your wireless device? Have you >> tried >> a different link with a completely different ap. >> >>> I am surprised this basic functionality in managed mode has persisted >>> for so >>> long without other people noticing it or addressing it >> >> This is the thing: If it is true then why are there no other reports of >> this behaviour. None the less I wouldn't give up, these impossible things >> usually get resolved and become history as long as you stick to it. >> >> >> Bruce >> _______________________________________________ >> ath9k-devel mailing list >> ath9k-devel at lists.ath9k.org >> https://lists.ath9k.org/mailman/listinfo/ath9k-devel >> > > here are test results which i get with recent kernel: > > uname -a > Linux ultralex 4.8.0-rc3-00201-gaf56ff2 #200 SMP Sun Aug 28 14:14:36 > CEST 2016 x86_64 x86_64 x86_64 GNU/Linux > > > ./tests zwerg.local > tcp from client to server > MIGRATED TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to > zwerg.local () port 0 AF_INET : demo > Recv Send Send > Socket Socket Message Elapsed > Size Size Size Time Throughput > bytes bytes bytes secs. 10^6bits/sec > > 87380 16384 16384 10.04 24.80 > tcp from server to client > MIGRATED TCP MAERTS TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to > zwerg.local () port 0 AF_INET : demo > Recv Send Send > Socket Socket Message Elapsed > Size Size Size Time Throughput > bytes bytes bytes secs. 10^6bits/sec > > 87380 16384 16384 10.00 48.61 > udp from client to server > MIGRATED UDP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to > zwerg.local () port 0 AF_INET : demo > Socket Message Elapsed Messages > Size Size Time Okay Errors Throughput > bytes bytes secs # # 10^6bits/sec > > 212992 65507 10.02 1062 0 55.57 > 212992 10.02 1062 55.57 > > two tcp tasts at same time. both directions > MIGRATED TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to > zwerg.local () port 0 AF_INET : demo > MIGRATED TCP MAERTS TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to > zwerg.local () port 0 AF_INET : demo > Interim result: 49.69 10^6bits/s over 5.001 seconds ending at > 1472655100.562 > Interim result: 50.81 10^6bits/s over 5.001 seconds ending at > 1472655105.562 > Interim result: 1.25 10^6bits/s over 19.644 seconds ending at > 1472655115.205 > Interim result: 25.92 10^6bits/s over 9.793 seconds ending at > 1472655115.355 > Interim result: 1.71 10^6bits/s over 5.059 seconds ending at > 1472655120.264 > Interim result: 50.22 10^6bits/s over 5.015 seconds ending at > 1472655120.370 > Interim result: 1.67 10^6bits/s over 5.036 seconds ending at > 1472655125.300 > Interim result: 49.50 10^6bits/s over 5.072 seconds ending at > 1472655125.442 > Interim result: 1.69 10^6bits/s over 5.036 seconds ending at > 1472655130.336 > Interim result: 50.05 10^6bits/s over 5.001 seconds ending at > 1472655130.444 > > > Since it is not my reference setup i can't absolute maximum, but what i > get in this busy network with 20HT is not bad - 50Mbit/s! > > I would suggest to start with git bisect to track down actual source of > regression. > > > -- > Regards, > Oleksij > >