From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (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 26EE221F351 for ; Wed, 22 Apr 2015 11:34:07 -0700 (PDT) Received: by iget9 with SMTP id t9so743162ige.1 for ; Wed, 22 Apr 2015 11:34:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:to:cc:date:in-reply-to:references :content-type:mime-version:content-transfer-encoding; bh=A4WKHGl+UKKYxkhEPw5AJ9Z7r7raCEKP3mavRbJl9s8=; b=cM+3N5wUl3GDpoz/4wFyXbYszLTmKqILT9zGTpuq2fJBiAhYO1jEEfA3FcP6RrLrKV J4m1whsdEBjpa9x5xL0xEsMcwcRMvUgVs359Hbnv/b3OyNGJGbj9akJBy/3opYAT9+/f yFcek10SL6cnKOjbp0fs4sH1CI731r+irANxMRkPUEz73bpVXCWEVuHX6TpFHLPTARWz Xc/XnCnyfnTk6lZgMu5IiQVe3aDGIPNj7T/N4k5zd6X1N8pFoUln0c7dXvRwGjlIYRjQ xnVmDbblcaYu7Tbv2LmZQt3DE3tcTGy4QxMHfJPNmAyg2wqz/orif+BiKWLx4ePo5oXj IL8w== X-Received: by 10.107.132.42 with SMTP id g42mr38324717iod.25.1429727647393; Wed, 22 Apr 2015 11:34:07 -0700 (PDT) Received: from [172.26.55.207] ([172.26.55.207]) by mx.google.com with ESMTPSA id fv2sm10621409igb.22.2015.04.22.11.34.06 (version=TLSv1.2 cipher=AES128-GCM-SHA256 bits=128/128); Wed, 22 Apr 2015 11:34:07 -0700 (PDT) Message-ID: <1429727646.18561.126.camel@edumazet-glaptop2.roam.corp.google.com> From: Eric Dumazet To: Jim Gettys Date: Wed, 22 Apr 2015 11:34:06 -0700 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: bloat Subject: Re: [Bloat] Pacing ---- was RE: RE : DSLReports Speed Test has latency measurement built-in X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Apr 2015 18:34:36 -0000 On Wed, 2015-04-22 at 10:53 -0700, Jim Gettys wrote: > Actually, fq_codel's sparse flow optimization provides a pretty strong > incentive for pacing traffic. > > > If your TCP traffic is well paced, and is running at a rate below that > of the bottleneck, then it will not build a queue. > > > It will then be recognized as a "good guy" flow, and scheduled > preferentially against other TCP flows that do build a queue (which is > what happens today, with TCP's without pacing). > - Jim > Well, fq_codel 'sparse flow' is not going to state that a flow sending one packet every 100 ms is a 'good guy' meaning it needs a boost. This kind of flow (paced but sending 10 packets per second) will use the normal RR mechanism. However, he will get a normal share, compared to some elephant flows. fq_codel 'boost' is only for first packets of a new flow.