From: Rushil Gupta <rushilg@google.com>
To: junfeng.guo@intel.com, jeroendb@google.com, joshwash@google.com,
ferruh.yigit@amd.com
Cc: dev@dpdk.org, stable@dpdk.org, Rushil Gupta <rushilg@google.com>
Subject: [PATCH] net/gve: Change ERR to DEBUG to prevent flooding of logs for Tx-Dqo.
Date: Mon, 19 Feb 2024 02:44:35 +0000 [thread overview]
Message-ID: <20240219024436.1010010-1-rushilg@google.com> (raw)
This was causing failure for testpmd runs (for queues >=15)
presumably due to flooding of logs due to descriptor ring being
overwritten.
Fixes: a01854 ("net/gve: fix dqo bug for chained descriptors")
Cc: stable@dpdk.org
Signed-off-by: Rushil Gupta <rushilg@google.com>
Reviewed-by: Joshua Washington <joshwash@google.com>
---
drivers/net/gve/gve_tx_dqo.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/gve/gve_tx_dqo.c b/drivers/net/gve/gve_tx_dqo.c
index 1a8eb96ea9..30a1455b20 100644
--- a/drivers/net/gve/gve_tx_dqo.c
+++ b/drivers/net/gve/gve_tx_dqo.c
@@ -116,7 +116,7 @@ gve_tx_burst_dqo(void *tx_queue, struct rte_mbuf **tx_pkts, uint16_t nb_pkts)
first_sw_id = sw_id;
do {
if (sw_ring[sw_id] != NULL)
- PMD_DRV_LOG(ERR, "Overwriting an entry in sw_ring");
+ PMD_DRV_LOG(DEBUG, "Overwriting an entry in sw_ring");
txd = &txr[tx_id];
sw_ring[sw_id] = tx_pkt;
--
2.44.0.rc0.258.g7320e95886-goog
next reply other threads:[~2024-02-19 2:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 2:44 Rushil Gupta [this message]
2024-02-19 9:33 ` Ferruh Yigit
2024-02-20 9:40 ` Rushil Gupta
2024-02-19 10:14 ` Ferruh Yigit
2024-02-19 17:26 ` Stephen Hemminger
2024-02-20 3:38 ` Rushil Gupta
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=20240219024436.1010010-1-rushilg@google.com \
--to=rushilg@google.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jeroendb@google.com \
--cc=joshwash@google.com \
--cc=junfeng.guo@intel.com \
--cc=stable@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).