From: David Lang <david@lang.hm>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: moeller0 <moeller0@gmx.de>,
cake@lists.bufferbloat.net, codel@lists.bufferbloat.net
Subject: Re: [Cake] Proposing COBALT
Date: Fri, 20 May 2016 06:41:01 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1605200638530.1578@nftneq.ynat.uz> (raw)
In-Reply-To: <A714A489-BA53-4FCF-BECC-1C092619C556@gmail.com>
On Fri, 20 May 2016, Jonathan Morton wrote:
> Normal traffic does not include large numbers of fragmented packets (I would
> expect a mere handful from certain one-shot request-response protocols which
> can produce large responses), so it is better to shunt them to a single queue
> per host-pair.
I don't agree with this.
Normal traffic on a well setup network should not include large numbers of
fragmented packets. But I have seen too many networks that fragment almost
everything as a result of there being a hop that goes through one or more
tunneling layers that lower the effective MTU (and no, path mtu discovery does
not always work)
David Lang
next prev parent reply other threads:[~2016-05-20 13:41 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 10:04 Jonathan Morton
2016-05-20 11:37 ` moeller0
2016-05-20 12:18 ` Jonathan Morton
2016-05-20 13:22 ` moeller0
2016-05-20 14:36 ` Jonathan Morton
2016-05-20 16:03 ` David Lang
2016-05-20 17:31 ` Jonathan Morton
2016-05-20 16:37 ` Luis E. Garcia
2016-05-20 16:43 ` Jonathan Morton
2016-05-20 16:55 ` Luis E. Garcia
2016-05-23 18:30 ` Jonathan Morton
2016-05-23 19:11 ` Luis E. Garcia
2016-05-24 13:47 ` [Cake] [Codel] " Jeff Weeks
2016-05-24 14:07 ` Jonathan Morton
2016-05-24 15:52 ` Dave Täht
2016-05-24 15:56 ` Jonathan Morton
2016-05-24 16:02 ` Dave Taht
2016-05-25 6:40 ` Loganaden Velvindron
2016-05-25 12:00 ` Benjamin Cronce
2016-05-26 12:33 ` Jonathan Morton
2016-06-03 19:09 ` Noah Causin
2016-06-03 19:34 ` Jonathan Morton
2016-06-04 1:01 ` Andrew McGregor
2016-06-04 6:23 ` Jonathan Morton
2016-06-04 13:55 ` Jonathan Morton
2016-06-04 14:01 ` moeller0
2016-06-04 14:16 ` Vincent Frentzel
2016-06-04 14:16 ` Jonathan Morton
2016-06-04 15:03 ` moeller0
2016-06-04 17:10 ` Noah Causin
2016-06-04 17:49 ` Eric Dumazet
2016-06-04 19:55 ` Jonathan Morton
2016-06-04 20:56 ` Eric Dumazet
2016-06-27 3:56 ` Jonathan Morton
2016-06-27 7:59 ` moeller0
2016-06-27 15:18 ` Kevin Darbyshire-Bryant
2016-06-28 2:51 ` Jonathan Morton
2016-06-28 8:40 ` Kevin Darbyshire-Bryant
2016-06-28 15:33 ` Jonathan Morton
2016-06-28 17:37 ` Kevin Darbyshire-Bryant
2016-06-29 15:22 ` Kevin Darbyshire-Bryant
2016-06-30 8:16 ` Kevin Darbyshire-Bryant
2016-06-28 15:44 ` Dave Taht
2016-05-20 13:41 ` David Lang [this message]
2016-05-20 13:46 ` [Cake] " moeller0
2016-05-20 14:04 ` David Lang
2016-05-20 15:12 ` Jonathan Morton
2016-05-20 16:05 ` David Lang
2016-05-20 17:06 ` Jonathan Morton
2016-05-20 16:20 ` [Cake] [Codel] " Rick Jones
2016-05-20 16:35 ` Jonathan Morton
2016-05-20 17:01 ` Rick Jones
2016-05-20 17:07 ` Jonathan Morton
2016-05-20 17:21 ` Rick Jones
2016-05-20 17:26 ` David Lang
2016-05-20 17:33 ` Jonathan Morton
2016-05-20 14:09 ` [Cake] " Jonathan Morton
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/cake.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.1605200638530.1578@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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