From: Kayra Cizmeci <kayracizmeci@gmail.com>
To: peterz@infradead.org, Tim Chen <tim.c.chen@linux.intel.com>,
Chen Yu <yu.c.chen@intel.com>
Cc: brauner@kernel.org, bsegall@google.com, dietmar.eggemann@arm.com,
imv4bel@gmail.com, jack@suse.cz, juri.lelli@redhat.com,
kees@kernel.org, kprateek.nayak@amd.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mgorman@suse.de, mingo@redhat.com,
qyousef@layalina.io, ricardo.neri-calderon@linux.intel.com,
rostedt@goodmis.org, srikar@linux.ibm.com, sshegde@linux.ibm.com,
vincent.guittot@linaro.org, vineethr@linux.ibm.com,
viro@zeniv.linux.org.uk, vschneid@redhat.com,
wanglu.priv@gmail.com, yi1.lai@intel.com,
zhanxusheng1024@gmail.com, zhanxusheng@xiaomi.com,
ziqianlu@bytedance.com
Subject: Re: [PATCH 1/4] sched/cache: Keep nr_pref_llc_running in the runnable domain
Date: Wed, 16 Sep 2026 16:33:28 +0300 [thread overview]
Message-ID: <20260916133328.3422-1-kayracizmeci@gmail.com> (raw)
In-Reply-To: <20260916123046.GE776954@noisy.programming.kicks-ass.net>
> Needs a fixes tag.
Hi Peter and Tim,
The Fixes tag should be something like:
Fixes: 714059f79ff0 ("sched/cache: Handle moving single tasks to/from their preferred LLC")
This is the commit that adds this:
env->src_rq->nr_pref_llc_running == env->src_rq->cfs.h_nr_runnable
thing. It causes the issue so, you can use this, Tim.
Hope this wasn't a unnecessary message. I wanted to
say this since I already found the commit and didn't want
you guys to search for it again.
Thanks,
Kayra :>
next prev parent reply other threads:[~2026-09-16 13:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 17:46 [PATCH 0/4] sched/cache: Fixes for cache aware scheduling Tim Chen
2026-09-10 17:46 ` [PATCH 1/4] sched/cache: Keep nr_pref_llc_running in the runnable domain Tim Chen
2026-09-10 18:33 ` Kayra Cizmeci
2026-09-10 20:46 ` Tim Chen
2026-09-10 22:03 ` Kayra Cizmeci
2026-09-14 2:02 ` Chen Yu
2026-09-14 5:27 ` Kayra Cizmeci
2026-09-14 22:25 ` Tim Chen
2026-09-10 22:48 ` Kayra Cizmeci
2026-09-16 12:30 ` Peter Zijlstra
2026-09-16 13:33 ` Kayra Cizmeci [this message]
2026-09-10 17:46 ` [PATCH 2/4] sched/cache: Honor migrate_llc_task semantics in active load balance Tim Chen
2026-09-10 17:46 ` [PATCH 3/4] sched/cache: Decouple sched_cache_group from mm Tim Chen
2026-09-16 12:54 ` Peter Zijlstra
2026-09-10 17:46 ` [PATCH 4/4] sched/cache: Introduce task_struct->sched_cache_grp Tim Chen
2026-09-10 19:19 ` Peter Zijlstra
2026-09-10 22:50 ` Tim Chen
2026-09-14 14:34 ` Chen Yu
2026-09-16 13:02 ` Peter Zijlstra
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=20260916133328.3422-1-kayracizmeci@gmail.com \
--to=kayracizmeci@gmail.com \
--cc=brauner@kernel.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=imv4bel@gmail.com \
--cc=jack@suse.cz \
--cc=juri.lelli@redhat.com \
--cc=kees@kernel.org \
--cc=kprateek.nayak@amd.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qyousef@layalina.io \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.ibm.com \
--cc=sshegde@linux.ibm.com \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=vineethr@linux.ibm.com \
--cc=viro@zeniv.linux.org.uk \
--cc=vschneid@redhat.com \
--cc=wanglu.priv@gmail.com \
--cc=yi1.lai@intel.com \
--cc=yu.c.chen@intel.com \
--cc=zhanxusheng1024@gmail.com \
--cc=zhanxusheng@xiaomi.com \
--cc=ziqianlu@bytedance.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®