From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jim Gettys <jg@freedesktop.org>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Pacing ---- was RE: RE : DSLReports Speed Test has latency measurement built-in
Date: Wed, 22 Apr 2015 11:34:06 -0700 [thread overview]
Message-ID: <1429727646.18561.126.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <CAGhGL2A1se847yZ6sdevLPTDAfsWNJjD-CT40vRZYpcBWfxVGA@mail.gmail.com>
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.
prev parent reply other threads:[~2015-04-22 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 17:05 Bill Ver Steeg (versteb)
2015-04-22 17:53 ` Jim Gettys
2015-04-22 17:56 ` Bill Ver Steeg (versteb)
2015-04-22 18:34 ` Eric Dumazet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1429727646.18561.126.camel@edumazet-glaptop2.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jg@freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox