From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id B38AC3B29D for ; Tue, 23 Jun 2020 05:35:35 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1592904935; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=8t8l0WD94Z/o9FZCmgK8w3SYLMkPUSfPtqimevExj1Y=; b=Q1sihA3T7V19yelB4uGEd4tJkPaVAj17gEjuMaJoMtkWrh2Mz8AVX7vRbOxWLAEoA8NLEt ipS+NNvG4PBAir5cWSka3mboa6woHUv34qJF2wS7yJDFLLcoJMgd5MQM8atekcZ+mX3NID aIUnylrEoHOAafXt4jpJB/t7s1bENGs= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-288-vOIJplEFM7WutULhD0FjqA-1; Tue, 23 Jun 2020 05:35:33 -0400 X-MC-Unique: vOIJplEFM7WutULhD0FjqA-1 Received: by mail-wm1-f70.google.com with SMTP id t18so3347285wmj.5 for ; Tue, 23 Jun 2020 02:35:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:in-reply-to:references:date :message-id:mime-version; bh=8t8l0WD94Z/o9FZCmgK8w3SYLMkPUSfPtqimevExj1Y=; b=B4YjklGxFCzSa5/hHA7wxZ2l/XqTrFKXJvx6NYANYY9AUC8ESHk7i/eVk7AwIzOwQe OjERVBKPuwUsz/yqCQjbe1d+lPA4payKbC1QHHzJwzlJa7bkPt1PhWgi+92fLSiWrBkU PjgBMz/pe0gR8pKU6qj3sJeMDKng4dOc6zR9isILrXugNOpWiHvdF38N+8zKW5e73eaS xkBogU0gDgG0jZSffoppZOT1lIlyQnki7DVL3NnDwwFekCuDk6/Au9lPEYKrZE7PXkKK 79kQfVe1vhxvklscpjek9WPt0O1liXFbiRxvox5fD7wFJdxmlUpCWFGSLNSK/hdAtlcq Cjmw== X-Gm-Message-State: AOAM531WGWbn/rRB8GFrAN/hFxX/irJnZ5F0+w8XEtflt0FRvB1/UjDS gSo/QyBG6De5rbXdIhQ7bdMmQ7dDP59u+lXvowhnyd/cTLbmPZ2Hm9ue/35CCp0pTjGn6vcI6P9 7y2U77wecokoXP7gJ3VAuK9CBGjIZ4oDc/zc= X-Received: by 2002:a5d:498f:: with SMTP id r15mr25651970wrq.175.1592904932339; Tue, 23 Jun 2020 02:35:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzsicQl2Vu9aNjKz9oQUfQD432xl1fEWFRTaOXg+AmYhW46FIJpGg3JdpVCpS/DyoLNufYJ6w== X-Received: by 2002:a5d:498f:: with SMTP id r15mr25651947wrq.175.1592904932056; Tue, 23 Jun 2020 02:35:32 -0700 (PDT) Received: from alrua-x1.borgediget.toke.dk ([45.145.92.2]) by smtp.gmail.com with ESMTPSA id v24sm24963115wrd.92.2020.06.23.02.35.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 23 Jun 2020 02:35:31 -0700 (PDT) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id F22B3181502; Tue, 23 Jun 2020 11:35:29 +0200 (CEST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: Miguel Catalan Cid , make-wifi-fast@lists.bufferbloat.net, linux-wireless@vger.kernel.org In-Reply-To: References: X-Clacks-Overhead: GNU Terry Pratchett Date: Tue, 23 Jun 2020 11:35:29 +0200 Message-ID: <87zh8uruou.fsf@toke.dk> MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Subject: Re: [Make-wifi-fast] Support for airtime scheduling using ath10k 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: Tue, 23 Jun 2020 09:35:35 -0000 Miguel Catalan Cid writes: > Hi, > > we are trying to apply different airtime weights to different stations in > order to have some prioritization among connected stations. While this is > working pretty well with ath9k, with ath10k we always obtain a fair > distribution of the airtime (i.e. 50%-50% in the case of two stations), > regardless of the airtime weight specified. > > E.g. STA1: > RX: 0 us > TX: 2295610622 us > > *Weight: 200*Deficit: VO: 256 us VI: 256 us BE: 34 us BK: 256 us > > E.g. STA2: > RX: 0 us > TX: 162597077 us 2295610622/162597077 ~= 14 which is not *too* far from the 20/1 ratio you've configured? Does the ratio change at all when you change the weights (i.e., if they are equal, do you get closer to a 50/50 split?). Do the two stations have roughly the same signal strength / rate? > *Weight: 10*Deficit: VO: 256 us VI: 256 us BE: 9 us BK: 256 us > > We are using Compex WLE650V5-18A cards. > > So, does ath10k support airtime scheduling? In such a case, do we need > specific Wi-Fi cards? It should. My guess would be that maybe you're not getting enough backpressure for the scheduler to actually enforce things correctly. You could try to look at the TXQ output and see if you actually have any drops ('iw dev wlan0 station dump -v' and look at the drops/marks columns). What kernel version are you running? If it's not new enough to have AQL, that might help moving the backlog to where the scheduler can do more with it. -Toke