From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vn0-x233.google.com (mail-vn0-x233.google.com [IPv6:2607:f8b0:400c:c0f::233]) (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 0A3A421F246 for ; Sun, 12 Apr 2015 02:58:12 -0700 (PDT) Received: by vnbg1 with SMTP id g1so13269217vnb.2 for ; Sun, 12 Apr 2015 02:58:11 -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=bs4jU2iGgcgI6Uc9LvVClyE4a0DDxrechXdecmHBifw=; b=hep52n53e8AkjMWJ8WkKXGr/QcY/jfr0yHeLPZnyPLwuauwEuOVvORGY9igejtF8uz 3+YxrB4x7MLRue9jhg68aeotbV7r2JoK1FzsOUb1uJouz/W1WEIGfcjtbzU/IOycH7ru UYkMy4XGwFvI7OVmoyaBt9ICU1/IXlsX8h1U4Xc1sI/Xj/ZDaxKuQAh/pAM8E2H6/rty kPOA8bq8AmNwAUBZncVyzrA7CXVAFSqpi/rKp1DzJeZFOQz7eG56qigcViEIj1wHECAY /bSnMOsXLCDwE+tIeQAyh5v/+9mlHue4To5O3NLzFF32P1TJcG+LABRtRXNvwqm0IAs1 fzRw== MIME-Version: 1.0 X-Received: by 10.52.10.202 with SMTP id k10mr11518749vdb.44.1428832691384; Sun, 12 Apr 2015 02:58:11 -0700 (PDT) Received: by 10.52.12.167 with HTTP; Sun, 12 Apr 2015 02:58:11 -0700 (PDT) Received: by 10.52.12.167 with HTTP; Sun, 12 Apr 2015 02:58:11 -0700 (PDT) In-Reply-To: References: Date: Sun, 12 Apr 2015 12:58:11 +0300 Message-ID: From: Jonathan Morton To: Adrian Popescu Content-Type: multipart/alternative; boundary=bcaec511e1940376360513840938 Cc: cake@lists.bufferbloat.net Subject: Re: [Cake] Cake3 - source code and some questions X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2015 09:58:41 -0000 --bcaec511e1940376360513840938 Content-Type: text/plain; charset=UTF-8 To answer the later questions first: Cake is designed for use at the internet edge, and therefore assumes internet scale RTTs. It does not have any sort of tuning for datacentre networks. But it does work and has a measurable effect on home LANs, even though it's not specifically tuned for that. If there is sufficient demand for cake's features on such networks, then a flag could be added to provide appropriate tuning for low RTTs. Fq_codel can already be tuned this way by adjusting the target and interval parameters. Cake does have tuning for low bandwidth links (increasing codel's target and interval), and has been run (but not yet extensively tested) at 64kbps. We have cake's code in a git repo, but I don't think we have anonymous pull access to it. Toke? - Jonathan Morton --bcaec511e1940376360513840938 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

To answer the later questions first:

Cake is designed for use at the internet edge, and therefore= assumes internet scale RTTs. It does not have any sort of tuning for datac= entre networks. But it does work and has a measurable effect on home LANs, = even though it's not specifically tuned for that.

If there is sufficient demand for cake's features on suc= h networks, then a flag could be added to provide appropriate tuning for lo= w RTTs. Fq_codel can already be tuned this way by adjusting the target and = interval parameters.

Cake does have tuning for low bandwidth links (increasing co= del's target and interval), and has been run (but not yet extensively t= ested) at 64kbps.

We have cake's code in a git repo, but I don't think= we have anonymous pull access to it. Toke?

- Jonathan Morton

--bcaec511e1940376360513840938--