From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 4BA943B29E for ; Wed, 4 Dec 2019 03:08:05 -0500 (EST) Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.92.3) (envelope-from ) id 1icPhY-00HZvi-VX; Wed, 04 Dec 2019 09:08:01 +0100 Message-ID: From: Johannes Berg To: Kalle Valo , Kan Yan Cc: Dave Taht , Toke =?ISO-8859-1?Q?H=F8iland-J=F8rgensen?= , Rajkumar Manoharan , Kevin Hayes , Make-Wifi-fast , linux-wireless , Yibo Zhao , John Crispin , Lorenzo Bianconi , Felix Fietkau Date: Wed, 04 Dec 2019 09:07:59 +0100 In-Reply-To: <0101016ecf3bc899-6e391bba-96ed-4495-a7be-1aa8dd8f1bf2-000000@us-west-2.amazonses.com> References: <20191115014846.126007-1-kyan@google.com> <8736eiam8f.fsf@toke.dk> <87a78p8rz7.fsf@toke.dk> <87muco5gv5.fsf@toke.dk> <87eexvyoy8.fsf@toke.dk> <878so2m5gp.fsf@nemesis.taht.net> <0101016ecf3bc899-6e391bba-96ed-4495-a7be-1aa8dd8f1bf2-000000@us-west-2.amazonses.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.34.2 (3.34.2-1.fc31) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Make-wifi-fast] [PATCH v8 0/2] 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: Wed, 04 Dec 2019 08:08:05 -0000 On Wed, 2019-12-04 at 04:47 +0000, Kalle Valo wrote: > > > Overall, I think AQL and fq_codel works well, at least with ath10k. > > The current target value of 20 ms is a reasonable default. It is > > relatively conservative that helps stations with weak signal to > > maintain stable throughput. Although, a debugfs entry that allows > > runtime adjustment of target value could be useful. > > Why not make it configurable via nl80211? We should use debugfs only for > testing and debugging, not in production builds, and to me the use case > for this value sounds like more than just testing. On the other hand, what application/tool or even user would be able to set this correctly? johannes