From: Weiping Zhang <zwp10758@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, Ming Lei <ming.lei@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
mpatocka@redhat.com, linux-block@vger.kernel.org
Subject: Re: [PATCH v5 0/2] fix inaccurate io_ticks
Date: Wed, 4 Nov 2020 11:26:13 +0800 [thread overview]
Message-ID: <CAA70yB7bepwNPAMtxth8qJCE6sQM9vxr1A5sU8miFn3tSOSYQQ@mail.gmail.com> (raw)
In-Reply-To: <20201027045411.GA39796@192.168.3.9>
Ping
On Wed, Oct 28, 2020 at 6:59 AM Weiping Zhang
<zhangweiping@didiglobal.com> wrote:
>
> Hi,
>
> This patchset include two patches,
>
> 01. block: fix inaccurate io_ticks
> fix the io_ticks if start a new IO and there is no inflight IO before.
>
> 02. blk-mq: break more earlier when interate hctx
> An optimization for blk_mq_queue_inflight and blk_mq_part_is_in_flight
> these two function only want to know if there is IO inflight and do
> not care how many inflight IOs are there.
> After this patch blk_mq_queue_inflight will stop interate other hctx
> when find a inflight IO, blk_mq_part_is_in_inflight stop interate
> other setbit/hctx when find a inflight IO.
>
> Changes since v4:
> * only get inflight in update_io_ticks when start a new IO every jiffy.
>
> Changes since v3:
> * add a parameter for blk_mq_queue_tag_busy_iter to break earlier
> when interate hctx of a queue, since blk_mq_part_is_in_inflight
> and blk_mq_queue_inflight do not care how many inflight IOs.
>
> Changes since v2:
> * use blk_mq_queue_tag_busy_iter framework instead of open-code.
> * update_io_ticks before update inflight for __part_start_io_acct
>
> Changes since v1:
> * avoid iterate all tagset, return directly if find a set bit.
> * fix some typo in commit message
>
> Weiping Zhang (2):
> block: fix inaccurate io_ticks
> blk-mq: break more earlier when interate hctx
>
> block/blk-core.c | 19 ++++++++++----
> block/blk-mq-tag.c | 11 ++++++--
> block/blk-mq-tag.h | 2 +-
> block/blk-mq.c | 58 +++++++++++++++++++++++++++++++++++++++---
> block/blk-mq.h | 1 +
> block/blk.h | 1 +
> block/genhd.c | 13 ++++++++++
> include/linux/blk-mq.h | 1 +
> 8 files changed, 94 insertions(+), 12 deletions(-)
>
> --
> 2.18.4
>
next prev parent reply other threads:[~2020-11-04 3:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 4:54 [PATCH v5 0/2] fix inaccurate io_ticks Weiping Zhang
2020-11-04 3:26 ` Weiping Zhang [this message]
2020-11-17 3:01 ` Weiping Zhang
2020-11-17 3:27 ` Ming Lei
2020-11-17 4:59 ` Weiping Zhang
2020-11-17 7:40 ` Ming Lei
2020-11-18 5:55 ` Weiping Zhang
2020-11-26 11:23 ` Weiping Zhang
2020-12-17 17:03 ` Weiping 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=CAA70yB7bepwNPAMtxth8qJCE6sQM9vxr1A5sU8miFn3tSOSYQQ@mail.gmail.com \
--to=zwp10758@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=mpatocka@redhat.com \
--cc=snitzer@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).