General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
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 15:33:18 +0200	[thread overview]
Message-ID: <87r3nstnj5.fsf@toke.dk> (raw)
In-Reply-To: <87a8ugqvid.wl-jch@pps.univ-paris-diderot.fr> (Juliusz Chroboczek's message of "Tue, 28 Jul 2015 15:09:14 +0200")

Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> writes:

> 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.

I don't think NetworkManager does anything to set qdiscs. The kernel
simple sets pfifo_fast if not told otherwise (but see below).

> Is that the expected behaviour? Shouldn't we be pushing patches
> somewhere to change the default?

What distro are you on?

There's a sysctl to set the default qdisc: net.core.default_qdisc. Set
this to fq_codel and you should be good to go. This is becoming the
default in more and more distros (currently at least Arch and Fedora;
and OpenWrt has been patching out pfifo_fast entirely for a while).

There's a bug for Ubuntu here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436945 -- feel
free to bug them :)

-Toke

  reply	other threads:[~2015-07-28 13:33 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 [this message]
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
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=87r3nstnj5.fsf@toke.dk \
    --to=toke@toke.dk \
    --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