From: Christoph Hellwig <hch@lst.de>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Alan Stern <stern@rowland.harvard.edu>,
linux-pm@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Christoph Hellwig <hch@lst.de>,
Bart Van Assche <bart.vanassche@wdc.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH RFC 3/4] blk-mq: prepare for supporting runtime PM
Date: Wed, 11 Jul 2018 19:19:08 +0200 [thread overview]
Message-ID: <20180711171908.GD3500@lst.de> (raw)
In-Reply-To: <20180711162906.14271-4-ming.lei@redhat.com>
> index c4b57d8806fe..bf66d561980d 100644
> --- a/block/blk-core.c
> +++ b/block/blk-core.c
> @@ -3804,12 +3804,17 @@ EXPORT_SYMBOL(blk_pm_runtime_init);
> int blk_pre_runtime_suspend(struct request_queue *q)
> {
> int ret = 0;
> + bool active;
>
> if (!q->dev)
> return ret;
>
> spin_lock_irq(q->queue_lock);
> - if (q->nr_pending) {
> + if (!q->mq_ops)
> + active = !!q->nr_pending;
> + else
> + active = !blk_mq_pm_queue_idle(q);
> + if (active) {
We shouldn't really need queue_lock for blk-mq. Also the !! is not
really needed when assigning to a bool.
> +static void blk_mq_pm_add_request(struct request_queue *q, struct request *rq)
> +{
> + if (!blk_mq_support_runtime_pm(q))
> + return;
> +
> + if (q->dev && !(rq->rq_flags & RQF_PM) &&
> + (q->rpm_status == RPM_SUSPENDED || q->rpm_status == RPM_SUSPENDING))
> + pm_request_resume(q->dev);
blk_mq_support_runtime_pm already checks for q->dev. Also to mee
it sems just opencoding blk_mq_pm_add_request / blk_mq_pm_put_request
in the callers would seems more obvious.
> @@ -1841,6 +1863,8 @@ static blk_qc_t blk_mq_make_request(struct request_queue *q, struct bio *bio)
>
> rq_qos_track(q, rq, bio);
>
> + blk_mq_pm_add_request(q, rq);
This doesn't seem to handle passthrough requests and not actually
pair with blk_mq_free_request, is that intentional?
next prev parent reply other threads:[~2018-07-11 17:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 16:29 [PATCH RFC 0/4] blk-mq: support runtime PM Ming Lei
2018-07-11 16:29 ` [PATCH RFC 1/4] blk-mq: introduce blk_mq_support_runtime_pm() Ming Lei
2018-07-11 17:10 ` Christoph Hellwig
2018-07-11 16:29 ` [PATCH RFC 2/4] blk-mq: introduce blk_mq_pm_queue_idle() Ming Lei
2018-07-11 17:11 ` Christoph Hellwig
2018-07-11 16:29 ` [PATCH RFC 3/4] blk-mq: prepare for supporting runtime PM Ming Lei
2018-07-11 17:19 ` Christoph Hellwig [this message]
2018-07-12 9:58 ` Ming Lei
2018-07-12 12:28 ` Ming Lei
2018-07-12 14:00 ` Jens Axboe
2018-07-12 21:32 ` Ming Lei
2018-07-12 21:44 ` Jens Axboe
2018-07-12 23:15 ` Ming Lei
2018-07-13 14:20 ` Jens Axboe
2018-07-13 20:27 ` Alan Stern
2018-07-13 20:39 ` Jens Axboe
2018-07-13 22:47 ` Ming Lei
2018-07-11 16:29 ` [PATCH RFC 4/4] scsi_mq: enable " Ming Lei
2018-07-11 17:14 ` Christoph Hellwig
2018-07-12 1:36 ` Ming Lei
2018-07-12 7:17 ` Christoph Hellwig
2018-07-12 12:21 ` Ming Lei
2018-07-11 17:28 ` Alan Stern
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=20180711171908.GD3500@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@wdc.com \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=stern@rowland.harvard.edu \
/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).