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 EB3A03B25E for ; Mon, 5 Sep 2016 13:26:36 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail2.tohojo.dk DKIM-Filter: OpenDKIM Filter v2.10.3 mail2.tohojo.dk BAC864161D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=201310; t=1473096394; bh=Kv7jcdhgOI/rM0GSnYiQ6u0Qum5cSewjfkcMifczwfw=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=jFa1aJbs5TaSnoOQy+Jr6fUfH0QvJ2eXCpS5jZLWVFb7P4qNBiBnMuG9RBuEr64OZ 1npDHRmIH2hGRBNwy2zk9P58iqvJikNjj93T9EDihwjVvSO+IpRGXCPc70BaUkb9yC 1RrlYD2IAlqIyg0zH5C3mOZy33d1M1hoq8d8F2JY= Sender: toke@toke.dk Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id C870C7916; Mon, 5 Sep 2016 19:26:33 +0200 (CEST) From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: Dave Taht Cc: make-wifi-fast@lists.bufferbloat.net References: <20160902134104.29309-1-toke@toke.dk> <20160905113042.22271-1-toke@toke.dk> <87oa4249hf.fsf@toke.dk> Date: Mon, 05 Sep 2016 19:26:33 +0200 In-Reply-To: (Dave Taht's message of "Mon, 5 Sep 2016 10:00:55 -0700") X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <8760qab6ly.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Make-wifi-fast] [PATCH v7] mac80211: Move reorder-sensitive TX handlers to after TXQ dequeue. 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, 05 Sep 2016 17:26:37 -0000 Dave Taht writes: > Just when I thought it was safe to boot up a router. Got a build from this? > > (feature request - the UAP-ac-lite is working well, and also gets > built out of the ar71xx tree) https://kau.toke.dk/lede/airtime-fairness-builds/ar71xx/generic/ built from this tree: https://kau.toke.dk/git/lede/ > Regarding the rate suggestion back-shift to earlier, does that defer > it until the queue empties, or merely 2 times through the algo, where > intermediate queues, before, it was every time (potentially). I have read this paragraph five or six times now, but for the life of me I can't make sense of it. So, erm... huh? -Toke