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 250E33B29E for ; Mon, 7 Oct 2019 15:40:49 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1570477248; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=J2Ph3icJn0W6wDmYyDFwH4B1x+sv1ciEVjfPrKs/LDI=; b=D1UOmt92UgPrzMqT+5+2K5c53X83y22HFjCdi6SMIhSg8LBG/vY+qorGVwyp89YjsjcctM /ooxDNbaXkjQKyr8orWwZ79dN9s+DNBh0eH1d6tYJS2LWb6K0Iy6JE1IPGxyztaCyz9XU2 T/f5nEa/pY1WzoqFzw9GmBK6OwRPCeg= Received: from mail-lj1-f198.google.com (mail-lj1-f198.google.com [209.85.208.198]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-186-DBZBN07_Pb2QfA3NUy1C-g-1; Mon, 07 Oct 2019 15:40:44 -0400 Received: by mail-lj1-f198.google.com with SMTP id e3so3824879ljj.16 for ; Mon, 07 Oct 2019 12:40:44 -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:cc:subject:in-reply-to:references:date :message-id:mime-version:content-transfer-encoding; bh=dGQcdmDOU5djooYj79l+KDc1Soqz551iHKq25ESjU+I=; b=XRDCRbU39ckpm7JKB6AU3+vuJZ01bPPw191Nimsc3pKPHedR/0ZhK+7IOxfEO05aLN WW714pMJakaBGONpY9VVWUZCzCIPS7eSOmgbPpX7z+RmBcA3x2iKbEZavkjUdbRTXofm x0tiZlIqgxuvNS3SkY25O7LHqtadA29X8pfsdt7dJ1icUQUlY58/GFChu5hNKBNbgH1C lQ9a/vOoZsPlrFhLX9UMITyUICsh+sorFCWFWML9LA81YN+srbwrwykXfXjZHMZJMoMA Jlj81xejP5f7AmBnVAXp8y0y76wdctAkFLnWuCczi8BkTM+whrhTO83myj5w1jzXpPLC bwzA== X-Gm-Message-State: APjAAAWrAvnnAz6jt2exobVVsQRV8duBVEcAf/E+Amoh7REyPk8xHGJn MdgjBMYjvd6ZSNFiEwCXTIiq+7K/KHwHWv4YbdF8ybIDU0OAwMS5yh0jmvyXrMCdNB5gfWRkQDI dSTyh4V29daPZVW6LK96pzlqCRPwP4r0NupM= X-Received: by 2002:a2e:730a:: with SMTP id o10mr20348406ljc.214.1570477242945; Mon, 07 Oct 2019 12:40:42 -0700 (PDT) X-Google-Smtp-Source: APXvYqyNCnUF881B+ASd51GbvvhhhTTw3DmRUBGe1LKyqDcA88YBX1NuI1aTa2BzRr4IFUyKru+GbA== X-Received: by 2002:a2e:730a:: with SMTP id o10mr20348397ljc.214.1570477242735; Mon, 07 Oct 2019 12:40:42 -0700 (PDT) Received: from alrua-x1.borgediget.toke.dk ([2a00:7660:6da:443::2]) by smtp.gmail.com with ESMTPSA id l7sm3299248lji.46.2019.10.07.12.40.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 07 Oct 2019 12:40:41 -0700 (PDT) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id B2B9418063D; Mon, 7 Oct 2019 21:40:40 +0200 (CEST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: Johannes Berg , Kan Yan Cc: linux-wireless@vger.kernel.org, make-wifi-fast@lists.bufferbloat.net, Felix Fietkau , Yibo Zhao In-Reply-To: References: <20191004062151.131405-1-kyan@google.com> <20191004062151.131405-2-kyan@google.com> <87imp4o6qp.fsf@toke.dk> <87pnj9n55y.fsf@toke.dk> X-Clacks-Overhead: GNU Terry Pratchett Date: Mon, 07 Oct 2019 21:40:40 +0200 Message-ID: <878spwmjif.fsf@toke.dk> MIME-Version: 1.0 X-MC-Unique: DBZBN07_Pb2QfA3NUy1C-g-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Make-wifi-fast] [PATCH 1/2] mac80211: Implement Airtime-based Queue Limit (AQL) 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: Mon, 07 Oct 2019 19:40:49 -0000 Johannes Berg writes: > On Sun, 2019-10-06 at 19:40 +0200, Toke H=C3=B8iland-J=C3=B8rgensen 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. >> >=20 >> > 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? >>=20 >> 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). >>=20 >> 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. Indeed :) >> 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... -Toke