All of lore.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH 1/2] blk-mq-sched: Allocate sched reserved tags as specified in the original queue tagset
Date: Mon, 27 Feb 2017 07:49:39 -0800	[thread overview]
Message-ID: <20170227154939.GA10715@vader> (raw)
In-Reply-To: <1488209781-1084-1-git-send-email-sagi@grimberg.me>

On Mon, Feb 27, 2017 at 05:36:20PM +0200, Sagi Grimberg wrote:
> Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
> ---
>  block/blk-mq-sched.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/block/blk-mq-sched.c b/block/blk-mq-sched.c
> index 98c7b061781e..46ca965fff5c 100644
> --- a/block/blk-mq-sched.c
> +++ b/block/blk-mq-sched.c
> @@ -454,7 +454,8 @@ int blk_mq_sched_setup(struct request_queue *q)
>  	 */
>  	ret = 0;
>  	queue_for_each_hw_ctx(q, hctx, i) {
> -		hctx->sched_tags = blk_mq_alloc_rq_map(set, i, q->nr_requests, 0);
> +		hctx->sched_tags = blk_mq_alloc_rq_map(set, i,
> +				q->nr_requests, set->reserved_tags);
>  		if (!hctx->sched_tags) {
>  			ret = -ENOMEM;
>  			break;
> -- 
> 2.7.4

Hm, this may fix the crash, but I'm not sure it'll work as intended.
When we allocate the request, we'll get a reserved scheduler tag, but
then when we go to dispatch the request and call
blk_mq_get_driver_tag(), we'll be competing with all of the normal
requests for a regular driver tag. So maybe on top of this we should add
the BLK_MQ_REQ_RESERVED flag to the allocation attempt in
blk_mq_get_driver_tag() if the scheduler tag is reserved? I'm hazy on
what we expect from reserved tags, so feel free to call me crazy.

WARNING: multiple messages have this Message-ID (diff)
From: osandov@osandov.com (Omar Sandoval)
Subject: [PATCH 1/2] blk-mq-sched: Allocate sched reserved tags as specified in the original queue tagset
Date: Mon, 27 Feb 2017 07:49:39 -0800	[thread overview]
Message-ID: <20170227154939.GA10715@vader> (raw)
In-Reply-To: <1488209781-1084-1-git-send-email-sagi@grimberg.me>

On Mon, Feb 27, 2017@05:36:20PM +0200, Sagi Grimberg wrote:
> Signed-off-by: Sagi Grimberg <sagi at grimberg.me>
> ---
>  block/blk-mq-sched.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/block/blk-mq-sched.c b/block/blk-mq-sched.c
> index 98c7b061781e..46ca965fff5c 100644
> --- a/block/blk-mq-sched.c
> +++ b/block/blk-mq-sched.c
> @@ -454,7 +454,8 @@ int blk_mq_sched_setup(struct request_queue *q)
>  	 */
>  	ret = 0;
>  	queue_for_each_hw_ctx(q, hctx, i) {
> -		hctx->sched_tags = blk_mq_alloc_rq_map(set, i, q->nr_requests, 0);
> +		hctx->sched_tags = blk_mq_alloc_rq_map(set, i,
> +				q->nr_requests, set->reserved_tags);
>  		if (!hctx->sched_tags) {
>  			ret = -ENOMEM;
>  			break;
> -- 
> 2.7.4

Hm, this may fix the crash, but I'm not sure it'll work as intended.
When we allocate the request, we'll get a reserved scheduler tag, but
then when we go to dispatch the request and call
blk_mq_get_driver_tag(), we'll be competing with all of the normal
requests for a regular driver tag. So maybe on top of this we should add
the BLK_MQ_REQ_RESERVED flag to the allocation attempt in
blk_mq_get_driver_tag() if the scheduler tag is reserved? I'm hazy on
what we expect from reserved tags, so feel free to call me crazy.

  parent reply	other threads:[~2017-02-27 15:49 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27 15:36 [PATCH 1/2] blk-mq-sched: Allocate sched reserved tags as specified in the original queue tagset Sagi Grimberg
2017-02-27 15:36 ` Sagi Grimberg
2017-02-27 15:36 ` [PATCH 2/2] blk-mq: make sure to back-assign the request to rq_map in blk_mq_alloc_request_hctx Sagi Grimberg
2017-02-27 15:36   ` Sagi Grimberg
2017-02-27 16:59   ` Omar Sandoval
2017-02-27 16:59     ` Omar Sandoval
2017-02-27 17:03     ` Jens Axboe
2017-02-27 17:03       ` Jens Axboe
2017-02-27 17:04       ` Omar Sandoval
2017-02-27 17:04         ` Omar Sandoval
2017-02-27 17:06         ` Jens Axboe
2017-02-27 17:06           ` Jens Axboe
2017-02-27 17:26           ` Sagi Grimberg
2017-02-27 17:26             ` Sagi Grimberg
2017-02-27 15:38 ` [PATCH 1/2] blk-mq-sched: Allocate sched reserved tags as specified in the original queue tagset Jens Axboe
2017-02-27 15:38   ` Jens Axboe
2017-02-27 15:49 ` Omar Sandoval [this message]
2017-02-27 15:49   ` Omar Sandoval
2017-02-27 15:53   ` Jens Axboe
2017-02-27 15:53     ` Jens Axboe
2017-02-27 16:10     ` Sagi Grimberg
2017-02-27 16:10       ` Sagi Grimberg
2017-02-27 16:14       ` Omar Sandoval
2017-02-27 16:14         ` Omar Sandoval
2017-02-27 16:17         ` Jens Axboe
2017-02-27 16:17           ` Jens Axboe
2017-02-27 16:15       ` Jens Axboe
2017-02-27 16:15         ` Jens Axboe
2017-02-27 16:23         ` Sagi Grimberg
2017-02-27 16:23           ` Sagi Grimberg
2017-02-27 16:25         ` Omar Sandoval
2017-02-27 16:25           ` Omar Sandoval
2017-02-27 16:27           ` Jens Axboe
2017-02-27 16:27             ` 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=20170227154939.GA10715@vader \
    --to=osandov@osandov.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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.