From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vn0-x236.google.com (mail-vn0-x236.google.com [IPv6:2607:f8b0:400c:c0f::236]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 0E94521F60F for ; Sat, 6 Jun 2015 06:53:44 -0700 (PDT) Received: by vnbg7 with SMTP id g7so6210694vnb.10 for ; Sat, 06 Jun 2015 06:53:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xlEKtBO0WuPyQelFTuwdo+FK9mWpQBLX6W2hAWbj41Q=; b=GgoagicMSaoDLfyp608woUo3Ehqy2+EjIBP2lde/2UERVrTCyhO9lKnHuDZOmhb21Z QIhHkTIwzLq0iNXuihSiJdJbVnyt81ig2XesKdJKWKdIouSCv7RamtKO9ymtAmO8mJNT 5paGSHb/OrajQU7ThpyuO0ax4CaXLQgRQ+jMXaxOjtgxI3HcYPwIHmILGYRmkcwe6Ewl La3jkoNiFviEkHQs7KdsTM8nxYBPfc/XAFOk0BZ6JHPKQTz3LUsPHYf5lrwGUHcJcGbs gDPswU9oLvXpw4lGKN7M3aFDxVYrfYlWOVqfaVp4ix+CdaL4gxhNxEaHwjjApjFK8yjN 6meg== MIME-Version: 1.0 X-Received: by 10.52.251.107 with SMTP id zj11mr15005589vdc.96.1433598823652; Sat, 06 Jun 2015 06:53:43 -0700 (PDT) Received: by 10.52.12.167 with HTTP; Sat, 6 Jun 2015 06:53:43 -0700 (PDT) Received: by 10.52.12.167 with HTTP; Sat, 6 Jun 2015 06:53:43 -0700 (PDT) In-Reply-To: <5572F7E0.3060602@darbyshire-bryant.me.uk> References: <5572F7E0.3060602@darbyshire-bryant.me.uk> Date: Sat, 6 Jun 2015 16:53:43 +0300 Message-ID: From: Jonathan Morton To: Kevin Darbyshire-Bryant Content-Type: multipart/alternative; boundary=001a1134d45ea265f20517d9bc0f Cc: bloat Subject: Re: [Bloat] ADSL, ATM drivers, bloat, education & confusion 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: Sat, 06 Jun 2015 13:54:13 -0000 --001a1134d45ea265f20517d9bc0f Content-Type: text/plain; charset=UTF-8 Ideally, one would read the raw sync rate out of the modem (there has to be a way to do that, since it is able to report it in the web interface), and use that to set cake's bandwidth parameter. You could update it periodically using "tc qdisc change ...". You will need to set the overhead calculation correctly, probably using "pppoa-vcmux" or similar, depending on precisely what encapsulation your ISP uses. If you're not confident about that, specify "conservative" to begin with. Once you have that, you can experiment to see how much you need to reduce the raw sync rate to achieve full bottleneck control - hopefully not much, at most 1%. The same approach would also work for inbound if necessary, except that you would need to reduce the raw sync rate rather more. - Jonathan Morton --001a1134d45ea265f20517d9bc0f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Ideally, one would read the raw sync rate out of the modem (= there has to be a way to do that, since it is able to report it in the web = interface), and use that to set cake's bandwidth parameter. You could u= pdate it periodically using "tc qdisc change ...".

You will need to set the overhead calculation correctly, pro= bably using "pppoa-vcmux" or similar, depending on precisely what= encapsulation your ISP uses. If you're not confident about that, speci= fy "conservative" to begin with. Once you have that, you can expe= riment to see how much you need to reduce the raw sync rate to achieve full= bottleneck control - hopefully not much, at most 1%.

The same approach would also work for inbound if necessary, = except that you would need to reduce the raw sync rate rather more.

- Jonathan Morton

--001a1134d45ea265f20517d9bc0f--