From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave@taht.net>
Cc: "Bjørn Ivar Teigen" <bjorn@domos.no>,
"Cake List" <cake@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Cake] [Make-wifi-fast] Cake in mac80211
Date: Wed, 5 Feb 2020 18:22:28 +0200 [thread overview]
Message-ID: <CC59BA6E-9C87-437E-A982-18D814EC2415@gmail.com> (raw)
In-Reply-To: <87v9oluih6.fsf@taht.net>
> On 5 Feb, 2020, at 6:06 pm, Dave Taht <dave@taht.net> wrote:
>
>> D) "cobalt" is proving out better in several respects than pure
>> codel,
>> and folding in some of that makes sense, except I don't know which
>> things are the most valuable considering wifi's other problems
>>
>> Reading paper now. Thanks for the pointer.
>
> I tend to think out that fq_codel is "good enough" in most
> circumstances. The edge cases that cake handles better are a matter of a
> few percentage points, vs orders of magnitude that we get with fq_codel
> alone vs a vs a FIFO, and my focus of late has been to make things that
> ate less cpu or were better offloadable than networked better. Others differ.
I think COBALT might be worth putting in, as it should have essentially no net cost and does behave a little better than stock Codel. It's better at handling unresponsive traffic, in particular.
- Jonathan Morton
next prev parent reply other threads:[~2020-02-05 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 15:20 [Cake] " Bjørn Ivar Teigen
2020-02-04 15:25 ` Jonathan Morton
2020-02-04 17:07 ` Dave Taht
2020-02-05 11:53 ` Bjørn Ivar Teigen
2020-02-05 16:06 ` Dave Taht
2020-02-05 16:16 ` [Cake] [Make-wifi-fast] " Toke Høiland-Jørgensen
2020-02-05 16:22 ` Jonathan Morton [this message]
2020-02-05 19:46 ` Dave Taht
2020-02-05 20:19 ` [Cake] " 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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CC59BA6E-9C87-437E-A982-18D814EC2415@gmail.com \
--to=chromatix99@gmail.com \
--cc=bjorn@domos.no \
--cc=cake@lists.bufferbloat.net \
--cc=dave@taht.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