From: Alexandre Ferrieux <alexandre.ferrieux@gmail.com>
To: Kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: [RFC] Netkit cannot be an XDP_REDIRECT target ?
Date: Mon, 9 Jun 2025 00:56:13 +0200 [thread overview]
Message-ID: <9be97119-e1b9-4e61-a0d4-6ad7419c9861@orange.com> (raw)
Hi,
When looking at netkit papers, one tends to view it as a kind of veth, rewritten
for efficiency. However, the feature flags of a netkit never contain
NETDEV_XDP_ACT_NDO_XMIT. In other words, it can never be an XDP_REDIRECT target.
By contrast, xdp-redirecting to a veth works.
This means that netkit is far from being a "drop-in" replacement for veth "just
faster". It rather sounds like unfinished work.
What am I missing here ? Is there another method to pass frames from the XDP RX
hook of an interface to a netkit's ring ? Is netkit "here to stay", being
actively worked on ? Or is it a single-purpose experiment that will never try to
reach veth's functional coverage ?
Thanks for any clarifications.
-Alex
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
reply other threads:[~2025-06-08 22:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9be97119-e1b9-4e61-a0d4-6ad7419c9861@orange.com \
--to=alexandre.ferrieux@gmail.com \
--cc=kernelnewbies@kernelnewbies.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