From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nbd.name (nbd.name [IPv6:2a01:4f8:131:30e2::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 1FAB83B29E for ; Thu, 5 Jan 2017 08:23:57 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=nbd.name; s=20160729; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=WRLbGPiTilJO792piZT8bnlXrTbDfkNZoUTTtRbwUdY=; b=sys0zBs4t5/QMRBcjgZkBfYWcMuSEzv3X+64uQ3TP0REL5Fz3UsMsOPyEF65pFVD5d74GGREMik3NfhPEo0kOhvpt5hJCuupy7NGxDE8/LISDpptG2wJK2bfrbv3Rr7AHavkfuEUgWyOofMMl4pz9bLl48H7/3x8x2R70POt4/U=; To: Loganaden Velvindron , Dave Taht References: Cc: make-wifi-fast@lists.bufferbloat.net, LEDE Development List From: Felix Fietkau Message-ID: <46229222-ccb9-549d-578d-a8f4c9b83de4@nbd.name> Date: Thu, 5 Jan 2017 14:23:55 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Make-wifi-fast] ath9k airtime fairness stabiity issues? 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: Thu, 05 Jan 2017 13:23:57 -0000 On 2017-01-05 14:22, Loganaden Velvindron wrote: > On Thu, Jan 5, 2017 at 4:59 PM, Dave Taht wrote: >> Felix: >> >> Was there a bugreport? (don't see one) >> >> Do you have a specific device or behavior triggering this revert? >> >> >> On Thu, Jan 5, 2017 at 4:42 AM, Dave Taht wrote: >>> https://github.com/lede-project/source/commit/c296ba834db4ce8c71e0ad7030aab188fe60b27b >> >> > > Hi nbd & Toke, > > Would it be possible to enable it only on platforms like the tp-link > archer c7 v2 and the ubnt, where we have confirmed test reports for > the upcoming release ? I think it's quite unlikely that these issues are hardware specific. It's probably more related to the environment, types of clients, or even traffic patterns. - Felix