From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2.tohojo.dk (mail2.tohojo.dk [IPv6:2a01:4f8:200:3141::101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 8A5D821F1C6 for ; Thu, 20 Mar 2014 09:44:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at example.com Received: by alrua-kau.localdomain (Postfix, from userid 1000) id 1F1B28FAE7; Thu, 20 Mar 2014 17:44:03 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=toke.dk; s=201310; t=1395333844; bh=Qq0N3W2CR4TdsGmMLhf8sfnNmSc8iw9FOiL8s8Ksckk=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=dRjpe3nGxzQ33z8dOoY1kxBBup6y8Igtu6u/1usKs15QkCIKAdP2JR9UGy7IEwy4T jvGjWiUvGHl+h3hDg4jpJg8ZziHVlg5XbqE9+iHeDBW78bLPm5ib5HASB3yB2afuJ3 SAE1SHH09PKtZfazG3Tsyfd+t/3DXA1czM/SGhTI= From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: Dave Taht References: <20140318145221.GA31327@sesse.net> <07BD4518-2A7E-4F43-8978-791E3B2BDA2A@cisco.com> <87eh1wc05c.fsf@toke.dk> Date: Thu, 20 Mar 2014 17:44:01 +0100 In-Reply-To: (Dave Taht's message of "Thu, 20 Mar 2014 09:29:29 -0700") Message-ID: <87a9ckbz1q.fsf@toke.dk> Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Cc: bloat Subject: Re: [Bloat] AQM creeping into L2 equipment X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Mar 2014 16:44:15 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Dave Taht writes: > I find it puzzling that you still lose the measurement flows early on. > Setting some QoS on via WTD might be interesting. Well if you can be more specific, I'll be happy to. Was looking for a way to have per-protocol QoS settings, but there does not seem to be any From=20the documentation (only IP-based). > If you have a later OS than 3.13 on the sources/sinks you might want > to try sch_fq (and sch_pfifo_fast for reference) - the improvements to > Linux's TCP are such that on a short path like this that the control > loop stays very tight - only two TSO offloads per flow, really > accurate use of tcp timestamps, etc. Added a result set with sch_fq in place of fq_codel to the bottom of the same page. Doesn't appear to make much of a difference... > See also if you have hardware flow control enabled (via ethtool) If by that you mean pause frames, ethtool seems to think not: Settings for eth2: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full=20 100baseT/Half 100baseT/Full=20 1000baseT/Full=20 Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full=20 100baseT/Half 100baseT/Full=20 1000baseT/Full=20 Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: off Supports Wake-on: d Wake-on: d Current message level: 0x00000007 (7) drv probe link Link detected: yes =2DToke --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBCAAGBQJTKxrRAAoJEENeEGz1+utPm30IAK252rzXG1YG4dAdWwMuCLyW Gpa5uKKiggjVyse9PSCamrdr6MJwaYhhDJbRzbgXy8sA96dUOOX6cO0/EmNcRMvi 0pW5+NbTIIZ1jp/GcuCiE72TXxWx1GY6YNnVqk99Gx+C0OUA9N6MJ0mvJFoj94mz NUte4t62vahn9F0CIBQG0wKSdML4GBbFilJwIKM89c2VCwqDHbF6clMKtGAnXlug pIOGPFyQOOhUXCG53TL0WyAdC08E1ofylFzEwtFcI3f5v+Q3TVamVmYpyEHAtu/H 3gpEJlQr6KPeazaHXUKOY48uFwRYID1UzzwK4FP3S+WgitRJ8jb132kjsRQB/MM= =RYr1 -----END PGP SIGNATURE----- --=-=-=--