From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [IPv6:2001:470:dc45:1000::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 9B1253BA8E for ; Thu, 5 Jul 2018 13:37:13 -0400 (EDT) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1530812232; bh=+l1D9HBLgFRSirCEQRQid6xXXeDRaXg5wvBt7Mm6pGE=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=UtC6T80JV54U4FENIhWCMZl/lVuxTtgCHFxE46WF+Y8afe9GVxHmqj/MdYVjGzN6C j8jzCY0eil77HhaKME6Jzazkt26Ets0CGH0UzyS/uAaC23Gz48shzZ3t8tcEU6Vcjg onoocZfM1o5vehxB/dmxtvfH3f5ac+0gVW2AroIu3YXfb/0Cq4+AU2XZhnA0vsWJKc J9egGRQcMb8Qpju4BTBOEZmhDXCBipJDvjX5kRyk081V0RHu96mVp1SDKEm+et56Ee mtXnFSVCZ64++ge5Qz0PJaMu+gakahX/7+hSQ8V/8fu7woz6jpEx7zals047qrPOQY gJragKVKhR+sA== To: Pete Heist Cc: bkil , Make-Wifi-fast In-Reply-To: References: <9E7E043B-2373-46ED-B122-38A287422999@eventide.io> <87d0wu7rbg.fsf@toke.dk> <8A44F1D4-1EB8-4D46-85F9-00C7307FF2D4@heistp.net> <2EC1279B-76C6-48C0-AED4-E9C4A7D0F004@heistp.net> <874lhdeso1.fsf@toke.dk> Date: Thu, 05 Jul 2018 19:37:10 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87fu0xd1o9.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Make-wifi-fast] mesh deployment with ath9k driver changes 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 Jul 2018 17:37:13 -0000 Pete Heist writes: >> On Jul 5, 2018, at 3:08 PM, Toke H=C3=B8iland-J=C3=B8rgensen wrote: >>=20 >> Pete Heist writes: >>=20 >>> And in the aqm driver support I=E2=80=99m not sure what fq_overmemory >>> signifies (Toke may know that) or if the other stats are within the >>> expected ranges for this amount of traffic. >>=20 >> Overmemory is the amount of times the total queue size went over the >> 4MiB limit. So I'd say that 60 million times is...quite a lot. Is there >> a lot of traffic that doesn't respond to congestion signals on that >> link? > > Wow, ok. Well, I suspect it=E2=80=99s p2p. Wouldn't be surprised. Note that packets will be dropped from the longest queue, though, so unresponsive flows just hurt themselves... -Toke