mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Swapnil Sapkal <swapnil.sapkal@amd.com>
Cc: dietmar.eggemann@arm.com, rostedt@goodmis.org,
	bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
	iamjoonsoo.kim@lge.com, qyousef@layalina.io, alexs@kernel.org,
	lukasz.luba@arm.com, gautham.shenoy@amd.com,
	kprateek.nayak@amd.com, ravi.bangoria@amd.com,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	peterz@infradead.org, mingo@redhat.com, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, corbet@lwn.net
Subject: Re: [PATCH v2 3/6] sched: Report the different kinds of imbalances in /proc/schedstat
Date: Fri, 20 Dec 2024 23:53:17 +0530	[thread overview]
Message-ID: <56790316-d73c-4201-a2fa-9be3019e2f49@linux.ibm.com> (raw)
In-Reply-To: <20241220063224.17767-4-swapnil.sapkal@amd.com>



On 12/20/24 12:02, Swapnil Sapkal wrote:
> In /proc/schedstat, lb_imbalance reports the sum of imbalances
> discovered in sched domains with each call to sched_balance_rq(), which is
> not very useful because lb_imbalance does not mention whether the imbalance
> is due to load, utilization, nr_tasks or misfit_tasks. Remove this field
> from /proc/schedstat.
> 
> Currently there is no field in /proc/schedstat to report different types
> of imbalances. Introduce new fields in /proc/schedstat to report the
> total imbalances in load, utilization, nr_tasks or misfit_tasks.
> 
> Added fields to /proc/schedstat:
>          - lb_imbalance_load: Total imbalance due to load.
>          - lb_imbalance_util: Total imbalance due to utilization.
>          - lb_imbalance_task: Total imbalance due to number of tasks.
>          - lb_imbalance_misfit: Total imbalance due to misfit tasks.
> 
> Reviewed-by: Shrikanth Hegde <sshegde@linux.ibm.com>
> Signed-off-by: Swapnil Sapkal <swapnil.sapkal@amd.com>

I think its better to merge patch 3 and patch 6.

> ---
>   include/linux/sched/topology.h |  5 ++++-
>   kernel/sched/fair.c            | 24 +++++++++++++++++++++++-
>   kernel/sched/stats.c           |  7 +++++--
>   3 files changed, 32 insertions(+), 4 deletions(-)
> 
> diff --git a/include/linux/sched/topology.h b/include/linux/sched/topology.h
> index 4237daa5ac7a..76a662e1ec24 100644
> --- a/include/linux/sched/topology.h
> +++ b/include/linux/sched/topology.h
> @@ -114,7 +114,10 @@ struct sched_domain {
>   	unsigned int lb_count[CPU_MAX_IDLE_TYPES];
>   	unsigned int lb_failed[CPU_MAX_IDLE_TYPES];
>   	unsigned int lb_balanced[CPU_MAX_IDLE_TYPES];
> -	unsigned int lb_imbalance[CPU_MAX_IDLE_TYPES];
> +	unsigned int lb_imbalance_load[CPU_MAX_IDLE_TYPES];
> +	unsigned int lb_imbalance_util[CPU_MAX_IDLE_TYPES];
> +	unsigned int lb_imbalance_task[CPU_MAX_IDLE_TYPES];
> +	unsigned int lb_imbalance_misfit[CPU_MAX_IDLE_TYPES];
>   	unsigned int lb_gained[CPU_MAX_IDLE_TYPES];
>   	unsigned int lb_hot_gained[CPU_MAX_IDLE_TYPES];
>   	unsigned int lb_nobusyg[CPU_MAX_IDLE_TYPES];
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 2ca3f098552c..5e7e4fe81648 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -11699,6 +11699,28 @@ static int should_we_balance(struct lb_env *env)
>   	return group_balance_cpu(sg) == env->dst_cpu;
>   }
>   
> +static void update_lb_imbalance_stat(struct lb_env *env, struct sched_domain *sd,
> +				     enum cpu_idle_type idle)
> +{
> +	if (!schedstat_enabled())
> +		return;
> +
> +	switch (env->migration_type) {
> +	case migrate_load:
> +		__schedstat_add(sd->lb_imbalance_load[idle], env->imbalance);
> +		break;
> +	case migrate_util:
> +		__schedstat_add(sd->lb_imbalance_util[idle], env->imbalance);
> +		break;
> +	case migrate_task:
> +		__schedstat_add(sd->lb_imbalance_task[idle], env->imbalance);
> +		break;
> +	case migrate_misfit:
> +		__schedstat_add(sd->lb_imbalance_misfit[idle], env->imbalance);
> +		break;
> +	}
> +}
> +
>   /*
>    * Check this_cpu to ensure it is balanced within domain. Attempt to move
>    * tasks if there is an imbalance.
> @@ -11749,7 +11771,7 @@ static int sched_balance_rq(int this_cpu, struct rq *this_rq,
>   
>   	WARN_ON_ONCE(busiest == env.dst_rq);
>   
> -	schedstat_add(sd->lb_imbalance[idle], env.imbalance);
> +	update_lb_imbalance_stat(&env, sd, idle);
>   
>   	env.src_cpu = busiest->cpu;
>   	env.src_rq = busiest;
> diff --git a/kernel/sched/stats.c b/kernel/sched/stats.c
> index eb0cdcd4d921..802bd9398a2e 100644
> --- a/kernel/sched/stats.c
> +++ b/kernel/sched/stats.c
> @@ -141,11 +141,14 @@ static int show_schedstat(struct seq_file *seq, void *v)
>   			seq_printf(seq, "domain%d %*pb", dcount++,
>   				   cpumask_pr_args(sched_domain_span(sd)));
>   			for (itype = 0; itype < CPU_MAX_IDLE_TYPES; itype++) {
> -				seq_printf(seq, " %u %u %u %u %u %u %u %u",
> +				seq_printf(seq, " %u %u %u %u %u %u %u %u %u %u %u",
>   				    sd->lb_count[itype],
>   				    sd->lb_balanced[itype],
>   				    sd->lb_failed[itype],
> -				    sd->lb_imbalance[itype],
> +				    sd->lb_imbalance_load[itype],
> +				    sd->lb_imbalance_util[itype],
> +				    sd->lb_imbalance_task[itype],
> +				    sd->lb_imbalance_misfit[itype],
>   				    sd->lb_gained[itype],
>   				    sd->lb_hot_gained[itype],
>   				    sd->lb_nobusyq[itype],

While you are adding this, please update the 
Documentation/scheduler/sched-stats.rst as well.

  reply	other threads:[~2024-12-20 18:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20  6:32 [PATCH v2 0/6] Fixes and improvements " Swapnil Sapkal
2024-12-20  6:32 ` [PATCH v2 1/6] sched/fair: Fix value reported by hot tasks pulled " Swapnil Sapkal
2024-12-24 18:54   ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
2024-12-20  6:32 ` [PATCH v2 2/6] sched/fair: Cleanup in migrate_degrades_locality() to improve readability Swapnil Sapkal
2024-12-24 18:54   ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
2024-12-20  6:32 ` [PATCH v2 3/6] sched: Report the different kinds of imbalances in /proc/schedstat Swapnil Sapkal
2024-12-20 18:23   ` Shrikanth Hegde [this message]
2024-12-20 19:18     ` Shrikanth Hegde
2024-12-24 18:54   ` [tip: sched/core] " tip-bot2 for Swapnil Sapkal
2024-12-20  6:32 ` [PATCH v2 4/6] sched: Move sched domain name out of CONFIG_SCHED_DEBUG Swapnil Sapkal
2024-12-20 18:59   ` Shrikanth Hegde
2024-12-24  4:20     ` Sapkal, Swapnil
2024-12-24 18:54   ` [tip: sched/core] " tip-bot2 for Swapnil Sapkal
2024-12-20  6:32 ` [PATCH v2 5/6] sched/stats: Print domain name in /proc/schedstat Swapnil Sapkal
2024-12-24 18:54   ` [tip: sched/core] " tip-bot2 for K Prateek Nayak
2024-12-20  6:32 ` [PATCH v2 6/6] docs: Update Schedstat version to 17 Swapnil Sapkal
2024-12-20 19:02   ` Shrikanth Hegde
2024-12-23  7:35   ` Shrikanth Hegde
2024-12-24  5:40     ` Sapkal, Swapnil
2024-12-24 18:54   ` [tip: sched/core] " tip-bot2 for Swapnil Sapkal

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=56790316-d73c-4201-a2fa-9be3019e2f49@linux.ibm.com \
    --to=sshegde@linux.ibm.com \
    --cc=alexs@kernel.org \
    --cc=bsegall@google.com \
    --cc=corbet@lwn.net \
    --cc=dietmar.eggemann@arm.com \
    --cc=gautham.shenoy@amd.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=qyousef@layalina.io \
    --cc=ravi.bangoria@amd.com \
    --cc=rostedt@goodmis.org \
    --cc=swapnil.sapkal@amd.com \
    --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 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®