From: Juliusz Chroboczek <jch@irif.fr>
To: Dave Taht <dave.taht@gmail.com>
Cc: babel-users@lists.alioth.debian.org,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
ecn-sane@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] [Babel-users] reducing delays in wifi mcast queues
Date: Wed, 19 Sep 2018 02:43:20 +0200 [thread overview]
Message-ID: <87zhweb9lj.wl-jch@irif.fr> (raw)
In-Reply-To: <CAA93jw488M1gVpvA5wg63Fx=OZMEabwHFbU-PsWkwQdb1VfXEA@mail.gmail.com>
>> Interesting. AFAIK, ECN is only considered by AQM queues, so this implies
>> there's a queue in the way that's dropping Babel packets.
> There's fq_codel on every queue, which does FQ, and codel assumes
> everything is at least moderately TCP friendly (and/or reasonably
> responsive to ecn marks)
Jonathan seems to agree with you.
Were your tests run with more than 60 installed routes or so?
>> Or perhaps, if we know which queue that is,
>> we could modify Babel's packet scheduling to be more AQM friendly?
> How would you describe babel's packet schedulig now?
The main flaw is that it sends periodic updates as a burst of back-to-back
full-size packets. That could trigger Codel if you had more than 60
routes or so.
> So dumping packets in there at a rate no more than 20ms each (short term
> burst of 100ms) - relative to whatever bandwidth can be achieved vs the
> other flows.
Right. Guilty as charged.
-- Juliusz
next prev parent reply other threads:[~2018-09-19 0:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 4:15 [Make-wifi-fast] " Dave Taht
2018-09-18 23:19 ` [Make-wifi-fast] [Babel-users] " Juliusz Chroboczek
2018-09-18 23:31 ` Dave Taht
2018-09-19 0:04 ` Juliusz Chroboczek
2018-09-19 0:07 ` Jonathan Morton
2018-09-19 0:32 ` Dave Taht
2018-09-19 0:43 ` Juliusz Chroboczek [this message]
2018-09-19 0:53 ` Dave Taht
2018-09-19 6:05 ` 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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhweb9lj.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=babel-users@lists.alioth.debian.org \
--cc=dave.taht@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.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