From: "Toke Høiland-Jørgensen" <toke@kernel.org>
To: Anton Protopopov <aspsk@isovalent.com>,
lsf-pc@lists.linux-foundation.org, bpf <bpf@vger.kernel.org>
Subject: Re: [LSF/MM/BPF TOPIC] XDP Multi-Attach
Date: Mon, 27 Feb 2023 15:08:51 +0100 [thread overview]
Message-ID: <87bklfjj4c.fsf@toke.dk> (raw)
In-Reply-To: <CAPyNcWeAc6qPnxGQVTh1D1WEhLNocDt-=OTOGsXi0D9=Sj6RYg@mail.gmail.com>
Anton Protopopov <aspsk@isovalent.com> writes:
> When the tc BPF links patch [1] will be merged, a similar concept for XDP
> links may be used to allow multiple users to live next to each other. The
> purpose of this topic is to discuss design and how to better sync with libxdp.
>
> [1] https://lpc.events/event/16/contributions/1353/
I'm all for doing this (and I agree we should sync with libxdp :)), but
I'm not sure what we'd discuss at the summit? Should be pretty
straight-forward to just implement the same thing between TC and XDP? :)
-Toke
prev parent reply other threads:[~2023-02-27 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 9:02 [LSF/MM/BPF TOPIC] XDP Multi-Attach Anton Protopopov
2023-02-27 14:08 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bklfjj4c.fsf@toke.dk \
--to=toke@kernel.org \
--cc=aspsk@isovalent.com \
--cc=bpf@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
/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