Received: by 2002:a17:90a:88:0:0:0:0 with SMTP id a8csp194095pja; Fri, 22 Nov 2019 05:18:12 -0800 (PST) X-Google-Smtp-Source: APXvYqxM/VU3xtl4c35h1vFbgGUV+9nUXzRBqadv9AMv+gCqnXqDMP87kJWn7thdmObnU9cG/9KB X-Received: by 2002:a17:906:2e52:: with SMTP id r18mr22470537eji.178.1574428692839; Fri, 22 Nov 2019 05:18:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574428692; cv=none; d=google.com; s=arc-20160816; b=mxjH1zgtHaKQTHcym2TN5uX63/ymD588M9F+4/Kv1SsoIUzRoZzHCMLQrBWDaqcXSq oIiAVWR/Hyc26zTXkFllCQp/4XJE021dB0T2rr8wvRTvzs4gqaxb/gmpnHAaGDTfH0nJ JpKUDHk8cM0aVVAoNts/PAZUOBJxatzYhTIdbdbYRqzPnzkpnDAY6Snt3FFTLxuNuy7N ZEmCIoCiZ/rCye8lqTP2duyKMnHtlD833TrmxNEjGiAhuaIJTdAcJEKyIKJyOY6qVkGo VmiByo2QrNtpJARku2aXH/snT7xEusnolpOuenP67J7L9HLXM8bgDZWI3EmCsiSxycz0 LByg== 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=pS/CzG8pzuu9qlo+j9i7j7vWCT0UeGffWhgMSkqc9wI=; b=Iqg1ydrj+b/ViXqP5g5JwxSBi5ijiDedpKEKy3NPBN7i+lfDt/EBOEgIxnlWThv7bn 8ZyzKSgzcn69lHvU3T7Ndbj5sVryU5fyBjWBnMVbZ/ZkVL9la3CamBIADUf3WJWFvtBl g8uPPm5cqB5KOGOnxrMO2FHvg22TrOQ2wdr9pevcBH4r686/PC9SoBlIe6GnOaCIgo6p ficj4+D6Xbzeaw9JONxmjdCz7QxqIUbA7ZKcptrHjDlHf/7/sbB8phN4OhY1RyZv86BM rTs5k72AU5/H+qK+LHLhQoLfarPVQ3t7t2WAaWyXToI3Bt9QPJVCYFRZ5bQNCEyQljbF 9SDQ== 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 z16si4121834eji.25.2019.11.22.05.17.46; Fri, 22 Nov 2019 05:18:12 -0800 (PST) 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 S1726846AbfKVNPN (ORCPT + 99 others); Fri, 22 Nov 2019 08:15:13 -0500 Received: from s3.sipsolutions.net ([144.76.43.62]:45332 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726548AbfKVNPN (ORCPT ); Fri, 22 Nov 2019 08:15:13 -0500 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 1iY8mF-000496-P6; Fri, 22 Nov 2019 14:15:11 +0100 Message-ID: <994e486e8e82c01e70150eacf59dedf61b80fc65.camel@sipsolutions.net> Subject: Re: [PATCH v11 2/4] mac80211: Import airtime calculation code from mt76 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, nbd@nbd.name, yiboz@codeaurora.org, john@phrozen.org, lorenzo@kernel.org, rmanohar@codeaurora.org, kevinhayes@google.com Date: Fri, 22 Nov 2019 14:15:09 +0100 In-Reply-To: <87imnc3vk9.fsf@toke.dk> References: <20191119060610.76681-1-kyan@google.com> <20191119060610.76681-3-kyan@google.com> <3e7bea0cc643714ec90978a7999022544a39b118.camel@sipsolutions.net> <87tv6w3w92.fsf@toke.dk> <87imnc3vk9.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 Fri, 2019-11-22 at 14:11 +0100, Toke Høiland-Jørgensen wrote: > > as in bitrate = 1/airtime? Dunno, maybe? How important is precision to > the bitrate calculations? Not *that* important, it's just sort of advisory for userspace. Though I think there's at least one place in mac80211 related to radiotap that actually does use it for airtime calculation, which should probably be changed to the new code now ... > > Or maybe we should keep both and use them as a sanity check for each > > other :P > > Hmm, yeah, it should be possible to write a selftest to iterate through > all rates and compare the output of each calculation, shouldn't it? > Where would be a good place to put that? No idea ... make a new kselftest thing for wireless? johannes