From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it1-x132.google.com (mail-it1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (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 7D7993B29E; Tue, 28 May 2019 11:51:15 -0400 (EDT) Received: by mail-it1-x132.google.com with SMTP id h11so4666616itf.5; Tue, 28 May 2019 08:51:15 -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 :content-transfer-encoding; bh=gMSy6omKOX68fV7Ibw9GMStYF8WrtdlyeAV82i7kweo=; b=S94OIHCxRClLzkFmQ2woQ3ibyhwSlf4e5b/quRO3vIUv8qc8ivcjkUTPhqI4V82OSQ NH7NoxbnAZxpv2X7theH7Q/G96aMsA/65SAHAkuORQm7yBwUEeenP9HsjXXrcqn/Z4dj HV0XH2D0/5uj9DSVaz0WtrtNN4JFfhdpgoy6fItVZr+Z7niW35VjP4mFjwZWRY5QIO8c btaoQUqKkg/MXoLTJ8C0PkZE44AllwlbHf0m87jOcpoJ0V/7PZwj0cS/pGSyXKzIq9bb VZ8gWynWx1BHNqOGRgBj4XV1bgAIzhanuNJ3VGlszFasfSGhN6XRfuJce5i5laz4tqdq t15Q== 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:content-transfer-encoding; bh=gMSy6omKOX68fV7Ibw9GMStYF8WrtdlyeAV82i7kweo=; b=GeSYZ+Sq6r2UP3WEeSn9tyPMn18FnSYER53ZDANN7rrdixhQGc8MFhDhqNG4uewXCA FJZkh12HTMauw50YWiOF43FHFWZkrEUyHo3/lnL8exb8rMcZEwnDdynVN1qxCMAX9Qps Vqey7EdHlIa3LzAwCfBJ3hnpWPn8NaCRJou+9EaFO9yVxtwE6Lm3x3b0HYdI7CTqYDB8 bf2SHmTBLMOkj/+dWQht7S5KOubxFpeMLiYBcOH7+pcd+B9As0KbkH4Zb/M089smHrVx MYkf+rhY5SpU6YAPs6pS8pQWqma2fzPrXg48UlEqoEvtnn3sErGUxCzdznPQXcmKiyP8 UTJw== X-Gm-Message-State: APjAAAX1TECjGEry5MmwdWT4HpCBWkbHCI8lC1qSvDA1McGy6VBDsFX+ v48/eP3aD9oUjwKhik6QPrr9H2eNYviOPLuTI2FVMA== X-Google-Smtp-Source: APXvYqx+Mfny1JWEryukJobFD4m/xX/DALg6+Wy6/VPyLEfetAXljC6mTtp55BKs8OD8e6Wil2oq3zE8bXL/HhCzRyw= X-Received: by 2002:a05:660c:28a:: with SMTP id s10mr3611473itl.173.1559058674660; Tue, 28 May 2019 08:51:14 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dave Taht Date: Tue, 28 May 2019 08:51:03 -0700 Message-ID: To: Cake List , ECN-Sane , bloat Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: [Ecn-sane] Fwd: [bbr-dev] BBR v2 ECN X-BeenThere: ecn-sane@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of explicit congestion notification's impact on the Internet List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2019 15:51:15 -0000 At least there will be a testable version of a L4S compliant BBRv2 before it goes upstream. (see below) I fear for what this will do to every inbound shaper in the world. (and also network namespaces, the fq_codel for wifi stuff, and the entire fq_codel deployment in general). All along (regardless of the SCE idea) I'd hoped for a simple, conservative rfc3168 compliant response in BBR to CE markings, and I didn't like how much BBR ignores packet loss as a signal in the first place. I thought, when the end users are desperately inbound shaping to keep their networks usable for all traffic, explicit signalling from that existing userbase with that expectation for a reasonable response seemed so reasonable... /me logs out for the day ---------- Forwarded message --------- From: 'Neal Cardwell' via BBR Development Date: Tue, May 28, 2019 at 7:11 AM Subject: Re: [bbr-dev] BBR v2 ECN To: Ingemar Johansson Cc: BBR Development On Tue, May 28, 2019 at 8:35 AM Ingemar Johansson wrote: > > Hi > > > Looking through the v5.2-rc2 code I can see that a parameter 'delivered_c= e' is defined in tcp_sock but other than that I don't see any evidence for = the support of ECN (L4S) in BBRv2. Do you still plan to include L4S support= for BBRv2 ? Hi Ingemar, Yes, we still plan on including L4S support for BBRv2. BBRv2 is not upstream in the Linux TCP code base yet. We are working on getting the code ready for a pre-release/RFC version that we plan on posting at: https://github.com/google/bbr But indeed tp->delivered and tp->delivered_ce are part of the infrastructure inside the Linux TCP stack that BBRv2 makes use of. cheers, neal -- You received this message because you are subscribed to the Google Groups "BBR Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to bbr-dev+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bbr-dev/CADVnQy%3DF4rHfLt2Nm-1rUGkfMjueju= _mWj5f%2BDdqFqBdaJ83oA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. --=20 Dave T=C3=A4ht CTO, TekLibre, LLC http://www.teklibre.com Tel: 1-831-205-9740