General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>, Pete Heist <pete@heistp.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] fq_codel on macosx
Date: Sun, 09 Sep 2018 20:49:05 +0200	[thread overview]
Message-ID: <87va7ebj6m.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw7zqfzxsZLN+7a9V2D+O_FPv1UEUxO0CatdFRKJLx+veA@mail.gmail.com>

Dave Taht <dave.taht@gmail.com> writes:

> On Sat, Sep 8, 2018 at 2:17 PM Pete Heist <pete@heistp.net> wrote:
>>
>>
>> On Sep 8, 2018, at 5:24 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> On Sat, Sep 8, 2018 at 8:12 AM Sebastian Moeller <moeller0@gmx.de> wrote:
>>
>>
>> Hi Dave,
>>
>> Jason Woringen just told me that macosx seems to include fq_codel now as well as some involved priority queues that I can not make much sense of. It might simply have inherited this from its freebsd underpinnings...
>>
>>
>> Wow. I had no idea. I know that they enabled tcp ecn universally last
>> year... but not fq_codel!! Holy cow!
>>
>>
>> Woah is right. It’s not in OS/X 10.11, but I also see it in 10.13, so it was either added in 10.12 or 10.13.
>>
>> fq_codel: good enough for Apple, but not systemd. :)
>>
>
> Well I should probably write more on that subject than I already have.

Erm, fq_codel has been the default in systemd for quite a while now?

-Toke

  reply	other threads:[~2018-09-09 18:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-08 15:12 Sebastian Moeller
2018-09-08 15:24 ` Dave Taht
2018-09-08 15:35   ` Sebastian Moeller
2018-09-08 15:54   ` Dave Taht
2018-09-08 21:17   ` Pete Heist
2018-09-08 21:58     ` Dave Taht
2018-09-09 18:49       ` Toke Høiland-Jørgensen [this message]
2018-09-09 18:51         ` Jonathan Morton
2018-09-09 20:38           ` 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=87va7ebj6m.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=pete@heistp.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