From: David Lang <david@lang.hm>
To: Simon Barber <simon@superduper.net>
Cc: bloat <bloat@lists.bufferbloat.net>,
Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [Bloat] AQM and PPP on Linux
Date: Wed, 29 Jul 2015 00:19:42 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1507290019040.1813@nftneq.ynat.uz> (raw)
In-Reply-To: <14ed5013130.27f7.e972a4f4d859b00521b2b659602cb2f9@superduper.net>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1322 bytes --]
If you have high RTT on loopback or virtual interfaces, Codel is going to be the
least of your problems ;-)
David Lang
On Tue, 28 Jul 2015, Simon Barber wrote:
> The main danger is the negative effects on performance of using Codel. You
> may experience low throughput on high RTT links.
>
> Simon
>
> Sent with AquaMail for Android
> http://www.aqua-mail.com
>
>
> On July 28, 2015 7:06:22 AM Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
>> Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> writes:
>>
>> >> What distro are you on?
>> >
>> > Debian. (One machine stable, one testing.)
>>
>> Right. Don't know if there's already an effort to convince the Debian
>> devs to switch the default...
>>
>> >> Set this to fq_codel and you should be good to go.
>> >
>> > Is that safe? I'm thinking lo and virtual interfaces.
>>
>> Why wouldn't it be? The lo interface doesn't have a queue at all AFAIK.
>> And if you have congestion at your virtual interfaces wouldn't you want
>> it de-bloated? :)
>>
>> -Toke
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
next prev parent reply other threads:[~2015-07-29 7:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 13:09 Juliusz Chroboczek
2015-07-28 13:33 ` Toke Høiland-Jørgensen
2015-07-28 13:50 ` Juliusz Chroboczek
2015-07-28 14:05 ` Toke Høiland-Jørgensen
2015-07-28 14:11 ` Simon Barber
2015-07-28 14:21 ` Eric Dumazet
2015-07-28 14:31 ` Simon Barber
2015-07-28 14:43 ` Jonathan Morton
2015-07-28 14:49 ` Eric Dumazet
2015-07-28 14:55 ` Eric Dumazet
2015-07-28 16:02 ` Alan Jenkins
2015-07-28 16:22 ` Sebastian Moeller
2015-07-28 17:11 ` Michael Welzl
2015-07-29 7:19 ` David Lang [this message]
2015-07-28 19:20 ` Juliusz Chroboczek
2015-07-28 19:29 ` Alan Jenkins
2015-07-28 14:18 ` Eric Dumazet
2015-07-28 14:44 ` Dave Taht
2015-07-28 14:52 ` Eric Dumazet
2015-07-28 19:24 ` Juliusz Chroboczek
2015-07-28 19:31 ` Bill Ver Steeg (versteb)
2015-07-28 20:10 ` Alan Jenkins
2015-07-28 20:45 ` Alan Jenkins
2015-07-29 13:15 ` Stefan Alfredsson
2015-07-29 13:41 ` 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/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.1507290019040.1813@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=jch@pps.univ-paris-diderot.fr \
--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