From: Phil Auld <pauld@redhat.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1] sched: Mention autogroup disabled behavior
Date: Thu, 16 Jan 2025 12:46:54 +0000 [thread overview]
Message-ID: <20250116124654.2365691-1-pauld@redhat.com> (raw)
The autogroup feature can be contolled at runtime when
built into the kernel. Disabling it in this case still
creates autogroups and still shows the autogroup membership
for the task in /proc. The scheduler code will just not
use the the autogroup task group. This can be confusing
to users. Add a sentence to this effect to sched.7 to
point this out.
Signed-off-by: Phil Auld <pauld@redhat.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: <linux-man@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
---
man/man7/sched.7 | 2 ++
1 file changed, 2 insertions(+)
diff --git a/man/man7/sched.7 b/man/man7/sched.7
index 71f098e48..f0a708cd7 100644
--- a/man/man7/sched.7
+++ b/man/man7/sched.7
@@ -724,6 +724,8 @@ in the group terminates.
.P
When autogrouping is enabled, all of the members of an autogroup
are placed in the same kernel scheduler "task group".
+When disabled the group creation happens as above, and autogroup membership
+is still visible in /proc, but the autogroups are not used.
The CFS scheduler employs an algorithm that equalizes the
distribution of CPU cycles across task groups.
The benefits of this for interactive desktop performance
--
2.47.0
next reply other threads:[~2025-01-16 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 12:46 Phil Auld [this message]
2025-01-16 13:06 ` [PATCH v1] sched: Mention autogroup disabled behavior Alejandro Colomar
2025-01-16 13:53 ` Phil Auld
2025-01-16 13:59 ` Alejandro Colomar
2025-01-16 14:14 ` Phil Auld
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=20250116124654.2365691-1-pauld@redhat.com \
--to=pauld@redhat.com \
--cc=alx@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).