From: Stephen Hemminger <stephen@networkplumber.org>
To: madhukar mythri <madhukar.mythri@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: Failed to load eBPF byte-code on TAP device
Date: Wed, 15 Nov 2023 07:19:23 -0800 [thread overview]
Message-ID: <20231115071923.6c550190@hermes.local> (raw)
In-Reply-To: <CAAUNki2G0ELck950FLq=w-YZsKSpVv21CAu_huhWqAsQBgaU=Q@mail.gmail.com>
On Wed, 15 Nov 2023 15:38:55 +0530
madhukar mythri <madhukar.mythri@gmail.com> 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?
next prev parent reply other threads:[~2023-11-15 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 10:08 madhukar mythri
2023-11-15 15:19 ` Stephen Hemminger [this message]
2023-11-16 8:11 ` madhukar mythri
2023-11-16 18:39 ` 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=20231115071923.6c550190@hermes.local \
--to=stephen@networkplumber.org \
--cc=madhukar.mythri@gmail.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).