From: Srikar Dronamraju <srikar@linux.ibm.com>
To: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
K Prateek Nayak <kprateek.nayak@amd.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Srikar Dronamraju <srikar@linux.ibm.com>
Subject: [PATCH 0/3] sched: Fix load accounting and improve imbalance calculation
Date: Fri, 20 Nov 2026 06:05:34 +0530 [thread overview]
Message-ID: <20261120003534.1339296-5-srikar@linux.ibm.com> (raw)
This series contains a few independent scheduler fixes and cleanups.
The first patch corrects load accounting in update_sg_lb_stats() by
excluding delayed-dequeued tasks from sum_nr_running. Delayed-dequeued
tasks remain visible in rq->nr_running even though they are no longer
runnable, causing load balancing statistics to overestimate runnable
load.
The second patch improves imbalance calculation for domains containing
groups with different numbers of cores. Idle CPU counts alone can be
misleading in such cases since larger groups naturally contain more idle
CPUs even when they are proportionally more heavily loaded. Use the
runnable task distribution for imbalance calculation when comparing
groups of differing sizes.
The final patch is a cleanup of cache_nice_tries initialization during
sched-domain construction. The resulting values remain unchanged but the
initialization becomes simpler and easier to follow.
Patches 1 and 2 contain functional fixes while patch 3 is a cleanup.
Srikar Dronamraju (3):
sched/fair: Exclude delayed-dequeued tasks from sum_nr_running
sched/fair: Use runnable task imbalance for asymmetric groups
sched/topology: Simplify cache_nice_tries initialization
kernel/sched/fair.c | 5 +++--
kernel/sched/topology.c | 9 ++-------
2 files changed, 5 insertions(+), 9 deletions(-)
--
2.55.0
next reply other threads:[~2026-11-20 0:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 0:35 Srikar Dronamraju [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-20 1:49 [PATCH 0/3] sched: Fix load accounting and improve imbalance calculation Srikar Dronamraju
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=20261120003534.1339296-5-srikar@linux.ibm.com \
--to=srikar@linux.ibm.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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.