From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Ming Lei <ming.lei@redhat.com>,
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 13:20:15 -0700 [thread overview]
Message-ID: <ZF6ff2l7SKiCrTt0@infradead.org> (raw)
In-Reply-To: <70478f95-2852-9bf1-f8f7-630c74641c0f@kernel.dk>
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.
Because we really need to keep the passthrough code separate. The
fact that a passthrough request can leak into common code in various
places is really a bit of a problem. We have most of these nicely
separate with two exceptions:
- the plug list
- the requeue list
The higher level and the more obvious we special case the passthrough
request there, the better for debuggability and maintainability.
next prev parent reply other threads:[~2023-05-12 20:20 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
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 [this message]
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=ZF6ff2l7SKiCrTt0@infradead.org \
--to=hch@infradead.org \
--cc=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