From: Tao Cui <cui.tao@linux.dev>
To: Zhe Liu <liuzhe1@kylinos.cn>,
tj@kernel.org, josef@toxicpanda.com, axboe@kernel.dk
Cc: cui.tao@linux.dev, cgroups@vger.kernel.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] blk-iocost: account flush sequence latency only once
Date: Fri, 30 Oct 2026 09:49:32 +0800 [thread overview]
Message-ID: <8f8d1c9e-da88-45a9-bbe0-c1b1403e949c@linux.dev> (raw)
In-Reply-To: <20261029092424.764545-1-liuzhe1@kylinos.cn>
Hi, Zhe
在 2026/10/29 17:24, Zhe Liu 写道:
> A flush sequence with a DATA phase can complete its original request
> twice. Both completions invoke ioc_rqos_done(), causing the request to
> contribute two latency samples and adding the same queue wait time
> twice. This gives such requests disproportionate weight compared to
> ordinary writes, distorting the device-wide latency and queue wait
> feedback used to adjust iocost's virtual time rate.
>
> Skip requests marked RQF_FLUSH_SEQ in ioc_rqos_done(). The flag is set
> when the request enters the flush machinery and is still set when the
> data phase completes; blk_flush_restore_request() clears it before the
> final completion, so accounting happens only once, after the whole
> sequence finishes. The remaining sample covers the request's lifetime
> through any postflush, and its queue wait time is accumulated only
> once.
>
> Fixes: 7caa47151ab2e ("blkcg: implement blk-iocost")
> Cc: stable@vger.kernel.org
> Signed-off-by: Zhe Liu <liuzhe1@kylinos.cn>
> ---
> block/blk-iocost.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/block/blk-iocost.c b/block/blk-iocost.c
> index 2ae40138e041..601029221e6f 100644
> --- a/block/blk-iocost.c
> +++ b/block/blk-iocost.c
> @@ -2868,6 +2868,9 @@ static void ioc_rqos_done(struct rq_qos *rqos, struct request *rq)
> if (!ioc->enabled || !rq->alloc_time_ns || !rq->start_time_ns)
> return;
>
> + if (rq->rq_flags & RQF_FLUSH_SEQ)
> + return;
> +
> switch (req_op(rq)) {
> case REQ_OP_READ:
> pidx = QOS_RLAT;
Reviewed-by: Tao Cui <cuitao@kylinos.cn>
prev parent reply other threads:[~2026-10-30 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 9:24 [PATCH] blk-iocost: account flush sequence latency only once Zhe Liu
2026-10-29 17:13 ` Tejun Heo
2026-10-30 1:49 ` Tao Cui [this message]
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=8f8d1c9e-da88-45a9-bbe0-c1b1403e949c@linux.dev \
--to=cui.tao@linux.dev \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuzhe1@kylinos.cn \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.