From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "hch@lst.de" <hch@lst.de>, "axboe@kernel.dk" <axboe@kernel.dk>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH 4/4] blk-mq: streamline blk_mq_make_request
Date: Tue, 14 Mar 2017 15:40:44 +0000 [thread overview]
Message-ID: <1489506031.2676.1.camel@sandisk.com> (raw)
In-Reply-To: <20170313154833.14165-5-hch@lst.de>
On Mon, 2017-03-13 at 09:48 -0600, Christoph Hellwig wrote:
> Turn the different ways of merging or issuing I/O into a series of if/els=
e
> statements instead of the current maze of gotos. Note that this means we
> pin the CPU a little longer for some cases as the CTX put is moved to
> common code at the end of the function.
>=20
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> block/blk-mq.c | 67 +++++++++++++++++++++++-----------------------------=
------
> 1 file changed, 27 insertions(+), 40 deletions(-)
>=20
> diff --git a/block/blk-mq.c b/block/blk-mq.c
> index 48748cb799ed..18e449cc832f 100644
> --- a/block/blk-mq.c
> +++ b/block/blk-mq.c
> @@ -1534,16 +1534,17 @@ static blk_qc_t blk_mq_make_request(struct reques=
t_queue *q, struct bio *bio)
> =20
> cookie =3D request_to_qc_t(data.hctx, rq);
> =20
> + plug =3D current->plug;
> if (unlikely(is_flush_fua)) {
> - if (q->elevator)
> - goto elv_insert;
> blk_mq_bio_to_request(rq, bio);
> - blk_insert_flush(rq);
> - goto run_queue;
> - }
> -
> - plug =3D current->plug;
> - if (plug && q->nr_hw_queues =3D=3D 1) {
> + if (q->elevator) {
> + blk_mq_sched_insert_request(rq, false, true,
> + !is_sync || is_flush_fua, true);
> + } else {
> + blk_insert_flush(rq);
> + blk_mq_run_hw_queue(data.hctx, !is_sync || is_flush_fua);
> + }
> + } else if (plug && q->nr_hw_queues =3D=3D 1) {
> struct request *last =3D NULL;
> =20
> blk_mq_bio_to_request(rq, bio);
This change introduces the following construct:
if (is_flush_fua) {
/* use is_flush_fua */
} else ...
Have you considered to simplify the code that uses is_flush_fua further?
> @@ -1562,8 +1563,6 @@ static blk_qc_t blk_mq_make_request(struct request_=
queue *q, struct bio *bio)
> else
> last =3D list_entry_rq(plug->mq_list.prev);
> =20
> - blk_mq_put_ctx(data.ctx);
> -
> if (request_count >=3D BLK_MAX_REQUEST_COUNT || (last &&
> blk_rq_bytes(last) >=3D BLK_PLUG_FLUSH_SIZE)) {
> blk_flush_plug_list(plug, false);
> @@ -1571,56 +1570,44 @@ static blk_qc_t blk_mq_make_request(struct reques=
t_queue *q, struct bio *bio)
> }
> =20
> list_add_tail(&rq->queuelist, &plug->mq_list);
> - goto done;
> - } else if (((plug && !blk_queue_nomerges(q)) || is_sync)) {
> - struct request *old_rq =3D NULL;
> -
> + } else if (plug && !blk_queue_nomerges(q)) {
> blk_mq_bio_to_request(rq, bio);
> =20
> /*
> * We do limited plugging. If the bio can be merged, do that.
> * Otherwise the existing request in the plug list will be
> * issued. So the plug list will have one request at most
> + *
> + * The plug list might get flushed before this. If that happens,
> + * the plug list is emptry and same_queue_rq is invalid.
> */
"emptry" looks like a typo?
> - if (plug) {
> - /*
> - * The plug list might get flushed before this. If that
> - * happens, same_queue_rq is invalid and plug list is
> - * empty
> - */
> - if (same_queue_rq && !list_empty(&plug->mq_list)) {
> - old_rq =3D same_queue_rq;
> - list_del_init(&old_rq->queuelist);
> - }
> - list_add_tail(&rq->queuelist, &plug->mq_list);
> - } else /* is_sync */
> - old_rq =3D rq;
> - blk_mq_put_ctx(data.ctx);
> - if (old_rq)
> - blk_mq_try_issue_directly(data.hctx, old_rq, &cookie);
> - goto done;
> - }
> + if (!list_empty(&plug->mq_list))
> + list_del_init(&same_queue_rq->queuelist);
> + else
> + same_queue_rq =3D NULL;
> =20
> - if (q->elevator) {
> -elv_insert:
> - blk_mq_put_ctx(data.ctx);
> + list_add_tail(&rq->queuelist, &plug->mq_list);
> + if (same_queue_rq)
> + blk_mq_try_issue_directly(data.hctx, same_queue_rq,
> + &cookie);
> + } else if (is_sync) {
> + blk_mq_bio_to_request(rq, bio);
> + blk_mq_try_issue_directly(data.hctx, rq, &cookie);
> + } else if (q->elevator) {
> blk_mq_bio_to_request(rq, bio);
> blk_mq_sched_insert_request(rq, false, true,
> !is_sync || is_flush_fua, true);
> - goto done;
> - }
> - if (!blk_mq_merge_queue_io(data.hctx, data.ctx, rq, bio)) {
> + } else if (!blk_mq_merge_queue_io(data.hctx, data.ctx, rq, bio)) {
> /*
> * For a SYNC request, send it to the hardware immediately. For
> * an ASYNC request, just ensure that we run it later on. The
> * latter allows for merging opportunities and more efficient
> * dispatching.
> */
> -run_queue:
> blk_mq_run_hw_queue(data.hctx, !is_sync || is_flush_fua);
> }
Since this code occurs in the else branch of an if (is_flush_fua) statement=
,
can "|| is_flush_fua" be left out?
What I noticed while reviewing this patch is that there are multiple change=
s in
this patch: not only the goto statements have been eliminated but the old_r=
q
variable has been eliminated too. I think this patch would be easier to rev=
iew
if it would be split in three patches: one that removes the old_rq variable=
,
one that eliminates the goto statements and one that removes dead code.
Thanks,
Bart.=
next prev parent reply other threads:[~2017-03-14 15:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 15:48 unify and streamline the blk-mq make_request implementations Christoph Hellwig
2017-03-13 15:48 ` [PATCH 1/4] blk-mq: remove BLK_MQ_F_DEFER_ISSUE Christoph Hellwig
2017-03-13 20:52 ` Bart Van Assche
2017-03-13 23:16 ` hch
2017-03-13 15:48 ` [PATCH 2/4] blk-mq: merge mq and sq make_request instances Christoph Hellwig
2017-03-13 21:01 ` Bart Van Assche
2017-03-13 23:17 ` hch
2017-03-13 15:48 ` [PATCH 3/4] blk-mq: improve blk_mq_try_issue_directly Christoph Hellwig
2017-03-13 21:02 ` Bart Van Assche
2017-03-13 15:48 ` [PATCH 4/4] blk-mq: streamline blk_mq_make_request Christoph Hellwig
2017-03-14 15:40 ` Bart Van Assche [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-20 20:39 unify and streamline the blk-mq make_request implementations V2 Christoph Hellwig
2017-03-20 20:39 ` [PATCH 4/4] blk-mq: streamline blk_mq_make_request Christoph Hellwig
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=1489506031.2676.1.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
/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