From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: bugzilla@dpdk.org
Cc: dev@dpdk.org
Subject: Re: [DPDK Bug 1376] A BPF can no longer include header rte_mbuf_core.h
Date: Tue, 30 Jan 2024 11:07:42 -0800 [thread overview]
Message-ID: <20240130190742.GA18445@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <bug-1376-3@http.bugs.dpdk.org/>
On Tue, Jan 30, 2024 at 03:42:05PM +0000, bugzilla@dpdk.org wrote:
> https://bugs.dpdk.org/show_bug.cgi?id=1376
>
> Bug ID: 1376
> Summary: A BPF can no longer include header rte_mbuf_core.h
> Product: DPDK
> Version: 23.11
> Hardware: x86
> OS: Linux
> Status: UNCONFIRMED
> Severity: major
> Priority: Normal
> Component: other
> Assignee: dev@dpdk.org
> Reporter: michel@digirati.com.br
> Target Milestone: ---
>
> Created attachment 272
> --> https://bugs.dpdk.org/attachment.cgi?id=272&action=edit
> Compilation errors for t2.c and t3.c
>
> A BPF needs to include the header <rte_mbuf_core.h> to access struct rte_mbuf.
> But the current version of the header <rte_mbuf_core.h> cannot be included in a
> BPF. The attached file shows the errors one gets while compiling the files
> examples/bpf/t2.c and examples/bpf/t3.c.
a bug was fixed where rte_arch_bswap16 was being hidden except when
RTE_FORCE_INTRINSICS was defined.
i suspect -t bpf should likely define RTE_FORCE_INTRINSICS since it
seems generally unreasonable to have x86 inline asm in a bpf translation
unit.
if there are problems with RTE_FORCE_INTRINSICS they'll have to be
addressed as separate bugs.
ty
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.
prev parent reply other threads:[~2024-01-30 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 15:42 bugzilla
2024-01-30 19:07 ` Tyler Retzlaff [this message]
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=20240130190742.GA18445@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=roretzla@linux.microsoft.com \
--cc=bugzilla@dpdk.org \
--cc=dev@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).