From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] AQM and PPP on Linux
Date: Tue, 28 Jul 2015 16:44:17 +0200 [thread overview]
Message-ID: <CAA93jw6XbCiA6Apew-qxdmt1fzAo2kX2dw2Uf_W-idL7bX5C1w@mail.gmail.com> (raw)
In-Reply-To: <87a8ugqvid.wl-jch@pps.univ-paris-diderot.fr>
On Tue, Jul 28, 2015 at 3:09 PM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
> I'm currently away from home, and using a 3G modem for Internet access.
> I've found out that both NetworkManager and wvdial/pppd setup the
> interface to use pfifo_fast (with a qlen of a mere 3 packets!). Setting
> fq_codel manually appears to work fine, but needs to be redone every time
> the modem has a hiccup.
>
> Is that the expected behaviour? Shouldn't we be pushing patches somewhere
> to change the default?
1) The ppp driver was debloated by david woodhouse way back when.
However, the netusb-related drivers, and the 3g devices themselves,
contain oft-huge buffers that reduce the effectiveness of any aqm or
fq system, sometimes to immeasurability.
I would be very interested in flent benchmarks of your 3g device with
the 3 packet txqueue and with fq_codel, for the tcp_upload, rrul, and
rrul_be tests.
2) Most advanced qdiscs ignore txqueuelen entirely.
3) Usually you can add a script in /etc/network/ifpreup.d or ifup.d to
do extra stuff you want.
4) setting the default qdisc to be fq_codel in the sysctl works on
most dynamically created devices, but does not work on devices that
come up at boot time before the sysctls have a chance to run and the
modprobes to complete. This is why fedora 22, for example, compiled in
fq_codel statically, rather than dynamically.
> -- Juliusz
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
next prev parent reply other threads:[~2015-07-28 14:44 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
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 [this message]
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=CAA93jw6XbCiA6Apew-qxdmt1fzAo2kX2dw2Uf_W-idL7bX5C1w@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jch@pps.univ-paris-diderot.fr \
/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