From: no-reply@sashiko.virtuozzo.com
To: Konstantin Khorenko <khorenko@virtuozzo.com>,
Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1] ms/block: drop the cached plug time when blk_add_rq_to_plug() flushes
Date: Thu, 1 Oct 2026 15:28:15 +0000 [thread overview]
Message-ID: <010701a0f8149d48-c303c705-ed50-4707-bbb6-308bfcee4e1c-000000@eu-central-1.amazonses.com> (raw)
In-Reply-To: <20261001-blk-flush-ts-plug-v1-1-22d9a1f0c9bf@virtuozzo.com>
> blk_time_get_ns() caches the current time in the task's plug. The idea
> is that the cache lives for one plug and is dropped when the plug is
> flushed. __blk_flush_plug() and finish_task_switch() do that.
>
> blk_add_rq_to_plug() also flushes, when the plug has too many requests
> or the last request is at least BLK_PLUG_FLUSH_SIZE. But it calls
> blk_mq_flush_plug_list() directly and never drops the cached time. So
> a task that keeps submitting without sleeping stamps every request
> after that with the time first cached in the plug. start_time_ns and
> io_start_time_ns are stale and the disk stats charge each request for
> the whole time since the plug began.
>
> Drop the cached time after the flush, same as __blk_flush_plug() does.
>
> Fixes: da4c8c3d0975 ("block: cache current nsec time in struct blk_plug")
> Cc: stable@vger.kernel.org
> Signed-off-by: Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>
> Link: https://patch.msgid.link/20260930-blk-plug-ts-flush-v1-1-bf8ca7bc5cd6@virtuozzo.com
> Signed-off-by: Jens Axboe <axboe@kernel.dk>
>
> (cherry picked from commit e0f2224433b15a57125d6ac5d46182f99c6c9d08)
>
> Rebase note: the commit is in the block tree (axboe/linux.git) and not
> in mainline yet. In this kernel blk_plug_invalidate_ts() still takes
> the task as an argument, so pass current.
>
> https://virtuozzo.atlassian.net/browse/VSTOR-147945
> Feature: fix ms/block
>
> Signed-off-by: Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.vzint.dev/#/patchset/20261001-blk-flush-ts-plug-v1-1-22d9a1f0c9bf@virtuozzo.com?part=1
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-10-01 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 15:23 Vasileios Almpanis
2026-10-01 15:28 ` no-reply [this message]
2026-10-06 15:16 ` Konstantin Khorenko
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=010701a0f8149d48-c303c705-ed50-4707-bbb6-308bfcee4e1c-000000@eu-central-1.amazonses.com \
--to=no-reply@sashiko.virtuozzo.com \
--cc=devel@openvz.org \
--cc=khorenko@virtuozzo.com \
--cc=vasileios.almpanis@virtuozzo.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 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.