public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Vitalii Bursov <vitaly@bursov.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	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>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	Valentin Schneider <vschneid@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] docs: cgroup-v1: clarify that domain levels are system-specific
Date: Mon, 1 Apr 2024 09:35:44 +0530	[thread overview]
Message-ID: <3d85926d-378a-4d5e-8303-92461bd3b100@linux.ibm.com> (raw)
In-Reply-To: <af9562aac2e9208029aef1dd19c3b0e096dd42c7.1711900396.git.vitaly@bursov.com>



On 3/31/24 9:31 PM, Vitalii Bursov wrote:
> Add a clarification that domain levels are system-specific
> and where to check for system details.
> 
> Add CPU clusters to the scheduler domain levels table.
> 
> Signed-off-by: Vitalii Bursov <vitaly@bursov.com>
> ---
>  Documentation/admin-guide/cgroup-v1/cpusets.rst | 16 +++++++++++-----
>  1 file changed, 11 insertions(+), 5 deletions(-)
> 
> diff --git a/Documentation/admin-guide/cgroup-v1/cpusets.rst b/Documentation/admin-guide/cgroup-v1/cpusets.rst
> index 7d3415eea..d16a3967d 100644
> --- a/Documentation/admin-guide/cgroup-v1/cpusets.rst
> +++ b/Documentation/admin-guide/cgroup-v1/cpusets.rst
> @@ -568,19 +568,25 @@ on the next tick.  For some applications in special situation, waiting
>  
>  The 'cpuset.sched_relax_domain_level' file allows you to request changing
>  this searching range as you like.  This file takes int value which
> -indicates size of searching range in levels ideally as follows,
> +indicates size of searching range in levels approximately as follows,
>  otherwise initial value -1 that indicates the cpuset has no request.
>  
>  ====== ===========================================================
>    -1   no request. use system default or follow request of others.
>     0   no search.
>     1   search siblings (hyperthreads in a core).
> -   2   search cores in a package.
> -   3   search cpus in a node [= system wide on non-NUMA system]
> -   4   search nodes in a chunk of node [on NUMA system]
> -   5   search system wide [on NUMA system]
> +   2   search cpu clusters
> +   3   search cores in a package.
> +   4   search cpus in a node [= system wide on non-NUMA system]
> +   5   search nodes in a chunk of node [on NUMA system]
> +   6   search system wide [on NUMA system]

I think above block of documentation need not change. SD_CLUSTER is a software 
construct, not a sched domain per se. 

IMO the next paragraph that is added is good enough and the above change can be removed.

>  ====== ===========================================================
>  
> +Not all levels can be present and values can change depending on the
> +system architecture and kernel configuration. Check
> +/sys/kernel/debug/sched/domains/cpu*/domain*/ for system-specific
> +details.
> +
>  The system default is architecture dependent.  The system default
>  can be changed using the relax_domain_level= boot parameter.
>  

  reply	other threads:[~2024-04-01  4:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-31 16:01 [PATCH v2 0/3] sched/fair: allow disabling sched_balance_newidle with sched_relax_domain_level Vitalii Bursov
2024-03-31 16:01 ` [PATCH v2 1/3] " Vitalii Bursov
2024-04-01 10:23   ` Vincent Guittot
2024-03-31 16:01 ` [PATCH v2 2/3] sched/debug: dump domains' level Vitalii Bursov
2024-03-31 16:01 ` [PATCH v2 3/3] docs: cgroup-v1: clarify that domain levels are system-specific Vitalii Bursov
2024-04-01  4:05   ` Shrikanth Hegde [this message]
2024-04-01 10:35     ` Vitalii Bursov
2024-04-01 13:30       ` Shrikanth Hegde

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=3d85926d-378a-4d5e-8303-92461bd3b100@linux.ibm.com \
    --to=sshegde@linux.ibm.com \
    --cc=bristot@redhat.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 \
    --cc=vitaly@bursov.com \
    --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