Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>, Jonathan Morton <chromatix99@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] codel in ebpf?
Date: Thu, 02 Aug 2018 22:04:27 +0200	[thread overview]
Message-ID: <87ftzwy1pw.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw5RvZSj3JBE9pS=sE29vSzNP9zonQzLBrE07XA3QAq7EQ@mail.gmail.com>

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

> On Wed, Aug 1, 2018 at 10:25 AM Dave Taht <dave.taht@gmail.com> wrote:
>>
>> I wonder if ebpf has opcode space for an invsqrt?
>
> bpf_ktime_get_ns() exists...
>
> one thing that I don't know if bpf can do is read/write the
> skb->tstamp field. The plan would be to rigorously write it (if not
> supplied by hw) on all ingress ports and check it on all egress ports.

An XDP eBPF program (run at earliest possible ingress) has access to a
buffer of arbitrary data that is attached to the skb and that can be
read from later eBPF programs. So it doesn't need to muck with
skb->tstamp for this.

> That said, every time I've tried to do something in ebpf I hit a
> limitation I'd not thunk of yet.

Yeah, the whole XDP/eBPF system is somewhat of a work in progress ;)

> For example, where can you attach the egress filter?
>
> My thought would be to use a bfifo > bpf -> bql, but from what little
> I understand, it's bpf -> bfifo -> bql

Yeah, it is. Don't think there's a way to run an eBPF program after the
qdisc...

-Toke

  reply	other threads:[~2018-08-02 20:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-01 16:22 [Cake] passing args to bpf programs 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
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 [this message]
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=87ftzwy1pw.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=dave.taht@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