From: "David P. Reed" <dpreed@deepplum.com>
To: "Frantisek Borsik" <frantisek.borsik@gmail.com>
Cc: "Cake List" <cake@lists.bufferbloat.net>,
codel@lists.bufferbloat.net,
"bloat" <bloat@lists.bufferbloat.net>,
"Jeremy Austin via Rpm" <rpm@lists.bufferbloat.net>
Subject: [Codel] Re: [Cake] XDP2 is here - from one and only Tom Herbert (almost to the date, 10 years after XDP was released)
Date: Tue, 9 Sep 2025 16:25:51 -0400 (EDT) [thread overview]
Message-ID: <1757449551.421420786@apps.rackspace.com> (raw)
In-Reply-To: <CAJUtOOhdVJCiRqhOTmdiPNmZEq9_dA+k=evLWX1UsB=ySHpf_A@mail.gmail.com>
Hi Frank -
I think it is interesting as a concept. A project I am advising has been using DPDK very effectively to get rid of the huge path and locking delays in the current Linux network stack. XDP2 could be supported in a ring3 (user) address space, achieving a similar result.
But I don't think XDP2 is going that direction - so it may be stuckinto the mess of kernel space networking. Adding eBPF only has made this more of a mess, by the way (and adding a new "compiler" that needs to be veriried as safe for the kernel).
I will be watching how this evolves.
David
On Tuesday, September 9, 2025 06:32, "Frantisek Borsik" <frantisek.borsik@gmail.com> said:
> Hello to all,
>
> Looks interesting:
> https://medium.com/@tom_84912/xdp2-this-changes-everything-at-least-for-ai-ml-infrastructure-850c1ba82771
>
>
> All the best,
>
> Frank
>
> Frantisek (Frank) Borsik
>
>
> *In loving memory of Dave Täht: *1965-2025
>
> https://libreqos.io/2025/04/01/in-loving-memory-of-dave/
>
>
> https://www.linkedin.com/in/frantisekborsik
>
> Signal, Telegram, WhatsApp: +421919416714
>
> iMessage, mobile: +420775230885
>
> Skype: casioa5302ca
>
> frantisek.borsik@gmail.com
> _______________________________________________
> Cake mailing list -- cake@lists.bufferbloat.net
> To unsubscribe send an email to cake-leave@lists.bufferbloat.net
>
next prev parent reply other threads:[~2025-09-09 20:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 10:32 [Codel] " Frantisek Borsik
2025-09-09 20:25 ` David P. Reed [this message]
2025-09-09 21:02 ` [Codel] Re: [Cake] " Frantisek Borsik
2025-09-09 21:36 ` [Codel] Re: [Cake] " Tom Herbert
2025-09-10 8:54 ` [Codel] Re: [Bloat] " BeckW
2025-09-10 13:59 ` Tom Herbert
2025-09-10 14:06 ` Tom Herbert
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1757449551.421420786@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=frantisek.borsik@gmail.com \
--cc=rpm@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