Linux block layer
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@fb.com>
To: Sagi Grimberg <sagi@grimberg.me>, Omar Sandoval <osandov@osandov.com>
Cc: <linux-block@vger.kernel.org>, <kernel-team@fb.com>
Subject: Re: [PATCH 1/3] blk-mq: make blk_mq_alloc_request_hctx() allocate a scheduler request
Date: Mon, 27 Feb 2017 11:44:32 -0700	[thread overview]
Message-ID: <9314f153-0264-2efb-fe52-a7823ce18051@fb.com> (raw)
In-Reply-To: <719e3d15-73e2-0b11-e205-e733b882c2ae@grimberg.me>

On 02/27/2017 11:41 AM, Sagi Grimberg wrote:
> 
>>>>> blk_mq_alloc_request_hctx() allocates a driver request directly, unlike
>>>>> its blk_mq_alloc_request() counterpart. It also crashes because it
>>>>> doesn't update the tags->rqs map.
>>>>>
>>>>> Fix it by making it allocate a scheduler request.
>>>>
>>>> All three look good to me. Would you mind respinning #1, it doesn't
>>>> apply on top of the reserved tag patch.
>>>
>>> Yup, I had those based on Sagi's original patches for some reason. I
>>> fat-fingered send-email, sent as a reply to the original patch 1 instead
>>> of this email.
>>
>> I got it, applied all 3, thanks Omar!
> 
> FWIW, you can add my:
> 
> Tested-by: Sagi Grimberg <sagi@grmberg.me>

Done, I fixed up your typo, though :-)

> Although I didn't try to trigger reserved vs. normal tag
> competition which will never ever happen for nvmf btw, but
> I assume it can happen in drivers who use reserved for error
> handling.

As long as we verify they work independently, there should not
be a need to check that edge case separately. We should have
identical behavior there now to previously.

-- 
Jens Axboe

  reply	other threads:[~2017-02-27 19:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27 17:47 [PATCH 1/3] blk-mq: make blk_mq_alloc_request_hctx() allocate a scheduler request Omar Sandoval
2017-02-27 17:47 ` [PATCH 2/3] blk-mq: kill blk_mq_set_alloc_data() Omar Sandoval
2017-02-27 17:47 ` [PATCH 3/3] blk-mq: move update of tags->rqs to __blk_mq_alloc_request() Omar Sandoval
2017-02-27 17:53 ` [PATCH 1/3] blk-mq: make blk_mq_alloc_request_hctx() allocate a scheduler request Omar Sandoval
2017-02-27 18:02   ` Sagi Grimberg
2017-02-27 18:07 ` Jens Axboe
2017-02-27 18:30   ` Omar Sandoval
2017-02-27 18:34     ` Jens Axboe
2017-02-27 18:41       ` Sagi Grimberg
2017-02-27 18:44         ` Jens Axboe [this message]
2017-02-27 18:28 ` [PATCH v2] " Omar Sandoval

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=9314f153-0264-2efb-fe52-a7823ce18051@fb.com \
    --to=axboe@fb.com \
    --cc=kernel-team@fb.com \
    --cc=linux-block@vger.kernel.org \
    --cc=osandov@osandov.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox