From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::243]) (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 161623B29E for ; Wed, 25 Jan 2017 17:12:08 -0500 (EST) Received: by mail-pg0-x243.google.com with SMTP id 194so20751600pgd.0 for ; Wed, 25 Jan 2017 14:12:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:cc:date:in-reply-to:references :mime-version:content-transfer-encoding; bh=u4wdoRIY+bHVqovif/mN03K/eFUb87DmxmgeRllMckg=; b=hvcspp4T+fv0BbcWaiSfgMenbCmmurWDVd1TSXRqOW5Kxc2xMW26TYsvO7fhaLBbp+ QD8Gt9izksIYQdUJIavjWxLX0q+xcXkifyF4MlCxV45TFMeNYstOz++8ahbbug6QZfiW amE8QrNHfQaZLROGak3tycVuCgDznTXC2GyEMTsqk5XP6lbEJuOB2QlaZxoxPj3MwRTy ggSZPewFJd4z8ljMmVWvPZbONYAcJt3dYgTdWmHHTxqEX6U6w5RFU7+K/WY6mL3DHedv 4qQ0kH6rK0yU4KDvQDqPpDpG1ap5uvW6Jf1p9K0K5Mzl3jMcccGN8LnwJcbn0EbKdnil MOaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=u4wdoRIY+bHVqovif/mN03K/eFUb87DmxmgeRllMckg=; b=pDaYISfHiDCsO3O7Q8E78RzwBGl7RJVO42lCYBxwDwP9VHCWFC7pDTWud2z/Ao5C8b 5iQLimCAGMpyb5uaq3ctq1GWlvaewgercpLmrIYorHs2ht5xQ5zBWFUxAptGRzxT8Gc5 ebADaVvhoQk6JtWO4YeBImDZqS8vVKL+gkaewjjYIhtQCC1tExpPoq5+oMeK1OOoTTcv cX7BV/g+sz0RhGtpVtsfRKLshhnDkWYWPQOpaHiioMm8Tqdc7Iwox7o261+LHT32wLff 4LnVg1begY4tq7OlzBEpg2po5u9X4Gzj1p+5Ec0LZrSQ0vEhMZ5hjTYP2C0QobbSkO9/ eSyA== X-Gm-Message-State: AIkVDXJs5vSd8EKsmIEz0WONzgLv9Dqf7coBjSaGaudqzJT2CHVIM2ONK2OO1aFcXHv9jg== X-Received: by 10.84.210.232 with SMTP id a95mr6919124pli.31.1485382327167; Wed, 25 Jan 2017 14:12:07 -0800 (PST) Received: from ?IPv6:2620:0:1000:1704:901f:c554:68ed:6757? ([2620:0:1000:1704:901f:c554:68ed:6757]) by smtp.googlemail.com with ESMTPSA id r8sm3363364pfa.44.2017.01.25.14.12.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Jan 2017 14:12:06 -0800 (PST) Message-ID: <1485382325.5145.64.camel@edumazet-glaptop3.roam.corp.google.com> From: Eric Dumazet To: "Steinar H. Gunderson" Cc: Neal Cardwell , bloat Date: Wed, 25 Jan 2017 14:12:05 -0800 In-Reply-To: <20170125220621.GA22074@sesse.net> References: <20170125220621.GA22074@sesse.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Bloat] Initial tests with BBR in kernel 4.9 X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 22:12:08 -0000 On Wed, 2017-01-25 at 23:06 +0100, Steinar H. Gunderson wrote: > On Wed, Jan 25, 2017 at 05:01:04PM -0500, Neal Cardwell wrote: > > Nope, BBR needs pacing to work correctly, and currently fq is the only > > Linux qdisc that implements pacing. > > I really wish sch_fq was renamed sch_pacing :-) And of course that we had a > single qdisc that was ideal for both end hosts and routers (especially since > some machines act as both). Well, pacing is optional in sch_fq. Only the FQ part is not optional. So sch_fq is actually a proper name ;) I have on my plate few things : 1) Add a fallback to actually do pacing in TCP itself, if it detects no pacing happens in a qdisc. This would be okay for devices that have very few local TCP flows (eg a router) 2) Add (optional) pacing to fq_codel. But this would come later.