From: Sebastian Moeller <moeller0@gmx.de>
To: Jonathan Morton <chromatix99@gmail.com>,dpreed@reed.com
Cc: cake@lists.bufferbloat.net, "Klatsky,
Carl" <carl_klatsky@cable.comcast.com>,
Simon Barber <simon@superduper.net>,
cerowrt-devel@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] heisenbug: dslreports 16 flow test vs cablemodems
Date: Mon, 18 May 2015 19:03:09 +0200 [thread overview]
Message-ID: <8E2F7EDC-3356-451A-8EFA-023A1EED4F0F@gmx.de> (raw)
In-Reply-To: <EF8F2CD0-AF82-4118-B3DE-18ADE3D93694@gmail.com>
Hi Jonathan,
On May 18, 2015 5:40:30 PM GMT+02:00, Jonathan Morton <chromatix99@gmail.com> wrote:
>
[...]
>
>Adding Diffserv and recommending that LEDBAT applications use the
>“background” traffic class (CS1 DSCP) solves this problem more
>elegantly. The share of bandwidth used by BitTorrent (say) is then
>independent of the number of flows it uses, and it also makes sense to
>configure FQ for ideal flow isolation rather than for mitigation.
I wonder, for this to work well wouldn't we need to allow/honor at least CS1 marks on ingress? I remember there was some discussion about mislabeled traffic on ingress (Comcast I believe), do you see an easy way around that issue?
Best Regards
Sebastian
>
> - Jonathan Morton
>
>_______________________________________________
>Cerowrt-devel mailing list
>Cerowrt-devel@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2015-05-18 17:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 19:13 [Cerowrt-devel] " Dave Taht
2015-05-15 2:48 ` Greg White
2015-05-15 4:44 ` Aaron Wood
2015-05-15 8:18 ` [Cerowrt-devel] [Bloat] " Eggert, Lars
2015-05-15 8:55 ` Sebastian Moeller
2015-05-15 11:10 ` [Cerowrt-devel] [Cake] " Alan Jenkins
2015-05-15 11:27 ` [Cerowrt-devel] " Bill Ver Steeg (versteb)
2015-05-15 12:19 ` Jonathan Morton
2015-05-15 12:44 ` Eggert, Lars
2015-05-15 13:09 ` Bill Ver Steeg (versteb)
2015-05-15 13:35 ` Jim Gettys
2015-05-15 14:36 ` Simon Barber
2015-05-18 3:30 ` dpreed
2015-05-18 5:06 ` Simon Barber
2015-05-18 9:06 ` Bill Ver Steeg (versteb)
2015-05-18 11:42 ` Eggert, Lars
2015-05-18 11:57 ` luca.muscariello
2015-05-18 12:30 ` Simon Barber
2015-05-18 15:03 ` Jonathan Morton
2015-05-18 15:09 ` dpreed
2015-05-18 15:32 ` Simon Barber
2015-05-18 17:21 ` [Cerowrt-devel] [Cake] " Dave Taht
2015-05-18 15:40 ` [Cerowrt-devel] " Jonathan Morton
2015-05-18 17:03 ` Sebastian Moeller [this message]
2015-05-18 17:17 ` Jonathan Morton
2015-05-18 18:14 ` Sebastian Moeller
2015-05-18 18:37 ` Dave Taht
2015-05-19 16:25 ` [Cerowrt-devel] [Cake] " Sebastian Moeller
2015-05-15 16:59 ` [Cerowrt-devel] " Dave Taht
2015-05-15 17:47 ` [Cerowrt-devel] " Dave Taht
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8E2F7EDC-3356-451A-8EFA-023A1EED4F0F@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=carl_klatsky@cable.comcast.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dpreed@reed.com \
--cc=simon@superduper.net \
/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