From: Zhan Xusheng <zhanxusheng1024@gmail.com>
To: Christian Loehle <christian.loehle@arm.com>
Cc: Zhan Xusheng <zhanxusheng@xiaomi.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Balbir Singh <bsingharora@gmail.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Valentin Schneider <vschneid@redhat.com>,
Josh Snyder <joshs@netflix.com>,
Kayra Cizmeci <kayracizmeci@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] sched: Account I/O waits independently of delayed dequeue
Date: Thu, 15 Oct 2026 20:02:27 +0800 [thread overview]
Message-ID: <20261015120227.1929531-1-zhanxusheng1024@gmail.com> (raw)
In-Reply-To: <fd8578a1-e60b-4993-ab51-2b5d63abcf77@arm.com>
From: Zhan Xusheng <zhanxusheng@xiaomi.com>
On 10/15/26 12:37, Christian Loehle wrote:
> Save the CPU charged at the start of the wait. Delayed tasks can migrate
> while still queued, and proxy execution can also move blocked tasks.
> Decrement the saved CPU's counter on unblock, regardless of the task's
> current placement, and remove the old dequeue-based accounting.
This addresses what I reported, and the nr_iowait pairing holds for the
paths I could find, including the should_block == false one where the
decrement comes from find_proxy_task().
Reviewed-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
next prev parent reply other threads:[~2026-10-15 12:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 8:17 [PATCH] delayacct: Account blkio start on the correct task Zhan Xusheng
2026-10-14 15:20 ` Christian Loehle
2026-10-14 16:12 ` [PATCH] sched: Account blkio delay independently of delayed dequeue Christian Loehle
2026-10-14 16:55 ` Kayra Cizmeci
2026-10-15 2:59 ` Zhan Xusheng
2026-10-15 10:40 ` Christian Loehle
2026-10-15 11:37 ` [PATCHv2] sched: Account I/O waits " Christian Loehle
2026-10-15 12:02 ` Zhan Xusheng [this message]
2026-10-15 12:16 ` Kayra Cizmeci
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=20261015120227.1929531-1-zhanxusheng1024@gmail.com \
--to=zhanxusheng1024@gmail.com \
--cc=bsingharora@gmail.com \
--cc=christian.loehle@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=joshs@netflix.com \
--cc=juri.lelli@redhat.com \
--cc=kayracizmeci@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=zhanxusheng@xiaomi.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
all inboxes | Powered by JetHome®