From: Mike Snitzer <snitzer@kernel.org>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: ming.lei@redhat.com, hch@lst.de, bvanassche@acm.org,
axboe@kernel.dk, mpatocka@redhat.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
yukuai3@huawei.com, yi.zhang@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH 2/2] block: remove blk_mq_in_flight() and blk_mq_in_flight_rw()
Date: Sat, 23 Mar 2024 12:05:23 -0400 [thread overview]
Message-ID: <Zf79w4Ip3fzSMCWh@redhat.com> (raw)
In-Reply-To: <20240323035959.1397382-3-yukuai1@huaweicloud.com>
On Fri, Mar 22 2024 at 11:59P -0400,
Yu Kuai <yukuai1@huaweicloud.com> wrote:
> From: Yu Kuai <yukuai3@huawei.com>
>
> Now that blk-mq also use per_cpu counter to trace inflight as bio-based
> device, they can be replaced by part_in_flight() and part_in_flight_rw()
> directly.
Please reference the commit that enabled this, e.g.:
With commit XXXXX ("commit subject") blk-mq was updated to use per_cpu
counters to track inflight IO same as bio-based devices, so replace
blk_mq_in_flight* with part_in_flight() and part_in_flight_rw()
accordingly.
(I'm not seeing the commit in question, but I only took a quick look).
Mike
next prev parent reply other threads:[~2024-03-23 16:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 3:59 [PATCH 0/2] block: support to account io_ticks precisely Yu Kuai
2024-03-23 3:59 ` [PATCH 1/2] " Yu Kuai
2024-03-23 3:59 ` [PATCH 2/2] block: remove blk_mq_in_flight() and blk_mq_in_flight_rw() Yu Kuai
2024-03-23 16:05 ` Mike Snitzer [this message]
2024-03-24 2:11 ` Yu Kuai
2024-03-24 21:57 ` Mike Snitzer
2024-03-25 1:15 ` Yu Kuai
2024-03-23 3:59 ` [PATCH 0/2] block: support to account io_ticks precisely Yu Kuai
2024-03-23 4:08 ` Yu Kuai
2024-03-23 3:59 ` [PATCH 1/2] " Yu Kuai
2024-03-23 3:59 ` [PATCH 2/2] block: remove blk_mq_in_flight() and blk_mq_in_flight_rw() Yu Kuai
2024-04-06 7:57 ` [PATCH 0/2] block: support to account io_ticks precisely Yu Kuai
2024-04-20 1:49 ` Yu Kuai
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=Zf79w4Ip3fzSMCWh@redhat.com \
--to=snitzer@kernel.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=mpatocka@redhat.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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