From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Herbert Wolverson <herberticus@gmail.com>
Cc: libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] Fwd: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context
Date: Fri, 11 Nov 2022 15:22:40 +0100 [thread overview]
Message-ID: <87h6z5370v.fsf@toke.dk> (raw)
In-Reply-To: <CA+erpM627Sq2CxsnoPuxn71xbw3HOEO6FPZYWy5rst9BZ985OQ@mail.gmail.com>
Herbert Wolverson via LibreQoS <libreqos@lists.bufferbloat.net> writes:
> That looks like it could be very, very useful. There's more email thread
> there than I have time to read,
> I wonder if there's a way to chain the xdp metadata to secondary XDP
> programs (which would
> obviate a lot of the "doing everything repeatedly" problem when dissecting
> packets on the XDP
> side as well as when passing to the TC side of things).
Yeah, that is very much in scope; the metadata survives through multiple
XDP programs even today (with libxdp) :)
-Toke
prev parent reply other threads:[~2022-11-11 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221104032532.1615099-1-sdf@google.com>
[not found] ` <20221104032532.1615099-7-sdf@google.com>
2022-11-10 23:26 ` Dave Taht
2022-11-10 23:45 ` Toke Høiland-Jørgensen
2022-11-11 14:06 ` Herbert Wolverson
2022-11-11 14:22 ` Toke Høiland-Jørgensen [this message]
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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6z5370v.fsf@toke.dk \
--to=toke@redhat.com \
--cc=herberticus@gmail.com \
--cc=libreqos@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