Return-path: Received: from mail-it0-f44.google.com ([209.85.214.44]:35212 "EHLO mail-it0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751105AbcFGABJ (ORCPT ); Mon, 6 Jun 2016 20:01:09 -0400 Received: by mail-it0-f44.google.com with SMTP id z189so59428184itg.0 for ; Mon, 06 Jun 2016 17:01:09 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20160603165144.17356-1-toke@toke.dk> <20160603165144.17356-6-toke@toke.dk> <8737orucq4.fsf@toke.dk> From: Adrian Chadd Date: Mon, 6 Jun 2016 17:01:08 -0700 Message-ID: (sfid-20160607_020114_318883_2CB7E913) Subject: Re: [RFC/RFT 5/5] ath9k: Count RX airtime in airtime deficit To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= Cc: "linux-wireless@vger.kernel.org" , make-wifi-fast@lists.bufferbloat.net, ath9k-devel Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: [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? -adrian