From: Chao Leng <lengchao@huawei.com>
To: <linux-nvme@lists.infradead.org>, <linux-block@vger.kernel.org>
Cc: <hch@lst.de>, <sagi@grimberg.me>, <kbusch@kernel.org>,
<axboe@kernel.dk>, <lengchao@huawei.com>
Subject: [PATCH 1/3] blk-mq: delete unnecessary comments
Date: Fri, 29 Jul 2022 15:39:46 +0800 [thread overview]
Message-ID: <20220729073948.32696-2-lengchao@huawei.com> (raw)
In-Reply-To: <20220729073948.32696-1-lengchao@huawei.com>
To improve the quiesce time when using a large set of namespaces, nvme
need using blk_mq_quiesce_queue_nowait directly.
Thus the comments for blk_mq_quiesce_queue_nowait is unnecessary,
so delete the comments.
Signed-off-by: Chao Leng <lengchao@huawei.com>
---
block/blk-mq.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/block/blk-mq.c b/block/blk-mq.c
index 92aae03103b7..6b525640009c 100644
--- a/block/blk-mq.c
+++ b/block/blk-mq.c
@@ -238,10 +238,6 @@ void blk_mq_unfreeze_queue(struct request_queue *q)
}
EXPORT_SYMBOL_GPL(blk_mq_unfreeze_queue);
-/*
- * FIXME: replace the scsi_internal_device_*block_nowait() calls in the
- * mpt3sas driver such that this function can be removed.
- */
void blk_mq_quiesce_queue_nowait(struct request_queue *q)
{
unsigned long flags;
--
2.16.4
next prev parent reply other threads:[~2022-07-29 7:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 7:39 [PATCH 0/3] improve nvme quiesce time for large amount of namespaces Chao Leng
2022-07-29 7:39 ` Chao Leng [this message]
2022-07-29 7:39 ` [PATCH 2/3] nvme: improve the quiesce time for non blocking transports Chao Leng
2022-07-29 7:39 ` [PATCH 3/3] nvme: improve the quiesce time for " Chao Leng
2022-07-29 14:26 ` [PATCH 0/3] improve nvme quiesce time for large amount of namespaces Christoph Hellwig
2022-07-30 0:39 ` Chao Leng
2022-07-31 10:23 ` Sagi Grimberg
2022-08-01 1:45 ` Chao Leng
2022-08-02 13:38 ` Christoph Hellwig
2022-10-10 8:46 ` Chao Leng
2022-10-12 6:37 ` Sagi Grimberg
2022-10-12 8:43 ` Chao Leng
2022-10-12 11:13 ` Sagi Grimberg
2022-10-13 1:37 ` Chao Leng
2022-10-13 2:06 ` Chao Leng
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=20220729073948.32696-2-lengchao@huawei.com \
--to=lengchao@huawei.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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