From: Stephen Hemminger <stephen@networkplumber.org>
To: Alessio Igor Bogani <alessio.bogani@elettra.eu>
Cc: users@dpdk.org
Subject: Re: dpdk-testpmd on XDP
Date: Tue, 19 Mar 2024 09:07:47 -0700 [thread overview]
Message-ID: <20240319090747.16a3b28d@hermes.local> (raw)
In-Reply-To: <CAPk1OjFMnpprktN=rYCweL5BUOPgyM38exXK-BC8VbTJmbwcUw@mail.gmail.com>
On Tue, 19 Mar 2024 11:48:53 +0100
Alessio Igor Bogani <alessio.bogani@elettra.eu> wrote:
> The only suspicious part in the output of the dpdk-testpmd utility is:
> [...]
> libxdp: XDP flag not supported by libxdp.
> libbpf: prog 'xdp_dispatcher': BPF program load failed: Invalid argument
> libbpf: prog 'xdp_dispatcher': -- BEGIN PROG LOAD LOG --
> Validating prog0() func#1...
> btf_vmlinux is malformed
> Arg#0 type PTR in prog0() is not supported yet.
> processed 0 insns (limit 1000000) max_states_per_insn 0 total_states 0
> peak_states 0 mark_read 0
> -- END PROG LOAD LOG --
> libbpf: failed to load program 'xdp_dispatcher'
> libbpf: failed to load object 'xdp-dispatcher.o'
> libxdp: Failed to load dispatcher: Invalid argument
> libxdp: Falling back to loading single prog without dispatcher
> [...]
What distribution and kernel version?
BPF/XDP has changed a lot over last couple of years and not maintained
compatibility. If you are building your own kernel, likely need to build
the xdp library as well. If getting from a distro (Fedora, Ubuntu, Debian, etc)
then make sure that xdp and kernel match.
next prev parent reply other threads:[~2024-03-19 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 10:48 Alessio Igor Bogani
2024-03-19 16:07 ` Stephen Hemminger [this message]
2024-03-20 7:22 ` Alessio Igor Bogani
2024-03-20 16:24 ` Stephen Hemminger
2024-03-22 17:57 ` Alessio Igor Bogani
2024-03-22 18:13 ` Alessio Igor Bogani
2024-03-22 23:32 ` Stephen Hemminger
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=20240319090747.16a3b28d@hermes.local \
--to=stephen@networkplumber.org \
--cc=alessio.bogani@elettra.eu \
--cc=users@dpdk.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;
as well as URLs for NNTP newsgroup(s).