From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] passing args to bpf programs
Date: Wed, 1 Aug 2018 09:54:02 -0700 [thread overview]
Message-ID: <CAA93jw5M3VeL0Q3NeDg7YphrcTp7e=zrUF1H5YH4LHrLaWEC3w@mail.gmail.com> (raw)
In-Reply-To: <FD8357DC-5238-42AB-A8B5-9ADD4E4D6CC7@gmail.com>
the other thing I noticed while fiddling with bql and cake unshaped is
that bql, too, had gained the ability to limit rates at mbit
granularity, when I wasn't looking. I am not sure if additional
hardware support is required, but:
https://patchwork.ozlabs.org/patch/449002/
On Wed, Aug 1, 2018 at 9:42 AM Jonathan Morton <chromatix99@gmail.com> wrote:
>
> > On 1 Aug, 2018, at 7:36 pm, Dave Taht <dave.taht@gmail.com> wrote:
> >
> > The one major loop in codel we could unroll to be a fixed unroll (and
> > just give up), and we're done there.
>
> The COBALT version only has a loop in the recovery phase, and that mainly to handle long pauses immediately following heavy congestion. The idle and marking phases do not loop.
>
> - Jonathan Morton
>
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next prev parent reply other threads:[~2018-08-01 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 16:22 Dave Taht
2018-08-01 16:35 ` Stephen Hemminger
2018-08-01 16:36 ` Dave Taht
2018-08-01 16:42 ` Jonathan Morton
2018-08-01 16:54 ` Dave Taht [this message]
2018-08-01 17:25 ` Dave Taht
2018-08-01 19:20 ` [Cake] codel in ebpf? Dave Taht
2018-08-02 20:04 ` Toke Høiland-Jørgensen
2018-08-03 0:22 ` Dave Taht
2018-08-03 10:19 ` Toke Høiland-Jørgensen
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='CAA93jw5M3VeL0Q3NeDg7YphrcTp7e=zrUF1H5YH4LHrLaWEC3w@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
/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