From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [IPv6:2a00:7660:6da:2001::664]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 455DA3B2A4 for ; Mon, 21 Jan 2019 11:48:41 -0500 (EST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1548089319; bh=r14cw7ZTUoQ1g4hz99LMnr1pSAW48GyAl0gMHC4xJrQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=ICLfXLeilaNBk4jMoPimgwPV2d0LNe/wKyvlbTiTCmE9mmwC8va8gZhS6NcE0GArt hiPLwCvPxbxJe2iqa088ssDMjy6jwET/GqxuyrUBmZ1TCGPPOGYdRIK0bwlY9XLLzH bsb9scYcbxFY/oSYEbyKcAXk+wy5uZOcFzW9P3nPKPZMfshTfOVN/vAlR+3bhL00/P 2IRHkAY7NAGByWv0cpgumF/e4WNtnzbX3wiPIk0pyictUszSJbyenj6buKO+2Aal6r Gb/uT/TJTjgopGJdVjIBNO/Z2nDFkik8IIPTrJYmQGOD9x7mvPMq5Ihpfso7is2VHH /O9Cg6+Az5Wrw== To: Rajkumar Manoharan , linux-wireless@vger.kernel.org, ath10k@lists.infradead.org Cc: make-wifi-fast@lists.bufferbloat.net, Kan Yan , Rajkumar Manoharan In-Reply-To: <8736pmmjbk.fsf@toke.dk> References: <1545172374-1072-1-git-send-email-rmanohar@codeaurora.org> <1545172374-1072-7-git-send-email-rmanohar@codeaurora.org> <8736pmmjbk.fsf@toke.dk> Date: Mon, 21 Jan 2019 17:48:39 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87sgxmklco.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Make-wifi-fast] [PATCH v4 6/6] ath10k: reporting estimated tx airtime for fairness 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, 21 Jan 2019 16:48:41 -0000 Toke H=C3=B8iland-J=C3=B8rgensen writes: > Rajkumar Manoharan writes: > >> From: Kan Yan >> >> Transmit airtime will be estimated from last tx rate used. >> Firmware report tx rate by peer stats. Airtime is computed >> on tx path and the same will be reported to mac80211 upon >> tx completion. > > FYI, it seems that this last patch in the series no longer applies > cleanly on top of mac80211-next. May need a refresh. > > The mac80211 parts were merged into mac80211-next (thanks, Johannes!); I > guess the driver updates are waiting for drivers-next to catch up to > that? > > Patches 4 and 5 in the series are fine... This was meant to be a reply to v5 of the patch set (which is where I had the issue); apologies for picking the wrong one to reply to... -Toke > > -Toke