From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (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 B01403B2A0; Sun, 14 Aug 2016 18:21:22 -0400 (EDT) Received: by mail-it0-x233.google.com with SMTP id u186so26634049ita.0; Sun, 14 Aug 2016 15:21:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=J/hJtwftNFRD8LkWgMiAUjWLPcjJpDoqFWbHtuPjICo=; b=zT+FevemKlwjjArRqimsPXAdakLaGXMXVAAoA278RO3J8tx996VpkQrv6EWi+dAhhD I2dWyuIBy+TDXoeiUiz9W5Bhn8RU2L+4PBToTEyiNkWZhOIoAZTQbxbd3DBc62+sxOYH tnSrv7eBzZ6/frQo8f34U2GSo8XGSZTU30C+XG3j/GHHBwGaaPy2WMimTmseXB4SfsE8 nKiOlLAm2lQWuVY6dE7OlOwdhpPE0zEYgBsCXjCqInHhC0vC+EzRPj+dD5Ve1bFPd1A9 AUNA6ti2cNClhMBVfqHNUOL52OJATVYVMpr8c6QMosCK4ujmHzQSjM5vqHajms+moZp9 exvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=J/hJtwftNFRD8LkWgMiAUjWLPcjJpDoqFWbHtuPjICo=; b=eqnRQUxWa4A3M9dU0VxFIgsOwch9p+6WmgXs1aQbXNc6ZBTksZUYS1Ih2Q7XI2j/43 q64tIJk5agtqLwnuhzhmV2i9T5gUBGuMcv0WP22cBJyb5wghO1Q8cn/MSakneEVGrMNP 4k7wKgktXgLvV+F+HAH1Bgu9b4K+if4jWZGFO1pDZ3lm3XtAWKTY76fN8RaqlLO2bHUr R6IMO5UbUTnRFBPAPoeXZKPTRie3c9+82VN/yT+7yHiTCVC2OZWMsDuIiBhcCJqen20U 0KjH99dPQLTFgYhN5kGCxQNMCQU+2x6gOYogtAJSnl0PBK331e38ZpfKTSzDVx2omSnw nUIA== X-Gm-Message-State: AEkoouv0UFJAgoypdfm1XuYjRKYayLvkCjaflRZ8epCLdR0Vlg9YpxDLwO+rT2wGKduaYM1hdUdLF33Ez/RcKQ== X-Received: by 10.36.53.197 with SMTP id k188mr10166717ita.58.1471213282105; Sun, 14 Aug 2016 15:21:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.13.200 with HTTP; Sun, 14 Aug 2016 15:21:21 -0700 (PDT) In-Reply-To: <76eb6a6a-2f39-3b36-d4c1-04198083c0f6@gmail.com> References: <76eb6a6a-2f39-3b36-d4c1-04198083c0f6@gmail.com> From: Dave Taht Date: Sun, 14 Aug 2016 15:21:21 -0700 Message-ID: To: Noah Causin Cc: make-wifi-fast@lists.bufferbloat.net, "cerowrt-devel@lists.bufferbloat.net" , Felix Fietkau , Simon Wunderlich Content-Type: text/plain; charset=UTF-8 Subject: Re: [Cerowrt-devel] [Make-wifi-fast] wifi airtime fairness patches could use eyeballs and testing X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Aug 2016 22:21:22 -0000 Toke and I have now done a great deal of testing and exploration of the issue with leaving "fq" enabled on the ath9k (running with and without felix's patch). The only thing we've found that "moves the bar" is the presence or absence of crypto. With crypto + fq on, on the wndr 3800, we see a significant performance variation of 32-80mbit as the number of flows goes from 12 to 1. without crypto, with or with fq enabled, we are able to reliably get 120Mbits on our test setup. The patterns of the degradation are also often variable, we will have long periods where things are quite stable, and other 10-20 sec periods where throughput drops or stops almost entirely. It would be nice to get confirmation that the fq is working without crypto enabled. Ideas as to why crypto chops off so much throughput in the first place (from 120mbit to 80), and as to what else to poke into with crypto on, would be nice.