From: Alexandre Cassen <acassen@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>,
"team lnx" <teamlnxi8@gmail.com>,
xdp-newbies@vger.kernel.org
Subject: Re: XDP packet queueing and scheduling capabilities
Date: Tue, 13 Feb 2024 15:33:11 +0100 [thread overview]
Message-ID: <d9da33bf-ecef-4470-9a8d-1b638a5ffa24@gmail.com> (raw)
In-Reply-To: <87le7ofre3.fsf@toke.dk>
Hi Toke,
here is a target with lot of interest for it : www.gtp-guard.org
When dealing with mobile network data-plane, at some point you have
ordering issues and shaping needs, so queuing is truly needed.
Alternatively ones can implement PIFO or others built on AF_XDP but if
dedicated bpf map covers the use-case, would be nice.
Watching at your LPC 2022 presentation, at the end, discussions where
made around using existing Qdisc kernel framework and find
a way to share the path between XDP and netstack. Is it a target for
adding PIFO, or more generally getting queuing support for XDP ?
regs,
Alexandre
On 13/02/2024 14:03, Toke Høiland-Jørgensen wrote:
> team lnx <teamlnxi8@gmail.com> writes:
>
>> Hello everyone,
>>
>> https://lwn.net/Articles/901046/
>> would this be resumed any time soon this year ?
>
> The latest version of those patches are here:
> https://git.kernel.org/pub/scm/linux/kernel/git/toke/linux.git/log/?h=xdp-queueing-08
>
> They are a bit rough around the edges, and there are some missing pieces
> still; I'm working on getting a userspace/BPF implementation to the
> point where those can be filled in. After that, and some thorough
> testing, it should be possible to post another revision.
>
> What's your interest in this? I.e., what do you want to use them for?
> Would be useful to know so I can make sure this is covered :)
>
> -Toke
>
>
next prev parent reply other threads:[~2024-02-13 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 4:27 XDP packet queueing and scheduling capabilities team lnx
2024-02-13 13:03 ` Toke Høiland-Jørgensen
2024-02-13 14:33 ` Alexandre Cassen [this message]
2024-02-13 15:01 ` Dave Taht
2024-02-13 16:07 ` Toke Høiland-Jørgensen
2024-02-13 17:31 ` Alexandre Cassen
2024-02-14 13:21 ` Toke Høiland-Jørgensen
2024-02-14 13:27 ` Marcus Wichelmann
2024-02-14 16:21 ` Toke Høiland-Jørgensen
2024-02-15 19:10 ` team lnx
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=d9da33bf-ecef-4470-9a8d-1b638a5ffa24@gmail.com \
--to=acassen@gmail.com \
--cc=teamlnxi8@gmail.com \
--cc=toke@redhat.com \
--cc=xdp-newbies@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.