From: Igor Russkikh <irusskikh@marvell.com>
To: <dev@dpdk.org>
Cc: Rasesh Mody <rmody@marvell.com>,
Devendra Singh Rawat <dsinghrawat@marvell.com>,
Igor Russkikh <irusskikh@marvell.com>, <stable@dpdk.org>
Subject: [dpdk-dev] [PATCH 1/2] qede: reduce trace verbosity level
Date: Sun, 21 Feb 2021 12:16:36 +0100 [thread overview]
Message-ID: <20210221111637.31193-2-irusskikh@marvell.com> (raw)
In-Reply-To: <20210221111637.31193-1-irusskikh@marvell.com>
On some hardware units it was found this trace is flooding the output,
making any dpdk interactive usage kind of problematic.
It is only informational, without any consequences handling, so reducing
it to verbose from explicit notice level.
CC: stable@dpdk.org
Signed-off-by: Igor Russkikh <irusskikh@marvell.com>
---
drivers/net/qede/base/ecore_int.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/qede/base/ecore_int.c b/drivers/net/qede/base/ecore_int.c
index 4207b1853..2c4aac941 100644
--- a/drivers/net/qede/base/ecore_int.c
+++ b/drivers/net/qede/base/ecore_int.c
@@ -928,7 +928,7 @@ static void ecore_int_attn_print(struct ecore_hwfn *p_hwfn,
bool b_clear)
{
/* @DPDK */
- DP_NOTICE(p_hwfn->p_dev, false, "[block_id %d type %d]\n", id, type);
+ DP_VERBOSE(p_hwfn, ECORE_MSG_INTR, "[block_id %d type %d]\n", id, type);
}
/**
--
2.25.1
next prev parent reply other threads:[~2021-02-21 11:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 11:16 [dpdk-dev] [PATCH 0/2] qede: 2020-02 minor fixes Igor Russkikh
2021-02-21 11:16 ` Igor Russkikh [this message]
2021-03-11 9:13 ` [dpdk-dev] [PATCH 1/2] qede: reduce trace verbosity level Devendra Singh Rawat
2021-02-21 11:16 ` [dpdk-dev] [PATCH 2/2] qede: make driver accept bigger rss tables Igor Russkikh
2021-03-08 19:02 ` Jerin Jacob
2021-03-11 9:28 ` Devendra Singh Rawat
2021-03-19 9:48 ` Igor Russkikh
2021-03-22 5:22 ` Devendra Singh Rawat
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=20210221111637.31193-2-irusskikh@marvell.com \
--to=irusskikh@marvell.com \
--cc=dev@dpdk.org \
--cc=dsinghrawat@marvell.com \
--cc=rmody@marvell.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).