From: Kouilakonda Anudattu <kouilakonda.anudattu@oracle.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: RE: net/tap: eBPF failed to load BPF section and failed to create flows for TAP device
Date: Mon, 9 Oct 2023 07:04:49 +0000 [thread overview]
Message-ID: <CY4PR1001MB2056E873FC1C2D30FB7F3147FDCEA@CY4PR1001MB2056.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CY4PR1001MB2056E539EB42048C4CE7EDFAFDCEA@CY4PR1001MB2056.namprd10.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
I'm adding some additional details to provide more context. I'm encountering this issue on Azure/Hyper-V platform with the existing DPDK-22.11.1 tap_bpf_insns.h byte-code.
Regards,
Anudattu.
From: Kouilakonda Anudattu <kouilakonda.anudattu@oracle.com>
Sent: Monday, October 9, 2023 9:48 AM
To: users@dpdk.org
Subject: [External] : net/tap: eBPF failed to load BPF section and failed to create flows for TAP device
Hi All,
With the latest Oracle EL9 with DPDK 22.11.1 version, I modified the RSS eBPF C program and generated the structure of a C array in the 'tap_bpf_insns.h' file.
This array is in eBPF bytecode instructions format. However, even with new bytecode eBPF failed to load 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."
Currently we are using below kernel:
5.15.0 #9 SMP PREEMPT
x86_64 GNU/Linux
How to resolve these errors ?
Regards,
Anudattu
[-- Attachment #2: Type: text/html, Size: 4254 bytes --]
next prev parent reply other threads:[~2023-10-09 7:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 4:18 Kouilakonda Anudattu
2023-10-09 7:04 ` Kouilakonda Anudattu [this message]
2023-10-09 15:14 ` Stephen Hemminger
2023-10-09 15:15 ` 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=CY4PR1001MB2056E873FC1C2D30FB7F3147FDCEA@CY4PR1001MB2056.namprd10.prod.outlook.com \
--to=kouilakonda.anudattu@oracle.com \
--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).