From: Allen Hubbe <Allen.Hubbe@emc.com>
To: linux-ntb@googlegroups.com
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Jon Mason <jdmason@kudzu.us>, Dave Jiang <dave.jiang@intel.com>,
Allen Hubbe <Allen.Hubbe@emc.com>
Subject: [PATCH v4 13/19] NTB: Rate limit ntb_qp_link_work
Date: Wed, 10 Jun 2015 05:08:18 -0400 [thread overview]
Message-ID: <26ce1a85c6ee91592fc6fcaa2bc407a26d04acbf.1433925092.git.Allen.Hubbe@emc.com> (raw)
In-Reply-To: <cover.1433925092.git.Allen.Hubbe@emc.com>
In-Reply-To: <cover.1433925092.git.Allen.Hubbe@emc.com>
When the ntb transport is connecting and waiting for the peer, the debug
console receives lots of debug level messages about the remote qp link
status being down. Rate limit those messages.
Signed-off-by: Allen Hubbe <Allen.Hubbe@emc.com>
---
drivers/ntb/ntb_transport.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/ntb/ntb_transport.c b/drivers/ntb/ntb_transport.c
index 2efd1eae9a7c..8ce0bf67ac20 100644
--- a/drivers/ntb/ntb_transport.c
+++ b/drivers/ntb/ntb_transport.c
@@ -850,7 +850,7 @@ static void ntb_qp_link_work(struct work_struct *work)
/* query remote spad for qp ready bits */
ntb_peer_spad_read(nt->ndev, QP_LINKS);
- dev_dbg(&pdev->dev, "Remote QP link status = %x\n", val);
+ dev_dbg_ratelimited(&pdev->dev, "Remote QP link status = %x\n", val);
/* See if the remote side is up */
if (val & BIT(qp->qp_num)) {
--
2.4.0.rc0.43.gcf8a8c6
next prev parent reply other threads:[~2015-06-10 9:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 9:08 [PATCH v4 00/19] NTB: Add NTB hardware abstraction layer Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 01/19] NTB: Move files in preparation for NTB abstraction Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 02/19] NTB: Add NTB hardware abstraction layer Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 03/19] NTB: Split ntb_hw_intel and ntb_transport drivers Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 04/19] NTB: Read peer info from local SPAD in transport Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 05/19] NTB: Enable link for Intel root port mode in probe Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 06/19] NTB: Check the device ID to set errata flags Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 07/19] NTB: Differentiate transport link down messages Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 08/19] NTB: Do not advance transport RX on link down Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 09/19] NTB: Reset transport QP link stats on down Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 10/19] NTB: Add parameters for Intel SNB B2B addresses Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 11/19] NTB: Add ping pong test client Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 12/19] NTB: Add tool " Allen Hubbe
2015-06-10 9:08 ` Allen Hubbe [this message]
2015-06-10 9:08 ` [PATCH v4 14/19] NTB: Use NUMA memory and DMA chan in transport Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 15/19] NTB: Use NUMA memory in Intel driver Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 16/19] NTB: Improve performance with write combining Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 17/19] NTB: Default to CPU memcpy for performance Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 18/19] NTB: Rename Intel code names to platform names Allen Hubbe
2015-06-10 9:08 ` [PATCH v4 19/19] NTB: Increase transport MTU to 64k from 16k Allen Hubbe
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=26ce1a85c6ee91592fc6fcaa2bc407a26d04acbf.1433925092.git.Allen.Hubbe@emc.com \
--to=allen.hubbe@emc.com \
--cc=dave.jiang@intel.com \
--cc=jdmason@kudzu.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.com \
--cc=linux-pci@vger.kernel.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).