Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp4714383ybp; Mon, 7 Oct 2019 12:44:24 -0700 (PDT) X-Google-Smtp-Source: APXvYqyNNE9TNZzO5Gz9bcUe6TegAVAi0j2Hbh1z9oIprOo08zle0gVyU43I/c90i7Mhe0n4BEy9 X-Received: by 2002:a05:6402:1202:: with SMTP id c2mr29436304edw.190.1570477464792; Mon, 07 Oct 2019 12:44:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570477464; cv=none; d=google.com; s=arc-20160816; b=bGPpNpvKUx1WJH56TD+hg/5L3/9wcBmtfESeM6Z1lRmpjMTxS/L6naUgvINw2IzQpl IYusuVzmAPX9TcNyeCozuedOb3/NSy1JnnTC75bvX8AX1CE9FJQc2v5SjwaUa6GzpCR0 YS4pcIaaaqVyo7YtJAXmUvc3s8WUhL/h2qVXw6SBsdYSG4KROj+98rQj7tLfIJiNdxED YDlBmglb0IVsPmk15gaeaFYn4hlrLQ3Mc6XFCPA5JOTwsGeBlH7jvMduyGn7qlsB6Jfx ARytUIGU6zfocjtSJ7EF+WIDvJ6qsa67LvPcGrcbLhcO1AdoL7ptmku7JIOlMwF3+0Ov scgw== 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=pRbap+zKfxybXeNJGjKpE6f+PtK4ZSP2C2NJWl0hFF8=; b=QdgUO8UJu1DJ5CviXmxMh0yLPh77qYm+60KFSiIsuUPii/yM0gdgJAFhudo7Jx1xJ5 vVTnhgr30TMCWxS5igcoSJXr+aQti1pXSexhnmYOEetNdGQrS4YkA3zmexlBkw0/IQhn Q4h16j+sRVwJ16HffgEoVxSX3gZu/p4R3Y/jlW+eNIPOpTGXsumvJkIBIu0IaCbn1sf+ AjmsYxe6uOXCyvMX6wnum7kMxmCktPFQNWeVt0lxCstVdfKtzPKiWkhK3cVvwc/zWREP LfP72ha6Kqkr2jVFa67k1GB5QPlXmuogT5zHnNLhIRyOZgfPIAkUbmk4pNadzfA87o6G UvTw== 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 x3si9404312eda.285.2019.10.07.12.43.59; Mon, 07 Oct 2019 12:44:24 -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 S1728325AbfJGTnu (ORCPT + 99 others); Mon, 7 Oct 2019 15:43:50 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:45336 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728212AbfJGTnu (ORCPT ); Mon, 7 Oct 2019 15:43:50 -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 1iHYv4-00088e-7l; Mon, 07 Oct 2019 21:43:46 +0200 Message-ID: <600f64e1e673fff25d2be71ac767d7332db0452a.camel@sipsolutions.net> 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:43:45 +0200 In-Reply-To: <878spwmjif.fsf@toke.dk> References: <20191004062151.131405-1-kyan@google.com> <20191004062151.131405-2-kyan@google.com> <87imp4o6qp.fsf@toke.dk> <87pnj9n55y.fsf@toke.dk> <878spwmjif.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 Mon, 2019-10-07 at 21:40 +0200, Toke Høiland-Jørgensen wrote: > > > 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? > > By "it all" I meant "all the airtime fairness stuff". Other than that, I > didn't have anything in particular in mind. I just kinda assumed there > would be lots of places that had an implicit assumption that all devices > on the same phy shares a channel... Not _that_ much - we do have the channel contexts after all. But except for hwsim (*cough cough* I was lazy) nothing actually implements real concurrent multi-channel yet, obviously, but uses a single radio with channel hopping... johannes