Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp2297959ybl; Sat, 7 Dec 2019 12:09:55 -0800 (PST) X-Google-Smtp-Source: APXvYqxG68++2BrDLbdEb4JazZSScdrbmB/YatbfGIAZiiH8fxCJfLIvvIgbSSb2FMSOyyYhSCfO X-Received: by 2002:a9d:5543:: with SMTP id h3mr16375579oti.33.1575749395133; Sat, 07 Dec 2019 12:09:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575749395; cv=none; d=google.com; s=arc-20160816; b=V3Vjp5byoHelBrXVtlHhlvBcjbOSvlkGOci65EE4bGjg7Lt4V+RSunzFpujeoSpK7h FzkKrDvCjdgayvOYVW9yxLq1IMlAoLQxyJBI39kIBEzrDKxHkIPqRmKGwYtU9/skb1ig cVHnZtLIihG/Ath+Q+D9PAjUzJFgmEPR9/Ro/OSSWvs7SguGkfjmfPPSNaTQTquBukQG fIuvfY+xYFKv3aFp43/WH0D8QWLN0yoUaN4C1taJwTMMrR/oo18RCoZsFLMteoEEuk4l kf4h+Ji2TCny+a4kKIqbis+hBsMDqoehwk8UrpBmGsoN5KlbaSkCTDvO65sATN7Wk9YL a3OA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=rCXM8xavEtyqFmfUE4O+MgQ84XYEYIe92WQhx0v1r0I=; b=uMxtjVxTo0yAogmVr85Bdr3FvAFjlI6PryqSvYYwgwQ6I5UorhY1R/F3z0deSFtS2M wFydZQB/cNLHVGCuf+EGxjHyqJFKPX4yjLNlPAM+W4yplLgOJfhli4BKWGg5ujmZ7pbf P7odjidu53qepfokkT2EamXXA4MT1LTcEFn3Smb0GMTWVHlXK0zfImbLH2pidyKYXGWU N5bmOwQVUuA1VQHF6Md0fXGAnT7GcNvqi+117ligQmEPGTK5XaHF0AISEbf4q25NQOo9 KNc6dMz33YySb6X3Klb5PjITeGmhjg2h2nwn1zvI9tCWfCyAQnf9ex7FsaugkZG7fyuB saAQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g16si9247505otj.129.2019.12.07.12.09.32; Sat, 07 Dec 2019 12:09:55 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726626AbfLGUJ0 (ORCPT + 99 others); Sat, 7 Dec 2019 15:09:26 -0500 Received: from s3.sipsolutions.net ([144.76.43.62]:60786 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726555AbfLGUJ0 (ORCPT ); Sat, 7 Dec 2019 15:09:26 -0500 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.92.3) (envelope-from ) id 1idgOF-00Aana-4D; Sat, 07 Dec 2019 21:09:19 +0100 Message-ID: Subject: Re: debugging TXQs being empty From: Johannes Berg To: Ben Greear , Kan Yan Cc: Toke =?ISO-8859-1?Q?H=F8iland-J=F8rgensen?= , linux-wireless Date: Sat, 07 Dec 2019 21:09:17 +0100 In-Reply-To: <336996e4-d9fe-bf3a-72fb-6919bd0adcbf@candelatech.com> References: <9b89b3b294295063aec045b9e863a44ad20b8782.camel@sipsolutions.net> <9bcbab4b562669b96198c632f476b1b74956ca09.camel@sipsolutions.net> <336996e4-d9fe-bf3a-72fb-6919bd0adcbf@candelatech.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.34.2 (3.34.2-1.fc31) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Fri, 2019-12-06 at 15:44 -0800, Ben Greear wrote: > I did some tests today: > > kernel is 5.2.21+, with the fix for ax200 upload corruption bug. > AP is QCA 9984 based PC (i5 processor) running ath10k-ct firmware/driver, configured for 2x2 160Mhz > STA is PC (i5 processor) with AX200 > OTA, about 5 feet apart > AP reports STA is sending at MCS-9 160Mhz (AX200 STA does not report tx rate it seems) Yeah, that was an oversight for HE, it should work for HT/VHT. I have a patch in the works to report the TX rate properly in iw. > Our LANforge tool is traffic generator, running directly on AP and STA machine. > > Download UDP, I see about 697Mbps goodput > Upload UDP, I see about 120Mbps goodput > > TCP download, about 660Mbps > TCP upload, about 99Mbps > > Our hacked version of pktgen, bps includes down to Ethernet frame: > Download: 740Mbps > Upload: 129Mbps Uh, wow, that's not good. I guess after I'm done with this bug, I should look at upstream ... > I changed AP to 80Mhz mode, and re-ran the UDP tests: > > Upload 137Mbps > Download 689Mbps > > Though not confirmed today, one of us reports about 1.7Gbps download on AX200 against an enterprise /AX AP, > and only abuot 600Mbps upload in that same system. That is in isolation chamber and such. > > So, for whatever reason(s), we see consistent poor upload performance on AX200. > > For reference, we have previously seen about 1.1Gbps upload between QCA9984 station and 4x4 /AC APs > (and about 1.3Gbps download goodput), so in general, wifi upload can run faster. Yes, for sure it can. Would be interesting to find out what the limiting factor is for you. Then again, I doubt we've released updated firmware recently - what version are you using? johannes