From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"axboe@fb.com" <axboe@fb.com>
Cc: "hch@lst.de" <hch@lst.de>, "osandov@fb.com" <osandov@fb.com>
Subject: Re: [PATCH 3/3] blk-mq: unify hctx delay_work and run_work
Date: Mon, 10 Apr 2017 16:21:57 +0000 [thread overview]
Message-ID: <1491841316.4199.12.camel@sandisk.com> (raw)
In-Reply-To: <1491839696-24783-4-git-send-email-axboe@fb.com>
On Mon, 2017-04-10 at 09:54 -0600, Jens Axboe wrote:
> @@ -1281,27 +1280,39 @@ static void blk_mq_run_work_fn(struct work_struct=
*work)
> struct blk_mq_hw_ctx *hctx;
> =20
> hctx =3D container_of(work, struct blk_mq_hw_ctx, run_work.work);
> - __blk_mq_run_hw_queue(hctx);
> -}
> =20
> -static void blk_mq_delay_work_fn(struct work_struct *work)
> -{
> - struct blk_mq_hw_ctx *hctx;
> + /*
> + * If we are stopped, don't run the queue. The exception is if
> + * BLK_MQ_S_START_ON_RUN is set. For that case, we auto-clear
> + * the STOPPED bit and run it.
> + */
> + if (test_bit(BLK_MQ_S_STOPPED, &hctx->state)) {
> + if (!test_bit(BLK_MQ_S_START_ON_RUN, &hctx->state))
> + return;
> =20
> - hctx =3D container_of(work, struct blk_mq_hw_ctx, delay_work.work);
> + clear_bit(BLK_MQ_S_START_ON_RUN, &hctx->state);
> + clear_bit(BLK_MQ_S_STOPPED, &hctx->state);
> + }
> =20
> - if (test_and_clear_bit(BLK_MQ_S_STOPPED, &hctx->state))
> - __blk_mq_run_hw_queue(hctx);
> + __blk_mq_run_hw_queue(hctx);
> }
> =20
> +
> void blk_mq_delay_queue(struct blk_mq_hw_ctx *hctx, unsigned long msecs)
> {
> if (unlikely(!blk_mq_hw_queue_mapped(hctx)))
> return;
> =20
> + /*
> + * Stop the hw queue, then modify currently delayed work.
> + * This should prevent us from running the queue prematurely.
> + * Mark the queue as auto-clearing STOPPED when it runs.
> + */
> blk_mq_stop_hw_queue(hctx);
> - kblockd_schedule_delayed_work_on(blk_mq_hctx_next_cpu(hctx),
> - &hctx->delay_work, msecs_to_jiffies(msecs));
> + set_bit(BLK_MQ_S_START_ON_RUN, &hctx->state);
> + kblockd_mod_delayed_work_on(blk_mq_hctx_next_cpu(hctx),
> + &hctx->run_work,
> + msecs_to_jiffies(msecs));
> }
> EXPORT_SYMBOL(blk_mq_delay_queue);
Hello Jens,
Is it possible for a block driver to call blk_mq_delay_queue() while
blk_mq_delay_work_fn() is running? Can that result in BLK_MQ_S_STOPPED
and=A0BLK_MQ_S_START_ON_RUN being checked by=A0blk_mq_delay_work_fn() after
blk_mq_delay_queue() has set BLK_MQ_S_STOPPED and before it has set
BLK_MQ_S_START_ON_RUN?
Thanks,
Bart.=
next prev parent reply other threads:[~2017-04-10 16:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 15:54 [PATCH 0/3] blk-mq: unify hardware queue run handlers Jens Axboe
2017-04-10 15:54 ` [PATCH 1/3] blk-mq: unify hctx delayed_run_work and run_work Jens Axboe
2017-04-10 16:09 ` Christoph Hellwig
2017-04-10 16:17 ` Bart Van Assche
2017-04-11 18:00 ` Bart Van Assche
2017-04-14 20:02 ` Jens Axboe
2017-04-14 20:56 ` Bart Van Assche
2017-04-28 2:12 ` Ming Lei
2017-04-10 15:54 ` [PATCH 2/3] block: add kblock_mod_delayed_work_on() Jens Axboe
2017-04-10 16:10 ` Christoph Hellwig
2017-04-10 16:17 ` Bart Van Assche
2017-04-10 15:54 ` [PATCH 3/3] blk-mq: unify hctx delay_work and run_work Jens Axboe
2017-04-10 16:21 ` Bart Van Assche [this message]
2017-04-10 16:53 ` Jens Axboe
2017-04-10 17:23 ` Jens Axboe
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=1491841316.4199.12.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.com \
/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