From: Dave Taht <dave.taht@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: bloat <bloat@lists.bufferbloat.net>,
Ivan Pepelnjak <ipepelnjak@gmail.com>
Subject: Re: [Bloat] Blog post: "Do packet drops matter for TCP"
Date: Fri, 7 Jun 2019 10:10:36 -0700 [thread overview]
Message-ID: <CAA93jw58bHxHkhSa-_LSUM_cQo_jLVc88+wbASxiqNKw7FG5fg@mail.gmail.com> (raw)
In-Reply-To: <20190607093014.7b3e26af@hermes.lan>
On Fri, Jun 7, 2019 at 9:30 AM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> Good summary of bufferbloat from network operator point of view.
Thanks stephen!
> https://blog.ipspace.net/2019/06/do-packet-drops-matter-for-tcp.html?ck_subscriber_id=182966812
One of these years ivan will mention fq_codel in a sentence. From a
network operator's perspective:
fq_codel ensures statistical multiplexing
fq_codel ensures that congestion control algorithms across many flows
fate share faster
fq_codel is more robust against packet floods
fq_codel is safer to use ecn with
anything else?
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
prev parent reply other threads:[~2019-06-07 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 16:30 Stephen Hemminger
2019-06-07 17:10 ` Dave Taht [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=CAA93jw58bHxHkhSa-_LSUM_cQo_jLVc88+wbASxiqNKw7FG5fg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=ipepelnjak@gmail.com \
--cc=stephen@networkplumber.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