From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id D5E9D43D00 for ; Wed, 20 Mar 2024 08:23:17 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 57855402A2; Wed, 20 Mar 2024 08:23:17 +0100 (CET) Received: from eggs.elettra.eu (eggs.elettra.trieste.it [140.105.207.10]) by mails.dpdk.org (Postfix) with ESMTP id 26742402A2 for ; Wed, 20 Mar 2024 08:23:16 +0100 (CET) X-Envelope-From: Received: from zmp.elettra.eu (zmp.elettra.trieste.it [140.105.206.204]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by eggs.elettra.eu (Postfix) with ESMTPS id 4V00PJ5JxDzBrLf for ; Wed, 20 Mar 2024 08:20:52 +0100 (CET) Received: from zmp.elettra.eu (localhost [127.0.0.1]) by zmp.elettra.eu (Postfix) with ESMTPS id B97FF140FEA2 for ; Wed, 20 Mar 2024 08:22:44 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by zmp.elettra.eu (Postfix) with ESMTP id A911C140FEAE for ; Wed, 20 Mar 2024 08:22:44 +0100 (CET) X-Virus-Scanned: amavis at zmp.elettra.eu Received: from zmp.elettra.eu ([127.0.0.1]) by localhost (zmp.elettra.eu [127.0.0.1]) (amavis, port 10026) with ESMTP id xXbIBISmqlws for ; Wed, 20 Mar 2024 08:22:44 +0100 (CET) Received: from mail-pf1-f181.google.com (mail-pf1-f181.google.com [209.85.210.181]) by zmp.elettra.eu (Postfix) with ESMTPSA id 8F0E8140FEA2 for ; Wed, 20 Mar 2024 08:22:44 +0100 (CET) Received: by mail-pf1-f181.google.com with SMTP id d2e1a72fcca58-6e6082eab17so5584488b3a.1 for ; Wed, 20 Mar 2024 00:22:44 -0700 (PDT) X-Gm-Message-State: AOJu0Yxv+NsShKdwoBSFjXeVuZ5/iKQHueuzQWmA8ZAdqECyNu8mZ9pp waHgodYcxmU0oL2Nvd1QWC0+cvn4JLf4Il+3/ymubrj1bRe8CXa3BFK3YbSGSK/EUgHYTGKKTwL VFRUGINUttSJ84Z87WGqT0QCf+HY= X-Google-Smtp-Source: AGHT+IGV/rc+wc+ZiHozZ7pj7K2X0H89Avp1/zCzYA8tYBLSomEo08vslOZVSWCNHsuxMxeRvYRhKvQMliPzQ2dCSw0= X-Received: by 2002:a05:6a21:a586:b0:1a3:6a4c:80a9 with SMTP id gd6-20020a056a21a58600b001a36a4c80a9mr8023672pzc.1.1710919361818; Wed, 20 Mar 2024 00:22:41 -0700 (PDT) MIME-Version: 1.0 References: <20240319090747.16a3b28d@hermes.local> In-Reply-To: <20240319090747.16a3b28d@hermes.local> From: Alessio Igor Bogani Date: Wed, 20 Mar 2024 08:22:05 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: dpdk-testpmd on XDP To: stephen@networkplumber.org Cc: users@dpdk.org, Anuj Mittal Content-Type: text/plain; charset="UTF-8" X-elettra-Libra-ESVA-Information: Please contact elettra for more information X-elettra-Libra-ESVA-ID: 4V00PJ5JxDzBrLf X-elettra-Libra-ESVA: No virus found X-elettra-Libra-ESVA-From: alessio.bogani@elettra.eu X-elettra-Libra-ESVA-Watermark: 1711524052.88704@B8OYOEHKIIncMli0dNgLyA X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Stephen, Thanks for your reply! On Tue, 19 Mar 2024 at 17:07, Stephen Hemminger wrote: > > On Tue, 19 Mar 2024 11:48:53 +0100 > Alessio Igor Bogani 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? Custom distribution (Yocto Kirkstone) using 5.10.184.All parts (kernel, DPDK, libbpf, xdp-tools) are built (cross-compiled) from source. > 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) Using libbpf 0.7.0 and libxdp 1.2.8, which are provided by meta-intel, it doesn't work. I tried the latest version libbpf 1.3.0 and libxdp 1.4.2 and unfortunately It still doesn't work The output changed a little: libbpf: prog 'xdp_dispatcher': failed to load: -22 libbpf: failed to load object 'xdp-dispatcher.o' libxdp: Failed to load dispatcher: Invalid argument libxdp: Falling back to loading single prog without dispatcher libbpf: elf: skipping unrecognized data section(7) xdp_metadata 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. > then make sure that xdp and kernel match. Where can I find that match table between xdp and kernel? Thanks a lot! Ciao, Alessio