From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Subject: Re: [PATCH 1/2] blk-mq-tag: change busy_iter_fn to return whether to continue or not
Date: Thu, 08 Nov 2018 10:04:32 -0800 [thread overview]
Message-ID: <1541700272.196084.226.camel@acm.org> (raw)
In-Reply-To: <57c15689-c5bd-be21-6a19-fbf7eb7dfcd0@kernel.dk>
On Thu, 2018-11-08 at 10:50 -0700, Jens Axboe wrote:
> How about this incremental?
>
> diff --git a/block/blk-mq-tag.c b/block/blk-mq-tag.c
> index 097e9a67d5f5..87bc5df72d48 100644
> --- a/block/blk-mq-tag.c
> +++ b/block/blk-mq-tag.c
> @@ -248,7 +248,8 @@ static bool bt_iter(struct sbitmap *bitmap, unsigned int bitnr, void *data)
> * @fn: Pointer to the function that will be called for each request
> * associated with @hctx that has been assigned a driver tag.
> * @fn will be called as follows: @fn(@hctx, rq, @data, @reserved)
> - * where rq is a pointer to a request.
> + * where rq is a pointer to a request. Return true to continue
> + * iterating tags, false to stop.
> * @data: Will be passed as third argument to @fn.
> * @reserved: Indicates whether @bt is the breserved_tags member or the
> * bitmap_tags member of struct blk_mq_tags.
> @@ -301,7 +302,8 @@ static bool bt_tags_iter(struct sbitmap *bitmap, unsigned int bitnr, void *data)
> * or the bitmap_tags member of struct blk_mq_tags.
> * @fn: Pointer to the function that will be called for each started
> * request. @fn will be called as follows: @fn(rq, @data,
> - * @reserved) where rq is a pointer to a request.
> + * @reserved) where rq is a pointer to a request. Return true
> + * to continue iterating tags, false to stop.
> * @data: Will be passed as second argument to @fn.
> * @reserved: Indicates whether @bt is the breserved_tags member or the
> * bitmap_tags member of struct blk_mq_tags.
> @@ -326,7 +328,8 @@ static void bt_tags_for_each(struct blk_mq_tags *tags, struct sbitmap_queue *bt,
> * @fn: Pointer to the function that will be called for each started
> * request. @fn will be called as follows: @fn(rq, @priv,
> * reserved) where rq is a pointer to a request. 'reserved'
> - * indicates whether or not @rq is a reserved request.
> + * indicates whether or not @rq is a reserved request. Return
> + * true to continue iterating tags, false to stop.
> * @priv: Will be passed as second argument to @fn.
> */
> static void blk_mq_all_tag_busy_iter(struct blk_mq_tags *tags,
> @@ -343,7 +346,8 @@ static void blk_mq_all_tag_busy_iter(struct blk_mq_tags *tags,
> * @fn: Pointer to the function that will be called for each started
> * request. @fn will be called as follows: @fn(rq, @priv,
> * reserved) where rq is a pointer to a request. 'reserved'
> - * indicates whether or not @rq is a reserved request.
> + * indicates whether or not @rq is a reserved request. Return
> + * true to continue iterating tags, false to stop.
> * @priv: Will be passed as second argument to @fn.
> */
> void blk_mq_tagset_busy_iter(struct blk_mq_tag_set *tagset,
This looks fine to me. Thanks!
Bart.
next prev parent reply other threads:[~2018-11-08 18:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 16:06 [PATCHSET v2 0/2] Add queue_is_busy helper Jens Axboe
2018-11-08 16:06 ` [PATCH] blk-mq: provide a helper to check if a queue is busy Jens Axboe
2018-11-08 16:06 ` [PATCH 1/2] blk-mq-tag: change busy_iter_fn to return whether to continue or not Jens Axboe
2018-11-08 16:28 ` Bart Van Assche
2018-11-08 16:31 ` Jens Axboe
2018-11-08 17:35 ` Bart Van Assche
2018-11-08 17:47 ` Jens Axboe
2018-11-08 17:50 ` Jens Axboe
2018-11-08 18:04 ` Bart Van Assche [this message]
2018-11-08 16:06 ` [PATCH 2/2] blk-mq: provide a helper to check if a queue is busy Jens Axboe
2018-11-08 16:30 ` Bart Van Assche
2018-11-08 16:32 ` Jens Axboe
2018-11-09 1:53 ` [PATCHSET v2 0/2] Add queue_is_busy helper jianchao.wang
2018-11-09 2:08 ` jianchao.wang
-- strict thread matches above, loose matches on Subject: below --
2018-11-08 15:42 [PATCHSET " Jens Axboe
2018-11-08 15:42 ` [PATCH 1/2] blk-mq-tag: change busy_iter_fn to return whether to continue or not Jens Axboe
2018-11-08 15:48 ` Mike Snitzer
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=1541700272.196084.226.camel@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--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;
as well as URLs for NNTP newsgroup(s).