From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B7E86C67863 for ; Sat, 20 Oct 2018 18:56:27 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6DB232157C for ; Sat, 20 Oct 2018 18:56:27 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6DB232157C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=candelatech.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727453AbeJUDH1 (ORCPT ); Sat, 20 Oct 2018 23:07:27 -0400 Received: from mail2.candelatech.com ([208.74.158.173]:60750 "EHLO mail2.candelatech.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727350AbeJUDH1 (ORCPT ); Sat, 20 Oct 2018 23:07:27 -0400 Received: from [172.31.98.117] (96-89-137-83-static.hfc.comcastbusiness.net [96.89.137.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail2.candelatech.com (Postfix) with ESMTPSA id AFF9D40A5A2 for ; Sat, 20 Oct 2018 11:56:02 -0700 (PDT) Message-ID: <5BCB7A83.3050907@candelatech.com> Date: Sat, 20 Oct 2018 11:57:07 -0700 From: Ben Greear Organization: Candela Technologies User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: "linux-wireless@vger.kernel.org" Subject: Re: Rate-ctrl experience gained with ath10k References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org I now have the 9984 ath10k working pretty good I think, at least as far as rate-ctrl is going. It tries to keep retransmit < 10% and throughput is fine compared to using MCS with higher retransmit (and higher encoding rates). But, I tried to put similar changes (dodge high retransmit MCS if possible), and for the wave-1 9880 chip, this decreased throughput. For instance, current rate-ctrl was retransmitting about 30% of the frames when allowed to choose its MCS. In this case, I saw around 225-230Mbps throughput. But, if I forced it down to MCS-5, 3x3, then throughput was about 220Mbps, and retry percent was closer to 2%. So, question is...should I still tweak its ratectrl to choose lower MCS when retransmit % is high, or should I just let it retransmit. Maybe lower MCS and lower retransmit would be better over-all if there are lots of devices on the network? I'll run some tests to experiment with that when I have time, but curious if others have already done similar... Thanks, Ben On 10/16/2018 04:31 PM, Ben Greear wrote: > So, I've been trying to understand why the ath10k-rate ctrl was acting > so poorly in my 20-station UDP tx case. I wrote that wifi-diag tool, > and it gave some clues, but only in retrospect were they obvious :) > > The problem in general was that a single station could upload, at say 500Mbps, > but 20 stations could only do about 325Mbps. If we fixed the MCS at 3x3 MCS7, > then the 20 station upload test ran about 490Mbps. > > There were several optimizations I made in the ath10k firmware rate-ctrl. One > was to penalize rates with higher PER (packet error rate) more than the old algorithm did. This helped > a small bit, but not enough (around 350-370Mbps total throughput). > > Then, after adding logs I noticed that each station was probing once about every 5 ampdu > chains, or almost 20% of the time! These probe AMPDUs are limited to a max of 4 AMSDUs, > and that explains why my 'bad' case showed 17% of the AMPDU chains were 4 in length in > my wifi-diag output. > > I changed the firmware to take number of active stations into account, and increase the > 75ms probe interval by up to a factor of 5. I also probe less often when the probed > rate has PER > 5 or the last probe had a dropped frame. > > And, I allow probing with AMPDU chains of up to 16 AMSDU instead of just 4. > > Together this gets me up to about 460Mbps in this test case. Still not quite as good > as fixing the MCS at 7, but good enough I think. > > Here's hoping this email will let other folks poking at rate-ctrl have a faster > time at fixing things than I did. > > Thanks, > Ben > -- Ben Greear Candela Technologies Inc http://www.candelatech.com