From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-x841.google.com (mail-qt1-x841.google.com [IPv6:2607:f8b0:4864:20::841]) (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 3032E3B2A4; Mon, 18 Mar 2019 05:26:47 -0400 (EDT) Received: by mail-qt1-x841.google.com with SMTP id w30so11733511qta.8; Mon, 18 Mar 2019 02:26:47 -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=/mQ2qaPTDikpo882ejGdwCJzw727nmgdkc+CgZd5pCg=; b=N/+CtQcUzp9hyrP5ezDRKQ38xpevxdZzegxYyaxTBHRg5FdpOfRgAlT39yJ8vLQ5zQ 1vTkaX5O4Po8kukfVn7aMNokCRiZeibvdbAzVYaW8jL0Ke+j6eQT5tz60Hiu0b1o6JjG iGHFw6brP898C5skRCHB5VhvgrZ4isKXDNsovCOnKjNJjtG+j1DFiFmWPcFuW+tZCY1V jVih9M7FqgQcQ3OI6NtTnKFayP20UAVgRufRRXHoZRG6DNb5EpP7s6Er3V2NbUlY4aY0 XihkHaowY6/6xI5ukHW0pRJlUdQwSPkJ0zmNabtvMlxloRIWux1FNVdJyEURYxwyK3aC rHkg== 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=/mQ2qaPTDikpo882ejGdwCJzw727nmgdkc+CgZd5pCg=; b=YV9aMjBz8OsPu+zEsQR9VfHw4A9I10acz67sUM94JdbUDjfCh7VK8YGe0vTCsrqiiQ hwOGG2myXWVkj+NVlecKqmsa1Pc41K0BtJ+kIp4qj96nDPoFZh0xsWRZ1K4Lj9fFZrMo 02RgTjfj2LhMoENycGDgayoMGtvONq7nNUJdBbtZdQJvtJVqTuT+VVQ4cULHc5GDpSui FjkSX42KN2lwWsgf2WOf1Vdy/AfN43GVvWVqKMTq/BnvqFYaktwxcC5U5pdCwmp8C7W6 YFkqaHLicV9RXSh+IWIEoGF8/clHW1RydOo8XqK7pt+PN2vnzkJ4bAjCWEip2eOEUG+/ uGVg== X-Gm-Message-State: APjAAAUaelOSRwEIAesWJRjkMVWmVYqBvk0zTJJS2VCla+U1z3Jn9RXi s9+ZwnU4vrcfozJPs3npM5dgIIgckjKrNMxRH841jg== X-Google-Smtp-Source: APXvYqwbiYXxTnqEjO7PLm2x1y/Fch6fajIdfRZcH/zxkeOaq47FD0YtafLuknc5kpcaAb8XOZ0i8mh0DWYlIAGhS5I= X-Received: by 2002:aed:23b4:: with SMTP id j49mr10103255qtc.175.1552901206359; Mon, 18 Mar 2019 02:26:46 -0700 (PDT) MIME-Version: 1.0 References: <189cdc56-9eff-4a9f-aee1-1eea06d78664@googlegroups.com> <1da4d9e4-13f9-4767-9519-93978664c79b@googlegroups.com> In-Reply-To: From: Dave Taht Date: Mon, 18 Mar 2019 02:26:35 -0700 Message-ID: To: Make-Wifi-fast , ecn-sane@lists.bufferbloat.net Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: [Ecn-sane] Fwd: [bbr-dev] Re: Applying BBRv2 patches 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: Mon, 18 Mar 2019 09:26:47 -0000 ---------- Forwarded message --------- From: 'Neal Cardwell' via BBR Development Date: Fri, Mar 15, 2019 at 12:18 PM Subject: Re: [bbr-dev] Re: Applying BBRv2 patches To: Jeremy Payne Cc: BBR Development Hi, The enhancements that we have been calling "BBR v2" are still under testing, and have not been posted yet. For BBR v2, we sketched out an overview and some lab test results at IETF 102 (links here). We'll be giving a quick update about that effort at the ICCRG session at IETF 104 in a few weeks. For Linux TCP BBR, the most recent upstream patches of interest are for improving performance with high degrees of aggregation (as in wifi, cellular, cable modems, LRO/GRO, etc) on low-RTT paths. The biggest impacts we have seen are cases with wifi links where the two-way propagation delay is in the range 1-10ms, so that would be a scenario to start with, for testing. Those patches are discussed here: https://groups.google.com/d/msg/bbr-dev/kBZaq98xCC4/5EUi7c3MCgAJ Keep in mind those patches are not in 5.0.2. They will be in 5.1, or if you have the option of building custom kernels then you can cherry-pick them on top of your 5.0.2. thanks, neal On Fri, Mar 15, 2019 at 11:34 AM Jeremy Payne wrote: > > Hello, > > I've been following developments here, and I'm now considering soaking BB= R on one of our production machines. > Question is, it seems there are some outstanding issues with BBR that may= affect network/application response times. > Before soaking in production, are there any suggested tests I can run in = the lab that show performance impacts without the > BBR2 patches, and then show performance improvements with the BBR2 patche= s? > > Primary use case is live MPEG-DASH/HLS video delivery. > > I plan on testing against a kernel that doesnt contain these patches, 4.1= 4.106, and a kernel that looks to contain most of the BBR2 patches, 5.0.2 > > Thanks! > > > On Wednesday, March 13, 2019 at 12:09:22 AM UTC-5, Jared Newman wrote: >> >> Hey BBR-dev, >> >> I'm trying to apply the patches given in https://groups.google.com/forum= /#!topic/bbr-dev/8pgyOyUavvY, but am struggling to find what commit of next= -net I should apply them on. I tried a couple different tags in https://git= .kernel.org/pub/scm/linux/kernel/git/davem/net-next.git but would always ge= t conflicts that I didn't feel comfortable resolving. Does anyone have a su= ggestion / commit hash to apply them to? >> >> Cheers, >> Jared. > > -- > 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. > For more options, visit https://groups.google.com/d/optout. -- 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. 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