From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (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 627813B2A4 for ; Tue, 17 Jul 2018 12:59:24 -0400 (EDT) Received: by mail-qt0-x235.google.com with SMTP id y19-v6so1503757qto.5 for ; Tue, 17 Jul 2018 09:59:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=rd0DnvLWWt/VMLWdFgeifV72iPy7HtNJsTIB1UxHjC4=; b=R52DqCzkZNTQ9qPKDa2NyTVYFOYMJQjgxug7dbuwowtCq6JSqI67X3dK12iJpPix2U NmxD001E9p0oA0gkEaeqReOOkBkS4w9dhAMkQ0ry8sNd3Kf2RTnImXYX0MiRs0bA+kMM ZZjOHyIgwoGxWcSMyP8kk88FooR4UXE2+s3nXxKhWSxIt9lY5Dpa65inw7mk/ASoT3O3 EgRQDjkbX86R9Fc8ZEc2vfCcpKWOTxYCPTx3oCntkUZmEIPZtapnZX1KYMFLK2BttLfW mC0CqPFEMbtivtzewoSk9vN9qlxCZTpZn6m8OzX5CJCJlHX0I6JCDSl2SDLLmqccC/8p 8OxQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=rd0DnvLWWt/VMLWdFgeifV72iPy7HtNJsTIB1UxHjC4=; b=T3PCkmwbFya9FGN0vUPrej2TzykMNYdULY96SwhhgxQr1ZwRZwU1SqA1ddmgFFjTRd UlS153/CG7Zy5k5ODf0tBIJPKzIIza6r3wOrxN2tGD10Z9l3lYLxNlvyFRcIcnbaW1ev 1qXecjq8Fh7D4oyqrDHxQFRgsD9QFrZC9aYl43olWbSAWtKWEkq8syBFSPC7aKtb1yGG BKN12s5O636DUdpbxgP+yAnVITWr2/O7ekDrCX1mJ1M5CfPIpiwDPm7SPATPn2iyfI/W Xo9BQJqafTqrWGIsr3S7G2UX3dMr4wa7TtQLiRyquABht6Jhts7fRWqpU3xthr5n4qM7 ZRLQ== X-Gm-Message-State: AOUpUlEisoKxDQJ2sUxY0VN4WRTnbSFcIMskHIZZ+bWoHmQvwuyk/JSi L34smu+JhYqf9NjZKLBnggZQ8uq2mR0pwiSaOGLsZA== X-Google-Smtp-Source: AAOMgpeEYdv/qlUQnhSwqIokNKT2/fLNIG4JLXPcLnOQlQ+jJU9mhbqL6cyfxJmGmYBRX41v6jhYGeoM0catvlsJSGI= X-Received: by 2002:ac8:354e:: with SMTP id z14-v6mr2475618qtb.261.1531846763713; Tue, 17 Jul 2018 09:59:23 -0700 (PDT) MIME-Version: 1.0 References: <1357421162.31089.1531812291583@webmail.strato.de> In-Reply-To: <1357421162.31089.1531812291583@webmail.strato.de> From: Dave Taht Date: Tue, 17 Jul 2018 09:59:12 -0700 Message-ID: To: fuller@beif.de Cc: Cake List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [Cake] =?utf-8?q?Using_cake_to_shape_1000=E2=80=99s_of_users=2E?= X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2018 16:59:24 -0000 On Tue, Jul 17, 2018 at 12:24 AM Felix Resch wrote: > > since commercial interest is involved, see here https://lists.bufferbloat= .net/pipermail/cake/2018-June/003861.html I grew that list substantially in the ending talk. It was motivating. :) I am thinking of doing something similar (with editorial comments) pointing to each of dslreports' values per ISP, like, for example, leveraging http://www.dslreports.com/speedtest/results/bufferbloat?up=3D1 To kvetch while pointing further to stuff like: http://www.dslreports.com/speedtest/results/isp/r3910-google-fiber http://www.dslreports.com/speedtest/results/isp/r2784-t-mobile http://www.dslreports.com/speedtest/results/isp/r896-sonic http://www.dslreports.com/speedtest/results/isp/r1579-Comcast%20XFINITY That angst out, ISPs and vendors that want to work with us to establish requirements and code for a transparent bridge/veth/cake-like thing are very welcome at any point! The core factor stopping us from even trying isn't lack of money or time... it is not knowing of *any* head-end equipment (DSLAM/CMTS/GPON/etc) that could be modified by us to have better queue management in the first place, and a transparent bridge seems second best, at best, with complexities involving ipv6 and ipv4 support, sag, nat, vlans, etc, etc - so we've focused on fixing the edge device itself, and making available published open source code and standards in the hope that some head-end vendor would pick it up... after being suitably nagged by their ISP customers. Or the sandvine type middlebox folk. Also, in terms of angst, we hope merely that ISPs would start supplying CPE that has our stuff in it (particularly since the aftermarket already has it, and it works in even the cheapest boxes made today), and either autoconfigure to their set rates, with cake, or supply that information to their end users to configure. It's been 6 years since the code hit the embedded world.... I'm pleased to say that "fq_codel for wifi" derivatives seem to propagating rapidly, at least. Maybe a fortigate or barracuda will ship some kind of smart queue management one day soon... if enough customers ask for it. example: https://forum.fortinet.com/tm.aspx?m=3D163978 on the transparent bridge front... Linux has issues scaling to high rates *on the receive path* at 10gigE+ speeds. I've certainly lain awake at night dreaming of what we could do with a smart line card for a cmts, or even a small dslam. > _______________________________________________ > Cake mailing list > Cake@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cake --=20 Dave T=C3=A4ht CEO, TekLibre, LLC http://www.teklibre.com Tel: 1-669-226-2619