From: Valentin Schneider <valentin.schneider@arm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>,
linux-kernel@vger.kernel.org, mingo@redhat.com,
peterz@infradead.org, dietmar.eggemann@arm.com,
juri.lelli@redhat.com, rostedt@goodmis.org, mgorman@suse.de
Cc: bsegall@google.com
Subject: Re: [PATCH] sched/fair: add comments for group_type and balancing at SD_NUMA level
Date: Tue, 12 Nov 2019 17:42:44 +0000 [thread overview]
Message-ID: <7325dac4-bb26-9fcb-75bc-15b68d35b62d@arm.com> (raw)
In-Reply-To: <1573570243-1903-1-git-send-email-vincent.guittot@linaro.org>
Hi Vincent,
On 12/11/2019 14:50, Vincent Guittot wrote:
> Add comments to describe each state of goup_type and to add some details
> about the load balance at NUMA level.
>
> Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
Suggestions/nits below. There's a bit of duplication with existing
comments (e.g. the nice blob atop sg_imbalanced()), but I think it can't
hurt to have the few extra lines you're introducing.
---
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index bfdcaf91b325..ec93ebd02352 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -6955,28 +6955,26 @@ enum fbq_type { regular, remote, all };
* group. see update_sd_pick_busiest().
*/
enum group_type {
- /*
- * The group has spare capacity that can be used to process more work.
- */
+ /* The group isn't significantly pressured and can be used to process more work */
group_has_spare = 0,
/*
* The group is fully used and the tasks don't compete for more CPU
- * cycles. Nevetheless, some tasks might wait before running.
+ * cycles. Nevertheless, some tasks might wait before running.
*/
group_fully_busy,
/*
- * One task doesn't fit with CPU's capacity and must be migrated on a
- * more powerful CPU.
+ * (SD_ASYM_CPUCAPACITY only) One task doesn't fit on its CPU's
+ * capacity and must be migrated to a CPU of higher capacity.
*/
group_misfit_task,
/*
- * One local CPU with higher capacity is available and task should be
- * migrated on it instead on current CPU.
+ * (SD_ASYM_PACKING only) One local CPU with higher capacity is
+ * available and task should be migrated to it.
*/
group_asym_packing,
/*
- * The tasks affinity prevents the scheduler to balance the load across
- * the system.
+ * The tasks affinity previously prevented the scheduler from balancing
+ * load across the system.
*/
group_imbalanced,
/*
next prev parent reply other threads:[~2019-11-12 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 14:50 Vincent Guittot
2019-11-12 17:42 ` Valentin Schneider [this message]
2019-11-18 13:34 ` [PATCH v2] " Ingo Molnar
2019-11-18 14:06 ` Valentin Schneider
2019-11-18 17:42 ` [tip: sched/core] sched/fair: Add " tip-bot2 for Vincent Guittot
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=7325dac4-bb26-9fcb-75bc-15b68d35b62d@arm.com \
--to=valentin.schneider@arm.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
/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®