From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2.tohojo.dk (mail2.tohojo.dk [77.235.48.147]) (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 EA7C73B25D for ; Sun, 5 Jun 2016 06:55:17 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail2.tohojo.dk DKIM-Filter: OpenDKIM Filter v2.10.3 mail2.tohojo.dk 314EC40472 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=201310; t=1465124116; bh=KVlVfWyby+hWl1sJOUDyHAzTFO5ti7ulteivNdB24OI=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=CC0wSMgrOQi8LpRSPfEkB7UeaLqoWZWWAZc0R/LWibYYY5SMDB+4P4pKzJwGgNzDy 2+F0FLUCWjNGvwFX8XIybHPvloaTJd1jjD3WQRcDaK3+hFhCmWUfxNfVgdC16o9CHd MJ5GAXTUARNeqx/2HKrQzr6cUWJt1h3Z6seMY2RA= Sender: toke@toke.dk Received: by alrua-karlstad.karlstad.toke.dk (Postfix, from userid 1000) id 3690C75801E; Sun, 5 Jun 2016 12:55:15 +0200 (CEST) From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: Adrian Chadd Cc: "linux-wireless\@vger.kernel.org" , make-wifi-fast@lists.bufferbloat.net, ath9k-devel References: <20160603165144.17356-1-toke@toke.dk> <20160603165144.17356-6-toke@toke.dk> Date: Sun, 05 Jun 2016 12:55:15 +0200 In-Reply-To: (Adrian Chadd's message of "Sat, 4 Jun 2016 10:06:08 -0700") X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <8737orucq4.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Make-wifi-fast] [RFC/RFT 5/5] ath9k: Count RX airtime in airtime deficit 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: Sun, 05 Jun 2016 10:55:18 -0000 Adrian Chadd writes: > I've been working on something similar in freebsd, so cool to see this > happening here! Cool. Do you have code available somewhere? > The only thing missing atm is STBC and LDPC. My RX airtime code looks > basically like this one too; but I have TODO items for ensuring > LDPC/STBC calculations are sane. So basically this means taking into account whether there was MIMO in use (which may lower the transmit time)? My understanding is that (at least in Linux) this is encoded in the rate tables (i.e. a MIMO rate is a separate entry). Am I wrong in thinking so? Or is this something else entirely? -Toke