Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp4696293ybp; Mon, 7 Oct 2019 12:24:20 -0700 (PDT) X-Google-Smtp-Source: APXvYqzUbhxKZVB5r4420nAyBlc6Ya2yyqM9efQSTC6wgjnYX17kxKhPa3JYgYJ6vpcgRWB6Y20i X-Received: by 2002:a50:e718:: with SMTP id a24mr30571226edn.289.1570476260179; Mon, 07 Oct 2019 12:24:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570476260; cv=none; d=google.com; s=arc-20160816; b=z13YZagofI142RCuGmmZ2M1dWffLd6rtSs2+rI09+IaLUTC0Ix59iDlyymhVb+0aYM ysdExOVdEkTp+jV21m0aflQAWq0uwPRuTtDkP0LVFq/uzzoYUWnvpecHl0xjO2o7Wv1z yhtYfKYpzWnEWae2I2LZpSGIqsvTnSlJ2hE1ipJuYCHdOwymePI8GP4yX5k3ZEhYIRCH QmLBx4WCvaOp3oVr5L/lBJ2ycty+qkeZw9HnRWc6oJ7DeeRFF7ZdWMBBIUj6gp/E+eGd DR1d8+3GrdzgADdfbgg1cKS41rtiVbFtM1rULSsWKRtlnbjJptZ+NI5iQSpW2sB59JCX iwcg== 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=9uDpeh3zOMjWrluXZ+AJtpqJ5J9ardUo10ARxRhL8OI=; b=S8xBdvNY5L2GvgVrQlYkRNncRnHo8fOQp+38njxggsG8sIDWtNRyzx40FaEIR/Xo8R VJjIAkz68gnZceJmCAgXgKvJRlEIXLfkGibuJoD44ArDv0DJq4GSiQVdaf7YlhzQd/A0 CxJ1VEs3EEsyc5ff5TETCtglGiSrKIpY7NT+Un/3qqPS7nJWI3SUTtjSlku/ij1nOkYl yC5qIVZMW1C373RMWLn2whcxU5YQhqw6g8nKlx2paplJE1icyFMS8983xfxSsUY7dOav d9f/9SAyomCrJJTiAFCDq7QhA0/o9LiFtBkPsSlnf+WRHLCRWO6pbSvrf7QWGlvNTa+e dMuA== 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 h43si8711567ede.142.2019.10.07.12.23.56; Mon, 07 Oct 2019 12:24:20 -0700 (PDT) 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 S1728212AbfJGTXz (ORCPT + 99 others); Mon, 7 Oct 2019 15:23:55 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:45018 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728079AbfJGTXy (ORCPT ); Mon, 7 Oct 2019 15:23:54 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.92.2) (envelope-from ) id 1iHYbm-0007aT-Vs; Mon, 07 Oct 2019 21:23:51 +0200 Message-ID: Subject: Re: [PATCH 1/2] mac80211: Implement Airtime-based Queue Limit (AQL) From: Johannes Berg To: Toke =?ISO-8859-1?Q?H=F8iland-J=F8rgensen?= , Kan Yan Cc: linux-wireless@vger.kernel.org, make-wifi-fast@lists.bufferbloat.net, Felix Fietkau , Yibo Zhao Date: Mon, 07 Oct 2019 21:23:49 +0200 In-Reply-To: <87pnj9n55y.fsf@toke.dk> References: <20191004062151.131405-1-kyan@google.com> <20191004062151.131405-2-kyan@google.com> <87imp4o6qp.fsf@toke.dk> <87pnj9n55y.fsf@toke.dk> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Sun, 2019-10-06 at 19:40 +0200, Toke Høiland-Jørgensen wrote: > > That's a good point. I haven't thought about real simultaneous dual > > band chipset and such chipset do exists now. Is RSDB support coming to > > mac80211 soon? Just curious if it will be just virtual interfaces or > > something else. I chose "local" instead of "sdata" thinking about the > > case of several virtual interfaces (AP, STA, MESH) operates in the > > same channel, then the interface total could be a better choice. > > > > I am ok with moving the "aql_total_pending_airtime" into sdata, but > > afraid that's not the most optimal choice for the case of multiple > > virtual interfaces operates in the same channel. > > Maybe we could leave it in "local" for now. What do you think? > > I'd lean towards keeping it in 'local' for consistency with all the > other airtime stuff. For now, I think having multiple SSIDs on the same > radio is more common than the reverse (multiple bands on a single > radio). > > In particular, the per-group airtime fairness stuff is definitely > designed on the assumption that all BSSes share the same band. s/band/channel/, presumably. > So if and when we start supporting true multi-band devices we'll have to > change these things anyway. So might as well keep everything together so > it all gets fixed :) I guess I'm OK with that, but I'm pretty sure this will come up sooner rather than later ... What else is there though? johannes