[Bloat] Fwd: [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking

[Jonas Mårtensson]

Speaking about systemd defaults, they just enabled ecn for outgoing
connections:

https://github.com/systemd/systemd/pull/9143

/Jonas

On Mon, Jun 4, 2018 at 7:08 PM, Dave Taht <dave.taht at gmail.com> wrote:

> On Mon, Jun 4, 2018 at 6:16 AM, Jonas Mårtensson
> <martensson.jonas at gmail.com> wrote:
> >
> >
> > On Mon, Jun 4, 2018 at 1:28 PM, Bless, Roland (TM) <roland.bless at kit.edu
> >
> > wrote:
> >>
> >> Hi,
> >>
> >> Am 24.05.2018 um 17:38 schrieb Jan Ceuleers:
> >> > Took 3 years after Dave approached them, but Ubuntu is finally
> adopting
> >> > fq_codel as the default qdisc.
> >>
> >> Yes, if the Linux kernel is forwarding packets it makes a lot of sense,
> >> but I don't understand why it make sense for ordinary end-systems.
> >> Didn't Byte Queue Limits (BQL) suffice? Just curious...
> >
> >
> > Actually, for a long time now the codel wiki has recommended using sch_fq
> > instead of fq_codel for servers.
>
> That recommendation predates the tcp pacing change you note below.
>
> I'm pretty convinced fq_codel is now the best all around "default"
> qdisc, and we should rework our recomendation.
>
> > It seems Ubuntu defaulting to fq_codel is a result of using systemd which
> > adopted it as default almost 4 years ago. There was a request to change
> the
> > default in systemd from fq_codel to sch_fq in order to support pacing but
> > the issue was closed when tcp internal pacing was introduced in linux
> 4.13:
> >
> > https://github.com/systemd/systemd/issues/5090
> >
> > /Jonas
> >
> > _______________________________________________
> > Bloat mailing list
> > Bloat at lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/bloat
> >
>
>
>
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-669-226-2619
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/bloat/attachments/20180604/15e28253/attachment-0002.html>