From: Dave Taht <dave.taht@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] passing args to bpf programs
Date: Wed, 1 Aug 2018 09:36:32 -0700 [thread overview]
Message-ID: <CAA93jw6yZ3=Nrt6uRVp=c94TfXWt4q5bwaUM=eq1K4dONGgopQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4YyAfgyFX-6_HTMaCdhfsWVt=V3eQ5uUzH78WuunVLRw@mail.gmail.com>
A somewhat related goal would be to apply the codel algorithm via bpf.
We'd take advantage of hardware
multiqueue for the fq part, ensure a good timestamp always existed on
all ingress ports, check it on egress.
The one major loop in codel we could unroll to be a fixed unroll (and
just give up), and we're done there.
next prev parent reply other threads:[~2018-08-01 16:36 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 [this message]
2018-08-01 16:42 ` Jonathan Morton
2018-08-01 16:54 ` Dave Taht
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='CAA93jw6yZ3=Nrt6uRVp=c94TfXWt4q5bwaUM=eq1K4dONGgopQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@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