From: Mike Snitzer <snitzer@redhat.com>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Ming Lei <ming.lei@redhat.com>
Subject: Re: [PATCH 2/3] blk-mq: Avoid that blk_mq_delay_run_hw_queue() introduces unintended delays
Date: Fri, 19 Jan 2018 12:21:27 -0500 [thread overview]
Message-ID: <20180119172127.GB29664@redhat.com> (raw)
In-Reply-To: <20180119165856.17677-3-bart.vanassche@wdc.com>
On Fri, Jan 19 2018 at 11:58am -0500,
Bart Van Assche <bart.vanassche@wdc.com> wrote:
> Make sure that calling blk_mq_run_hw_queue() or
> blk_mq_kick_requeue_list() triggers a queue run without delay even
> if blk_mq_delay_run_hw_queue() has been called recently and if its
> delay has not yet expired.
>
> Signed-off-by: Bart Van Assche <bart.vanassche@wdc.com>
Reviewed-by: Mike Snitzer <snitzer@redhat.com>
next prev parent reply other threads:[~2018-01-19 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 16:58 [PATCH 0/3] Avoid that blk_mq_delay_run_hw_queue() introduces unintended delays Bart Van Assche
2018-01-19 16:58 ` [PATCH 1/3] blk-mq: Rename blk_mq_request_direct_issue() into blk_mq_request_issue_directly() Bart Van Assche
2018-01-19 17:20 ` Mike Snitzer
2018-01-19 16:58 ` [PATCH 2/3] blk-mq: Avoid that blk_mq_delay_run_hw_queue() introduces unintended delays Bart Van Assche
2018-01-19 17:21 ` Mike Snitzer [this message]
2018-01-19 16:58 ` [PATCH 3/3] block: Remove kblockd_schedule_delayed_work{,_on}() Bart Van Assche
2018-01-19 17:22 ` Mike Snitzer
2018-01-19 19:54 ` [PATCH 0/3] Avoid that blk_mq_delay_run_hw_queue() introduces unintended delays 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=20180119172127.GB29664@redhat.com \
--to=snitzer@redhat.com \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@wdc.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.