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 2CE103B260 for ; Tue, 7 Jun 2016 04:58:08 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail2.tohojo.dk DKIM-Filter: OpenDKIM Filter v2.10.3 mail2.tohojo.dk C87CB40472 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=201310; t=1465289885; bh=r8JzUk0JhROZQ/tBrBfD2WafjFfgOxbUx0UlzhZx49k=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=kbBLOTrhjPr6VgWRbcblcGzjpUW3M9/9aflFKQ5Kf8zcBySEcgAoa9ZduPlUHWbBH rLayrYUvWNmv8E7ALbDMw1nAYKidk+s4zUxQ8T7/h+hEIPw1kIBrE6SkM15a1RFlup o7iwkT8TZSeTRJZcmOiBKS0vx8szn0Qbo1G7il8U= Sender: toke@toke.dk Received: by alrua-karlstad.karlstad.toke.dk (Postfix, from userid 1000) id D479175D371; Tue, 7 Jun 2016 10:58:04 +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> <8737orucq4.fsf@toke.dk> Date: Tue, 07 Jun 2016 10:58:04 +0200 In-Reply-To: (Adrian Chadd's message of "Mon, 6 Jun 2016 17:01:08 -0700") X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87k2i1ml43.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: Tue, 07 Jun 2016 08:58:08 -0000 Adrian Chadd writes: > [snip] > > I also found one of my notes in my version of this - how can we > estimate the duration of an A-MPDU, when we only get hardware > de-encapsulated frames? Well in my case I'm sidestepping this by getting the TX duration from a register in the hardware. There seems to be registers containing the duration spent on each step in the retry chain; I simply sum these. -Toke