From: Hui Su <sh_def@163.com>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: "Chen, Yu C" <yu.c.chen@intel.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Valentin Schneider <vschneid@redhat.com>,
John Stultz <jstultz@google.com>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] sched/numa: Drive NUMA task tick from execution context
Date: Wed, 9 Sep 2026 19:55:53 +0900 [thread overview]
Message-ID: <20260909105553.3158889-1-sh_def@163.com> (raw)
In-Reply-To: <e91848b651fbe163676813fffff76970d6895cf9.camel@linux.intel.com>
On Tue, Sep 08, 2026 at 09:01:16AM -0700, Tim Chen wrote:
> I would vote for the real-time comparison. What do you think, Tim?
>
> Agree, I think keeping the real-time comparison makes sense.
Thanks for confirming, Tim.
I agree that the task-clock comparison is the better direction here. I have
incorporated it into the v4 series as patch 5/5, using the donor's
exec_start and a selection-time core_sched_start baseline instead of a
vruntime snapshot. The v4 series has now been sent.
This keeps the comparison in the task-clock domain and avoids mixing
vruntime deltas accumulated under an old weight with a slice calculated from
the current weight. The non-proxy predicate matched the existing
sum_exec_runtime predicate across the tested HZ and nice configurations, and
the proxy force-idle reproducer showed the donor task-clock delta advancing
while the donor sum_exec_runtime delta remained zero.
The patch is available here:
https://lore.kernel.org/r/20260909092901.2989564-6-sh_def@163.com
The v4 cover letter is available here:
https://lore.kernel.org/r/20260909092901.2989564-1-sh_def@163.com
Thanks,
Hui
next prev parent reply other threads:[~2026-09-09 10:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 4:11 [PATCH v2 0/2] sched: Fix execution-context tick handling under proxy execution Hui Su
2026-09-03 4:11 ` [PATCH v2 1/2] sched/numa: Drive NUMA task tick from execution context Hui Su
2026-09-03 12:41 ` Chen, Yu C
2026-09-03 21:30 ` Tim Chen
2026-09-04 5:16 ` Hui Su
2026-09-04 14:10 ` Hui Su
2026-09-04 20:15 ` Tim Chen
2026-09-05 13:58 ` Hui Su
2026-09-08 5:38 ` Chen, Yu C
2026-09-08 16:01 ` Tim Chen
2026-09-09 10:55 ` Hui Su [this message]
2026-09-04 16:10 ` Chen Yu
2026-09-04 20:24 ` Tim Chen
2026-09-03 4:11 ` [PATCH v2 2/2] sched/cache: Drive cache " Hui Su
2026-09-03 4:37 ` K Prateek Nayak
2026-09-03 4:51 ` Hui Su
2026-09-03 17:23 ` Tim Chen
2026-09-04 4:03 ` Hui Su
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=20260909105553.3158889-1-sh_def@163.com \
--to=sh_def@163.com \
--cc=dietmar.eggemann@arm.com \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yu.c.chen@intel.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®