From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Swapnil Sapkal <swapnil.sapkal@amd.com>,
peterz@infradead.org, corbet@lwn.net
Cc: kprateek.nayak@amd.com, gautham.shenoy@amd.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Shrikanth Hegde <sshegde@linux.ibm.com>
Subject: Re: [PATCH] docs/sched: Make the sched-stats documentation consistent
Date: Fri, 2 May 2025 14:49:40 +0700 [thread overview]
Message-ID: <aBR5FLEq66tuoEXm@archie.me> (raw)
In-Reply-To: <20250430062559.1188661-1-swapnil.sapkal@amd.com>
[-- Attachment #1: Type: text/plain, Size: 5791 bytes --]
On Wed, Apr 30, 2025 at 06:25:59AM +0000, Swapnil Sapkal wrote:
> diff --git a/Documentation/scheduler/sched-stats.rst b/Documentation/scheduler/sched-stats.rst
> index 08b6bc9a315c..ad68cf1c99e1 100644
> --- a/Documentation/scheduler/sched-stats.rst
> +++ b/Documentation/scheduler/sched-stats.rst
> @@ -86,13 +86,16 @@ Domain statistics
> -----------------
> One of these is produced per domain for each cpu described. (Note that if
> CONFIG_SMP is not defined, *no* domains are utilized and these lines
> -will not appear in the output. <name> is an extension to the domain field
> -that prints the name of the corresponding sched domain. It can appear in
> -schedstat version 17 and above.
> +will not appear in the output.)
>
> domain<N> <name> <cpumask> 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
>
> -The first field is a bit mask indicating what cpus this domain operates over.
> +The <name> field prints the name of the sched domain and is only supported
> +with schedstat version >= 17. On previous versions, <cpumask> is the first
> +field.
> +
> +The <cpumask> field is a bit mask indicating what cpus this domain operates
> +over.
>
> The next 33 are a variety of sched_balance_rq() statistics in grouped into types
> of idleness (busy, idle and newly idle):
> @@ -103,12 +106,13 @@ of idleness (busy, idle and newly idle):
> load did not require balancing when busy
> 3) # of times in this domain sched_balance_rq() tried to move one or
> more tasks and failed, when the cpu was busy
> - 4) Total imbalance in load when the cpu was busy
> - 5) Total imbalance in utilization when the cpu was busy
> - 6) Total imbalance in number of tasks when the cpu was busy
> - 7) Total imbalance due to misfit tasks when the cpu was busy
> - 8) # of times in this domain pull_task() was called when busy
> - 9) # of times in this domain pull_task() was called even though the
> + 4) Total imbalance in load in this domain when the cpu was busy
> + 5) Total imbalance in utilization in this domain when the cpu was busy
> + 6) Total imbalance in number of tasks in this domain when the cpu was busy
> + 7) Total imbalance due to misfit tasks in this domain when the cpu was
> + busy
> + 8) # of times in this domain detach_task() was called when busy
> + 9) # of times in this domain detach_task() was called even though the
> target task was cache-hot when busy
> 10) # of times in this domain sched_balance_rq() was called but did not
> find a busier queue while the cpu was busy
> @@ -121,13 +125,14 @@ of idleness (busy, idle and newly idle):
> the load did not require balancing when the cpu was idle
> 14) # of times in this domain sched_balance_rq() tried to move one or
> more tasks and failed, when the cpu was idle
> - 15) Total imbalance in load when the cpu was idle
> - 16) Total imbalance in utilization when the cpu was idle
> - 17) Total imbalance in number of tasks when the cpu was idle
> - 18) Total imbalance due to misfit tasks when the cpu was idle
> - 19) # of times in this domain pull_task() was called when the cpu
> + 15) Total imbalance in load in this domain when the cpu was idle
> + 16) Total imbalance in utilization in this domain when the cpu was idle
> + 17) Total imbalance in number of tasks in this domain when the cpu was idle
> + 18) Total imbalance due to misfit tasks in this domain when the cpu was
> + idle
> + 19) # of times in this domain detach_task() was called when the cpu
> was idle
> - 20) # of times in this domain pull_task() was called even though
> + 20) # of times in this domain detach_task() was called even though
> the target task was cache-hot when idle
> 21) # of times in this domain sched_balance_rq() was called but did
> not find a busier queue while the cpu was idle
> @@ -140,12 +145,16 @@ of idleness (busy, idle and newly idle):
> load did not require balancing when the cpu was just becoming idle
> 25) # of times in this domain sched_balance_rq() tried to move one or more
> tasks and failed, when the cpu was just becoming idle
> - 26) Total imbalance in load when the cpu was just becoming idle
> - 27) Total imbalance in utilization when the cpu was just becoming idle
> - 28) Total imbalance in number of tasks when the cpu was just becoming idle
> - 29) Total imbalance due to misfit tasks when the cpu was just becoming idle
> - 30) # of times in this domain pull_task() was called when newly idle
> - 31) # of times in this domain pull_task() was called even though the
> + 26) Total imbalance in load in this domain when the cpu was just becoming
> + idle
> + 27) Total imbalance in utilization in this domain when the cpu was just
> + becoming idle
> + 28) Total imbalance in number of tasks in this domain when the cpu was just
> + becoming idle
> + 29) Total imbalance due to misfit tasks in this domain when the cpu was
> + just becoming idle
> + 30) # of times in this domain detach_task() was called when newly idle
> + 31) # of times in this domain detach_task() was called even though the
> target task was cache-hot when just becoming idle
> 32) # of times in this domain sched_balance_rq() was called but did not
> find a busier queue while the cpu was just becoming idle
LGTM, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-05-02 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 6:25 [PATCH] docs/sched: Make the sched-stats documentation consistent Swapnil Sapkal
2025-05-02 2:02 ` Bagas Sanjaya
2025-05-02 6:18 ` Jonathan Corbet
2025-05-02 7:30 ` Bagas Sanjaya
2025-05-02 7:49 ` Bagas Sanjaya [this message]
2025-06-09 22:09 ` Jonathan Corbet
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=aBR5FLEq66tuoEXm@archie.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=gautham.shenoy@amd.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sshegde@linux.ibm.com \
--cc=swapnil.sapkal@amd.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