From: Christoph Hellwig <hch@lst.de>
To: Ming Lei <ming.lei@redhat.com>
Cc: Keith Busch <kbusch@kernel.org>,
Bart Van Assche <bvanassche@acm.org>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH V2 2/2] blk-mq: make sure elevator callbacks aren't called for passthrough request
Date: Tue, 16 May 2023 08:24:09 +0200 [thread overview]
Message-ID: <20230516062409.GB7325@lst.de> (raw)
In-Reply-To: <ZGLad5yYUDJBleBQ@ovpn-8-19.pek2.redhat.com>
On Tue, May 16, 2023 at 09:20:55AM +0800, Ming Lei wrote:
> > That sounds like a good idea. It changes more behavior than what Ming is
> > targeting here, but after looking through each use for RQF_ELV, I think
> > not having that set really is the right thing to do in all cases for
> > passthrough requests.
>
> I did consider that approach. But:
>
> - RQF_ELV actually means that the request & its tag is allocated from sched tags.
>
> - if RQF_ELV is cleared for passthrough request, request may be
> allocated from sched tags(normal IO) and driver tags(passthrough) at the same time.
> This way may cause other problem, such as, breaking blk_mq_hctx_has_requests().
> Meantime it becomes not likely to optimize tags resource utilization in future,
> at least for single LUN/NS, no need to keep sched tags & driver tags
> in memory at the same time.
Then make that obvious. That is:
- rename RQF_ELV to RQV_SCHED_TAGS
- add the RQV_SCHED_TAGS check to your blk_mq_bypass_sched helper.
I'd also invert the return value and rename it to someting like
blk_rq_use_sched.
next prev parent reply other threads:[~2023-05-16 6:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 14:45 [PATCH V2 0/2] blk-mq: handle passthrough request as really passthrough Ming Lei
2023-05-15 14:46 ` [PATCH V2 1/2] blk-mq: don't queue plugged passthrough requests into scheduler Ming Lei
2023-05-16 6:22 ` Christoph Hellwig
2023-05-16 8:10 ` Ming Lei
2023-05-17 7:20 ` Christoph Hellwig
2023-05-15 14:46 ` [PATCH V2 2/2] blk-mq: make sure elevator callbacks aren't called for passthrough request Ming Lei
2023-05-15 15:52 ` Bart Van Assche
2023-05-15 20:22 ` Keith Busch
2023-05-16 1:20 ` Ming Lei
2023-05-16 6:24 ` Christoph Hellwig [this message]
2023-05-16 8:39 ` Ming Lei
2023-05-17 7:22 ` Christoph Hellwig
2023-05-17 8:58 ` Ming Lei
2023-05-16 14:47 ` Keith Busch
2023-05-17 3:26 ` Ming Lei
2023-05-17 18:13 ` Keith Busch
2023-05-18 1:22 ` Ming Lei
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=20230516062409.GB7325@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.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;
as well as URLs for NNTP newsgroup(s).