From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "axboe@kernel.dk" <axboe@kernel.dk>,
"ming.lei@redhat.com" <ming.lei@redhat.com>
Cc: "jthumshirn@suse.de" <jthumshirn@suse.de>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"hch@lst.de" <hch@lst.de>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"hare@suse.de" <hare@suse.de>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"stern@rowland.harvard.edu" <stern@rowland.harvard.edu>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>
Subject: Re: [PATCH RFC V2 0/3] blk-mq: support runtime PM
Date: Mon, 16 Jul 2018 16:21:43 +0000 [thread overview]
Message-ID: <8fde59725d10f2b48ec0f8e6e3a6216183a5fe53.camel@wdc.com> (raw)
In-Reply-To: <27bc4ec8-dd63-2b6f-84ef-4c4c0fc7f9e9@kernel.dk>
On Fri, 2018-07-13 at 20:54 -0600, Jens Axboe wrote:
> On 7/13/18 8:37 PM, Ming Lei wrote:
> > OK, I am thinking another idea for addressing this issue.
> >=20
> > We may introduce one logical admin(pm) request queue for each s=
csi_device,
> > and this queue shares tag with IO queue, with NO_SCHED set,=
and always
> > use atomic mode of the queue usage refcounter. Then we may send=
PM
> > command to device after the IO queue is frozen.
> >=20
> > Also PREEMPT_ONLY can be removed too in this way.
> >=20
> > Even in future, all pass-through commands may be sent to this a=
dmin queue.
> >=20
> > If no one objects, I will cook patches towards this direction.
>=20
> Yes, this seems like a fine idea. It's essentially the same as handli=
ng
> the enter differently, but the abstraction is nicer.
Hello Jens,
Why do you support the idea of removing the PREEMPT_ONLY flag? Are you
perhaps concerned about the performance impact of that flag for NVMe reques=
t
processing? If that is your concern and if it can be shown that the
processing of that flag has a measurable performance impact, how about usin=
g
jump labels to ensure that only request queues that need the PREEMPT_ON=
LY
flag pay the overhead of processing that flag? See also
Documentation/static-keys.txt.
Thanks,
Bart.
next prev parent reply other threads:[~2018-07-16 16:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 8:05 [PATCH RFC V2 0/3] blk-mq: support runtime PM Ming Lei
2018-07-13 8:06 ` [PATCH RFC V2 1/3] block: put runtime PM code into common helpers Ming Lei
2018-07-17 13:21 ` Christoph Hellwig
2018-07-13 8:06 ` [PATCH RFC V2 2/3] blk-mq: prepare for supporting runtime PM Ming Lei
2018-07-13 20:16 ` Alan Stern
2018-07-17 13:23 ` Christoph Hellwig
2018-07-13 8:06 ` [PATCH RFC V2 3/3] scsi_mq: enable " Ming Lei
2018-07-17 13:24 ` Christoph Hellwig
2018-07-17 15:30 ` Ming Lei
2018-07-17 15:34 ` Bart Van Assche
2018-07-17 15:38 ` Ming Lei
2018-07-17 19:50 ` hch
2018-07-17 20:54 ` Alan Stern
2018-07-17 21:49 ` Jens Axboe
2018-07-18 12:06 ` Ming Lei
2018-07-18 12:28 ` Johannes Thumshirn
2018-07-18 12:37 ` Ming Lei
2018-07-18 14:12 ` Alan Stern
2018-07-18 14:18 ` Johannes Thumshirn
2018-07-18 15:01 ` Alan Stern
2018-07-19 6:41 ` Johannes Thumshirn
2018-07-19 14:35 ` Alan Stern
2018-07-19 14:43 ` Johannes Thumshirn
2018-07-18 14:50 ` Jens Axboe
2018-07-18 18:46 ` Alan Stern
2018-07-18 23:08 ` Ming Lei
2018-07-18 12:43 ` Hannes Reinecke
2018-07-18 13:05 ` Ming Lei
2018-07-13 14:21 ` [PATCH RFC V2 0/3] blk-mq: support " Jens Axboe
2018-07-14 2:37 ` Ming Lei
2018-07-14 2:54 ` Jens Axboe
2018-07-16 16:21 ` Bart Van Assche [this message]
2018-07-16 16:03 ` Bart Van Assche
2018-07-17 1:12 ` Ming Lei
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=8fde59725d10f2b48ec0f8e6e3a6216183a5fe53.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=adrian.hunter@intel.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--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