summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKeith Busch <keith.busch@intel.com>2016-02-11 13:05:47 -0700
committerJens Axboe <axboe@fb.com>2016-02-12 08:10:31 -0700
commitf8e68a7c9af5f8047f7f8295874bedf306063709 (patch)
treecbd94ed118904ddbcffc6b080043de479e98b2fb
parentff23a2a15a2117245b4599c1352343c8b8fb4c43 (diff)
downloadlinux-f8e68a7c9af5f8047f7f8295874bedf306063709.tar.gz
linux-f8e68a7c9af5f8047f7f8295874bedf306063709.tar.bz2
linux-f8e68a7c9af5f8047f7f8295874bedf306063709.zip
NVMe: Rate limit nvme IO warnings
We don't need to spam the kernel logs with thousands of IO cancelling messages. We can infer all IO's are being cancelled with fewer, or even none at all. This patch rate limits the message and uses the debug log level as it is mainly used for testing purposes. Signed-off-by: Keith Busch <keith.busch@intel.com> Signed-off-by: Jens Axboe <axboe@fb.com>
-rw-r--r--drivers/nvme/host/pci.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 09cc4dafa32a..a128672472ec 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -1004,7 +1004,7 @@ static void nvme_cancel_queue_ios(struct request *req, void *data, bool reserved
if (!blk_mq_request_started(req))
return;
- dev_warn(nvmeq->q_dmadev,
+ dev_dbg_ratelimited(nvmeq->q_dmadev,
"Cancelling I/O %d QID %d\n", req->tag, nvmeq->qid);
status = NVME_SC_ABORT_REQ;