Linux block layer
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <ming.lei@redhat.com>
Cc: linux-block@vger.kernel.org, Guangwu Zhang <guazhang@redhat.com>,
	Yu Kuai <yukuai1@huaweicloud.com>
Subject: Re: [PATCH] blk-mq: don't queue passthrough request into scheduler
Date: Fri, 12 May 2023 09:25:18 -0600	[thread overview]
Message-ID: <b745f17b-088c-a72c-00f2-3c0a13cdead5@kernel.dk> (raw)
In-Reply-To: <ZF5ZB7QWPCF0ZKWN@ovpn-8-16.pek2.redhat.com>

On 5/12/23 9:19 AM, Ming Lei wrote:
> On Fri, May 12, 2023 at 09:08:54AM -0600, Jens Axboe wrote:
>> On 5/12/23 9:03?AM, Ming Lei wrote:
>>> Passthrough(pt) request shouldn't be queued to scheduler, especially some
>>> schedulers(such as bfq) supposes that req->bio is always available and
>>> blk-cgroup can be retrieved via bio.
>>>
>>> Sometimes pt request could be part of error handling, so it is better to always
>>> queue it into hctx->dispatch directly.
>>>
>>> Fix this issue by queuing pt request from plug list to hctx->dispatch
>>> directly.
>>
>> Why not just add the check to the BFQ insertion? That would be a lot
>> more trivial and would not be poluting the core with this stuff.
> 
> pt request is supposed to be issued to device directly, and we never
> queue it to scheduler before 1c2d2fff6dc0 ("block: wire-up support for
> passthrough plugging").
> 
> some pt request might be part of error handling, and adding it to
> scheduler could cause io hang.

I'm not suggesting adding it to the scheduler, just having the bypass
"add to dispatch" in a different spot.

Let me take a look at it... Do we have a reproducer for this issue?

-- 
Jens Axboe



  reply	other threads:[~2023-05-12 15:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 15:03 [PATCH] blk-mq: don't queue passthrough request into scheduler Ming Lei
2023-05-12 15:08 ` Jens Axboe
2023-05-12 15:19   ` Ming Lei
2023-05-12 15:25     ` Jens Axboe [this message]
2023-05-12 15:34       ` Ming Lei
2023-05-12 15:43         ` Jens Axboe
2023-05-12 15:55           ` Ming Lei
2023-05-12 16:10             ` Jens Axboe
2023-05-13 10:55               ` Ming Lei
2023-05-12 20:21           ` Christoph Hellwig
2023-05-12 21:31             ` Jens Axboe
2023-05-12 23:12               ` Christoph Hellwig
2023-05-12 23:14                 ` Christoph Hellwig
2023-05-12 20:20   ` Christoph Hellwig
2023-05-13 11:15     ` Ming Lei
2023-05-13 16:50 ` Jens Axboe
2023-05-14 12:11 ` Guangwu Zhang
2023-05-14 12:24   ` Ming Lei
2023-05-15 14:33 ` Guangwu Zhang

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=b745f17b-088c-a72c-00f2-3c0a13cdead5@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=guazhang@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=yukuai1@huaweicloud.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox