From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1448] cannot disable RTE_ETHDEV_RXTX_CALLBACKS from rte_config.h
Date: Thu, 30 May 2024 14:28:48 +0000 [thread overview]
Message-ID: <bug-1448-3-nP7iIor4h8@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1448-3@http.bugs.dpdk.org/>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1448
Morten Brørup (mb@smartsharesystems.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|CONFIRMED |RESOLVED
--- Comment #3 from Morten Brørup (mb@smartsharesystems.com) ---
The config/rte_config.h source code configuration is for exotic configuration
parameters that we don't want to expose to Meson.
The threshold between normal and exotic is not well defined. :-)
The bug report says that ethdev rx/tx callbacks cannot be disabled in
config/rte_config.h, where it is configurable. This is not correct. They can be
disabled in config/rte_config.h, so there is no bug; the bug reporter just
didn't know how to do it.
Although I personally prefer #if over #ifdef, it would be a huge patch series
to replace all occurrences of #ifdef XYZ with #if XYZ. (2800+ LOC containing
'#ifdef': grep -r '#ifdef' | grep -v '__cplusplus' | wc)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3216 bytes --]
prev parent reply other threads:[~2024-05-30 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 8:44 bugzilla
2024-05-30 10:54 ` bugzilla
2024-05-30 14:05 ` bugzilla
2024-05-30 14:28 ` bugzilla [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=bug-1448-3-nP7iIor4h8@http.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 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).