From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1774] Build error: static assertion failed: "GMAC_LARGE_PLAINTEXT_LENGTH should not be greater than LARGE_MBUF_DATAPAYLOAD_SIZE"
Date: Tue, 19 Aug 2025 20:58:41 +0000 [thread overview]
Message-ID: <bug-1774-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1980 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1774
Bug ID: 1774
Summary: Build error: static assertion failed:
"GMAC_LARGE_PLAINTEXT_LENGTH should not be greater
than LARGE_MBUF_DATAPAYLOAD_SIZE"
Product: DPDK
Version: 25.07
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: parthakumar.roy@ibm.com
Target Milestone: ---
This commit
https://github.com/DPDK/dpdk/commit/6a9f3f6df9ef51e30ff5bf3eea00f27ffef87a16
enables RTE_PKTMBUF_HEADROOM to be tuned from the build process. However,
GMAC_LARGE_PLAINTEXT_LENGTH setting of 65344 fails a static assert if
RTE_PKTMBUF_HEADROOM is set to 192. Changing it to 65343 would pass the build.
meson setup -Dplatform=x86_64 -Dpkt_mbuf_headroom=192 -Dmax_lcores=128
-Dmax_ethports=64
-Denable_drivers=bus/auxiliary,bus/pci,common/mlx5,net/mlx5,net/tap
-Denable_driver_sdk=true -Dcpu_instruction_set=broadwell -Dprefix=/ build; cd
build &&
...
[896/1072] Compiling C object app/dpdk-test.p/test_test_cryptodev.c.o
FAILED: app/dpdk-test.p/test_test_cryptodev.c.o
...
In file included from ../lib/net/rte_ether.h:14,
from ../app/test/test_cryptodev.c:16:
../app/test/test_cryptodev_aead_test_vectors.h:15:1: error: static assertion
failed: "GMAC_LARGE_PLAINTEXT_LENGTH should not be greater than
LARGE_MBUF_DATAPAYLOAD_SIZE"
15 | static_assert(GMAC_LARGE_PLAINTEXT_LENGTH <=
LARGE_MBUF_DATAPAYLOAD_SIZE,
| ^~~~~~~~~~~~~
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 4020 bytes --]
reply other threads:[~2025-08-19 20:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1774-3@https.bugs.dpdk.org/ \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.