From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [IPv6:2001:4b98:c:538::195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id BA1B23B29E for ; Wed, 22 Nov 2017 10:35:23 -0500 (EST) X-Originating-IP: 74.125.82.45 Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) (Authenticated sender: nctu@louie.lu) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id CEAB4A80DF for ; Wed, 22 Nov 2017 16:35:22 +0100 (CET) Received: by mail-wm0-f45.google.com with SMTP id v186so11026830wma.2 for ; Wed, 22 Nov 2017 07:35:22 -0800 (PST) X-Gm-Message-State: AJaThX5vBsyEgydgZNa6Fd4QlJAMyWJTUjszfWLqXlMs4azLXOvl6s22 1fwKC6RxxlSUN6AeupcO9zio+TIA9YpP2mwFzfc= X-Google-Smtp-Source: AGs4zMYDjt1NGrNCc8R8uTS2+b5L97kYY7iHKEPqq3WDmzUV5gYp58O0+1QZuWUtJ50wGggQGPoCCuhDqn7K5/eDiL8= X-Received: by 10.80.214.74 with SMTP id c10mr12143140edj.271.1511364922210; Wed, 22 Nov 2017 07:35:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.141.205 with HTTP; Wed, 22 Nov 2017 07:35:21 -0800 (PST) In-Reply-To: <87vai28k6j.fsf@toke.dk> References: <87vai28k6j.fsf@toke.dk> From: Louie Lu Date: Wed, 22 Nov 2017 23:35:21 +0800 X-Gmail-Original-Message-ID: Message-ID: To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= Cc: Make-wifi-fast@lists.bufferbloat.net Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Wed, 22 Nov 2017 10:36:11 -0500 Subject: Re: [Make-wifi-fast] How to figure out Linux wifi queue and ath10k queue scheduling? X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Nov 2017 15:35:23 -0000 2017-11-22 22:25 GMT+08:00 Toke H=C3=B8iland-J=C3=B8rgensen : > Hi Louie > >> I'm working on making VoWIFI performance more better on ath10k driver, >> my first thought is that I can modify queue scheduling algorithm >> inside ath10k. > > Sounds awesome! What kind of VoIP traffic are you working with, and what > aspect of performance are you looking to improve? :) We are working on 802.11ac with telecom operator's VoWIFI (through ePDG), but much more focus on the phone to AP jitter, latency and TXOP when AP has multiple stations (10+) traffic. >> After tracking the commit log, it seems currently ath10k is using >> mac80211 as an intermidieate queue[1][2], and as [2] indicate, ath10k >> is not able to do airtime fairness now. > > Yup, that's about right. We're working on the airtime fairness part, > though; see my recent presentation at Netdev a few weeks ago for an > updated status on previous and ongoing work [1]. Thanks for the update, I'll take a look at this. Also, is "airetime fairness" a concept as fair TXOP to each station? I'm not sure if I get this right. >> After reading the source code and [2], what I think about the queue in >> Linux to ath10k is: >> >> 1. Mac layer queue (mac80211) >> 2. ath10k 802.11e priority queues (4 queues, with different 802.11e ToS = level) >> 3. ath10k firmware (HW) queue >> >> Am I right on this? > > More or less (I don't know enough about how ath10k works internally to > tell you exactly how the internal queueing in the driver works). > Ideally, the lower-level queues (2 and 3) should be as empty as > possible, but no one ever got around to working on improving that. There > was an aborted attempt to apply the dynamic queue limit code[2] to > ath10k a while ago, but it was never completed. The WiP commit is here: > [3]. Thanks for the information, I'll take a look at it. >> Also, I saw the make-wifi-fast google docs[3], it has a plan for >> obsolete VO queue, is that still in the roadmap, or it is implemented, >> if not, where can I help for it? > > The work on the different QoS levels has mostly been on the idea stage > so far. My presentation[1] has some ideas related to this as well, but > nothing has been implemented thus far. What's on the roadmap depends > mostly on what people go ahead and implement ;) Got it, but are there any udpate about the make-wifi-fast google docs? Or this is the latest version of it. Beside patchwork, is there an issue tracker or just mailing list to get the latest information? Thanks, Louie. > -Toke > > [1] https://www.netdevconf.org/2.2/session.html?jorgensen-wifistack-talk > [2] https://lwn.net/Articles/454390/ > [3] https://github.com/kazikcz/linux/commit/1486ffbafdb4dd433203c35c694b7= 443fa769210