From: Ming Lei <ming.lei@redhat.com>
To: Bart Van Assche <Bart.VanAssche@wdc.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"hch@infradead.org" <hch@infradead.org>,
"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"axboe@fb.com" <axboe@fb.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"martin@lichtvoll.de" <martin@lichtvoll.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jthumshirn@suse.de" <jthumshirn@suse.de>,
"oleksandr@natalenko.name" <oleksandr@natalenko.name>,
"hare@suse.com" <hare@suse.com>,
"cavery@redhat.com" <cavery@redhat.com>
Subject: Re: [PATCH V7 5/6] block: support PREEMPT_ONLY
Date: Tue, 3 Oct 2017 16:13:33 +0800 [thread overview]
Message-ID: <20171003081333.GA23564@ming.t460p> (raw)
In-Reply-To: <1506961678.3368.29.camel@wdc.com>
On Mon, Oct 02, 2017 at 04:27:59PM +0000, Bart Van Assche wrote:
> On Sat, 2017-09-30 at 14:12 +0800, Ming Lei wrote:
> > +void blk_set_preempt_only(struct request_queue *q, bool preempt_only)
> > +{
> > + blk_mq_freeze_queue(q);
> > + if (preempt_only)
> > + queue_flag_set_unlocked(QUEUE_FLAG_PREEMPT_ONLY, q);
> > + else
> > + queue_flag_clear_unlocked(QUEUE_FLAG_PREEMPT_ONLY, q);
> > + blk_mq_unfreeze_queue(q);
> > +}
> > +EXPORT_SYMBOL(blk_set_preempt_only);
> > +
> > /**
> > * __blk_run_queue_uncond - run a queue whether or not it has been stopped
> > * @q: The queue to run
> > @@ -771,9 +782,18 @@ int blk_queue_enter(struct request_queue *q, unsigned flags)
> > while (true) {
> > int ret;
> >
> > + /*
> > + * preempt_only flag has to be set after queue is frozen,
> > + * so it can be checked here lockless and safely
> > + */
> > + if (blk_queue_preempt_only(q)) {
> > + if (!(flags & BLK_REQ_PREEMPT))
> > + goto slow_path;
> > + }
> > +
> > if (percpu_ref_tryget_live(&q->q_usage_counter))
> > return 0;
>
> Sorry but I don't think that it is possible with these changes to prevent
> that a non-preempt request gets allocated after a (SCSI) queue has been
> quiesced. If the CPU that calls blk_queue_enter() observes the set of the
> PREEMPT_ONLY flag after the queue has been unfrozen and after the SCSI
> device state has been changed into QUIESCED then blk_queue_enter() can
> succeed for a non-preempt request. I think this is exactly the scenario
OK, looks one issue, will address it in next version.
--
Ming
next prev parent reply other threads:[~2017-10-03 8:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-30 6:12 [PATCH V7 0/6] block/scsi: safe SCSI quiescing Ming Lei
2017-09-30 6:12 ` [PATCH V7 1/6] blk-mq: only run hw queues for blk-mq Ming Lei
2017-10-02 13:31 ` Christoph Hellwig
2017-09-30 6:12 ` [PATCH V7 2/6] block: tracking request allocation with q_usage_counter Ming Lei
2017-10-02 13:32 ` Christoph Hellwig
2017-10-02 16:01 ` Bart Van Assche
2017-09-30 6:12 ` [PATCH V7 3/6] block: pass flags to blk_queue_enter() Ming Lei
2017-10-02 13:40 ` Christoph Hellwig
2017-10-03 7:21 ` Ming Lei
2017-09-30 6:12 ` [PATCH V7 4/6] block: prepare for passing RQF_PREEMPT to request allocation Ming Lei
2017-10-02 13:45 ` Christoph Hellwig
2017-09-30 6:12 ` [PATCH V7 5/6] block: support PREEMPT_ONLY Ming Lei
2017-10-02 13:50 ` Christoph Hellwig
2017-10-03 8:22 ` Ming Lei
2017-10-02 16:27 ` Bart Van Assche
2017-10-03 8:13 ` Ming Lei [this message]
2017-09-30 6:12 ` [PATCH V7 6/6] SCSI: set block queue at preempt only when SCSI device is put into quiesce Ming Lei
2017-10-02 13:52 ` Christoph Hellwig
2017-10-03 8:17 ` Ming Lei
2017-09-30 9:47 ` [PATCH V7 0/6] block/scsi: safe SCSI quiescing Martin Steigerwald
2017-09-30 9:51 ` 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=20171003081333.GA23564@ming.t460p \
--to=ming.lei@redhat.com \
--cc=Bart.VanAssche@wdc.com \
--cc=axboe@fb.com \
--cc=cavery@redhat.com \
--cc=hare@suse.com \
--cc=hch@infradead.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=martin@lichtvoll.de \
--cc=oleksandr@natalenko.name \
/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).