From: Qi Zhang <qi.z.zhang@intel.com>
To: ferruh.yigit@intel.com
Cc: dev@dpdk.org, xiao.w.wang@intel.com, jingjing.wu@intel.com,
beilei.xing@intel.com, jia.guo@intel.com, qiming.yang@intel.com,
haiyue.wang@intel.comi, Qi Zhang <qi.z.zhang@intel.com>
Subject: [dpdk-dev] [PATCH 0/8] ether: refine debug compile option
Date: Wed, 10 Mar 2021 20:15:37 +0800 [thread overview]
Message-ID: <20210310121537.2019804-1-qi.z.zhang@intel.com> (raw)
PMDs use RTE_LIBRTE_<PMD_NAME>_DEBUG_RX|TX as compile option to wrap
data path debug code. As .config has been removed since the meson build,
It is not friendly for new DPDK users to notice those debug options.
Patch 1/8: introduces new compile options for specific Rx/Tx data path
debug in ether layer, so PMD can choose to reuse them to avoid maintain
their own.
- RTE_LIBRTE_ETHDEV_DEBUG_RX
- RTE_LIBRTE_ETHDEV_DEBUG_TX
Patch 2/8 - 8/8: refine all the compile option for Intel PMDs.
Qi Zhang (8):
ether: refine debug compile option
net/fm10k: refine debug compile option
net/e1000: refine debug compile option
net/i40e: refine debug compile option
net/iavf: refine debug compile option
net/ice: refine debug compile option
net/ixgbe: refine debug compile option
net/igc: refine debug compile option
doc/guides/nics/overview.rst | 20 ++++++++++
drivers/net/e1000/e1000_logs.c | 17 ++-------
drivers/net/e1000/e1000_logs.h | 13 +------
drivers/net/e1000/em_rxtx.c | 38 +++++++++----------
drivers/net/e1000/igb_rxtx.c | 2 +-
drivers/net/fm10k/fm10k_ethdev.c | 7 +---
drivers/net/fm10k/fm10k_logs.h | 13 +------
drivers/net/fm10k/fm10k_rxtx.c | 8 ++--
drivers/net/i40e/i40e_ethdev.c | 7 +---
drivers/net/i40e/i40e_logs.h | 13 +------
drivers/net/i40e/i40e_rxtx.c | 16 ++++----
drivers/net/iavf/iavf_ethdev.c | 7 +---
drivers/net/iavf/iavf_log.h | 13 +------
drivers/net/iavf/iavf_rxtx.c | 8 ++--
drivers/net/ice/ice_ethdev.c | 7 +---
drivers/net/ice/ice_logs.h | 13 +------
drivers/net/ice/ice_rxtx.c | 20 +++++-----
drivers/net/igc/igc_logs.h | 4 +-
drivers/net/igc/igc_txrx.c | 2 +-
drivers/net/ixgbe/ixgbe_ethdev.c | 7 +---
drivers/net/ixgbe/ixgbe_logs.h | 13 +------
drivers/net/ixgbe/ixgbe_rxtx.c | 64 ++++++++++++++++----------------
lib/librte_ethdev/rte_ethdev.h | 16 ++++----
23 files changed, 135 insertions(+), 193 deletions(-)
--
2.26.2
next reply other threads:[~2021-03-10 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 12:15 Qi Zhang [this message]
2021-03-10 12:16 Qi Zhang
2021-03-10 12:35 ` Ferruh Yigit
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=20210310121537.2019804-1-qi.z.zhang@intel.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=haiyue.wang@intel.comi \
--cc=jia.guo@intel.com \
--cc=jingjing.wu@intel.com \
--cc=qiming.yang@intel.com \
--cc=xiao.w.wang@intel.com \
/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).