From: David Lang <david@lang.hm>
To: Kartik Agaram <ak@akkartik.com>
Cc: Jordan Peacock <hewhocutsdown@gmail.com>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] http/2
Date: Sun, 15 Mar 2015 00:13:01 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1503150009500.22474@nftneq.ynat.uz> (raw)
In-Reply-To: <CANOtCLVp_A3hXd_vto2_SO=trH8-bQnAJV3iWswHM4xUmr5XSA@mail.gmail.com>
[-- Attachment #1: Type: TEXT/Plain, Size: 886 bytes --]
On Fri, 6 Mar 2015, Kartik Agaram wrote:
> 3. Has there been discussion of solving bufferbloat at the TCP layer, by
> making buffers harder to fill up? I'm thinking of heuristics like
> disallowing a single site from using 80% of the buffer, thereby leaving
> some slack available for other bursty requirements.
There are already multiple solutions at the TCP layer.
1. TCP slows down if it gets ECN responses, so it won't fill up buffers
not everything implements ECN and some firewall-type devices strip out or lie
about ECN data
2. TCP slows down if packets get dropped. Not all dropping needs to wait until
the buffers are full.
2a fq_codel does exactly this, it drops packets when there is congestion, before
the buffers fill up.
The problem is just getting these changes into new equipment/software and then
replacing the equipment/software in the field.
David Lang
[-- Attachment #2: Type: TEXT/PLAIN, Size: 140 bytes --]
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat
prev parent reply other threads:[~2015-03-15 7:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 21:38 Kartik Agaram
2015-03-12 15:02 ` Jonathan Morton
2015-03-12 18:18 ` Narseo Vallina Rodriguez
2015-03-12 18:39 ` Jonathan Morton
2015-03-12 18:56 ` Narseo Vallina Rodriguez
2015-03-12 19:07 ` Jonathan Morton
2015-03-12 19:28 ` Narseo Vallina Rodriguez
2015-03-12 19:42 ` Jonathan Morton
2015-03-15 7:23 ` Mikael Abrahamsson
2015-03-12 18:05 ` Rich Brown
2015-03-15 7:13 ` David Lang [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=alpine.DEB.2.02.1503150009500.22474@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=ak@akkartik.com \
--cc=bloat@lists.bufferbloat.net \
--cc=hewhocutsdown@gmail.com \
/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