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 C8E173B2C4 for ; Fri, 10 Jun 2016 05:08:03 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail2.tohojo.dk DKIM-Filter: OpenDKIM Filter v2.10.3 mail2.tohojo.dk 207AB40B39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=201310; t=1465549682; bh=qukzUsxOmqZeUeLXUYGKVmdjEk8PH+un1J8rcq5OwFM=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=jbWu2B1Wo2As6cmeKiS0zBbAJOhcVvXQrCQ6IoKzlx1JR92aAgQnkWiMGNFQ7eHJg vTiRCfN2fgZ+jYQ7/PMabxGaIKUojmBhpoJXxHaTxSUePdDDy2QK01RP4punuRk31u +wkSGEXYg7i+zNNswotW+5mvOFyx6XYZXCToCxZg= Received: by alrua-karlstad.karlstad.toke.dk (Postfix, from userid 1000) id 2E014767D89; Fri, 10 Jun 2016 11:08:01 +0200 (CEST) From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: Michal Kazior Cc: Adrian Chadd , make-wifi-fast@lists.bufferbloat.net, ath9k-devel , "linux-wireless\@vger.kernel.org" References: <20160603165144.17356-1-toke@toke.dk> <20160603165144.17356-6-toke@toke.dk> <8737orucq4.fsf@toke.dk> <87k2i1ml43.fsf@toke.dk> <87wpm1b6bu.fsf@toke.dk> <87inxhl90y.fsf@toke.dk> Date: Fri, 10 Jun 2016 11:08:01 +0200 In-Reply-To: (Michal Kazior's message of "Fri, 10 Jun 2016 11:02:35 +0200") X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <877fdxl8cu.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: Fri, 10 Jun 2016 09:08:03 -0000 Michal Kazior writes: > For A-MPDU all MPDU rx status (except last one) should share the same > timestamp. Last one has a different one so all you need is to > distinguish first and last MPDU. Non A-MPDU obviously are special case > (status bits are pricky). Right. So comparing the rs_stamp between first and last MPDU should give the duration of the entire thing? This would require keeping state between subsequent calls to the RX handler. Also, what happens if the last MPDU is lost? >> Is the entire A-MPDU received before the RX handler is called for the >> first frame? > > No idea. Maybe it is as there's distinction between "more" and > "moreaggr". Hmm. If it is, comparing the stamp of the first MPDU to the current time (when handling it) should give the needed duration? Will try doing that and see what the result is. -Toke