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 49E424333A for ; Wed, 15 Nov 2023 16:19:28 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BF8D5402B0; Wed, 15 Nov 2023 16:19:27 +0100 (CET) Received: from mail-pl1-f176.google.com (mail-pl1-f176.google.com [209.85.214.176]) by mails.dpdk.org (Postfix) with ESMTP id 616A44027D for ; Wed, 15 Nov 2023 16:19:26 +0100 (CET) Received: by mail-pl1-f176.google.com with SMTP id d9443c01a7336-1cc330e8f58so52154595ad.3 for ; Wed, 15 Nov 2023 07:19:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1700061565; x=1700666365; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=CV5RD5MMzBLObs0S9+EwHrwtfkjEzUnyPLJB6gBcZII=; b=0XT/xXiR01h77Mnoz5GYElgGGruwLsrHF7MX07PCz71yUQk4Z7mPGA6qL9ETR6H4b1 lys+5JpCiVgGFVjBfDWFol57dYUxCYHuwFquGncDn6UR/nnm8wsWnpPLTw1wxiOJArFd sZh4Kk16YpY7g230foA5qcjYsXS18mPprUvJZaRk5qO8oyac6gTexSNqAalRkL/I27F/ TEdVQBBXejA1+5F93Cvq0s5EMw27ZiqVaUs3TXIgDMx8yNF5WJ3mq101OBYMsePzTSFY EY58RQ3RL1lfzt5W1xC5XAUw8RKZoYHKe3W0H8xUmxQnKE9zGtyr3KxDgNV/J/eOVe0L CJhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700061565; x=1700666365; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=CV5RD5MMzBLObs0S9+EwHrwtfkjEzUnyPLJB6gBcZII=; b=J7D0netqoXq0RSOdbrdoEw+ooigRNF6KESw6vHJCpgKazvoHZwYRHyYYEUtsw81XE9 Y5TaDCYOgQy8QFYJKFlID6jNcIqqkc96oNJDFj9qEqvUGs4rHkVmukbzbMmjm4nACnSb ruUR2lnKI8SwGm96k9V/ye6r+B7SvVXBVf6H/W81OqiwCjkTY994CP+74IWKM6e+bjlj wkmfPEQ3zBHO22S9/sRYh8EvFGJyKHlBqOPmpBbSEF6NPhqtxK/CU0ni5CrzN9s/70PE tzFm8hpHpOPnUB39WuMuYzCNKFTU/ma8O+qUJaULLKF0rDuuZ+zk/zDPQSOt+GJb/O5V MGVA== X-Gm-Message-State: AOJu0YwfwGVpul8F1hVrYvUbFn3iKLpy8DZvwJoN2klbT+IHh3H8lgyf ANPKzFb9d0u/k0mTwc84WGAROlCBE8Od7rZXjTh62g== X-Google-Smtp-Source: AGHT+IFHENkImRz9yNFwHlyC6auEoZKxh6cBsHoBmuxKHFU0DPGtyxHdahh0UFTvRfEVdLd/IrmE+g== X-Received: by 2002:a17:903:110e:b0:1cc:4468:f1cf with SMTP id n14-20020a170903110e00b001cc4468f1cfmr6078103plh.3.1700061565374; Wed, 15 Nov 2023 07:19:25 -0800 (PST) Received: from hermes.local (204-195-123-141.wavecable.com. [204.195.123.141]) by smtp.gmail.com with ESMTPSA id ij26-20020a170902ab5a00b001c32fd9e412sm7737248plb.58.2023.11.15.07.19.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 15 Nov 2023 07:19:25 -0800 (PST) Date: Wed, 15 Nov 2023 07:19:23 -0800 From: Stephen Hemminger To: madhukar mythri Cc: users Subject: Re: Failed to load eBPF byte-code on TAP device Message-ID: <20231115071923.6c550190@hermes.local> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 On Wed, 15 Nov 2023 15:38:55 +0530 madhukar mythri wrote: > Hi all, > > On the RHEL9.2 with DPDK 22.11.1 version, DPDK primary application failed > to add RSS flow on TAP sub-device, when loading the TAP BPF byte-code > instructions. > > This "struct bpf_insn l3_l4_hash_insns[]" array(from file: > drivers/net/tap/tap_bpf_insns.h) is in eBPF bytecode instructions format, > this eBPF failed to load on TAP PMD with the following error: > > ===================== > rss_add_actions(): Failed to load BPF section 'l3_l4' (7): Argument list > too long. > net_failsafe: Failed to create a flow on sub_device 1." > ===================== > On Kernel-version: 5.15.0 #9 SMP PREEMPT > Arch: x86_64 GNU/Linux > > When added some debug logs on Kernel BPF verifier code, we could see that > instruction processed were reached to 1 Million. > But, the Byte code has only 1698 instructions only. Why the Kernel BPF > verifier is processing beyond 1,698 instructions ? > > The same byte-code(with DPDK-22.11.1) worked well with RHEL8.x and not > working in RHEL-9.x version. > > Does anybody faced such issues ? > Please let me know how to debug such issues on Byte-code. > > Thanks, > Madhukar. Is there anything in the kernel log?