From: Hui Su <sh_def@163.com>
To: peterz@infradead.org, mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org
Cc: dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
kprateek.nayak@amd.com, jstultz@google.com, metin.kaya@arm.com,
connoro@google.com, tim.c.chen@linux.intel.com,
yu.c.chen@intel.com, linux-kernel@vger.kernel.org,
Hui Su <sh_def@163.com>
Subject: [PATCH 2/2] sched/cache: Use execution context for cache task tick
Date: Thu, 3 Sep 2026 00:33:36 +0800 [thread overview]
Message-ID: <20260902163336.1552840-2-sh_def@163.com> (raw)
In-Reply-To: <20260902163336.1552840-1-sh_def@163.com>
Cache-aware scheduling accounts CPU runtime to the mm of the task
actually executing. update_se() passes rq->curr to account_mm_sched()
for this purpose.
With proxy execution, however, fair_sched_class::task_tick() receives
rq->donor as its task argument. Passing that argument to task_tick_cache()
can therefore queue cache_work and update the cache scan epoch for the
donor's mm even though the corresponding CPU runtime is accounted to the
execution context's mm.
Use rq->curr for task_tick_cache() so cache scan work is driven for the
same execution context whose runtime is accounted by account_mm_sched().
Fixes: df0d98475954 ("sched/cache: Introduce infrastructure for cache-aware load balancing")
Signed-off-by: Hui Su <sh_def@163.com>
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 09ddb3802c28..866f2a5dd101 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -15045,7 +15045,7 @@ static void task_tick_fair(struct rq *rq, struct task_struct *curr, int queued)
if (static_branch_unlikely(&sched_numa_balancing))
task_tick_numa(rq, rq->curr);
- task_tick_cache(rq, curr);
+ task_tick_cache(rq, rq->curr);
update_misfit_status(curr, rq);
check_update_overutilized_status(task_rq(curr));
--
2.54.0
next prev parent reply other threads:[~2026-09-02 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 16:33 [PATCH 1/2] sched/numa: Use execution context for NUMA " Hui Su
2026-09-02 16:33 ` Hui Su [this message]
2026-09-02 20:12 ` [PATCH 2/2] sched/cache: Use execution context for cache " Tim Chen
2026-09-03 2:53 ` 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=20260902163336.1552840-2-sh_def@163.com \
--to=sh_def@163.com \
--cc=bsegall@google.com \
--cc=connoro@google.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=metin.kaya@arm.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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®