From: Chris Friesen <chris.friesen@windriver.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: sched/fair: documentation on fair server sysfs interface?
Date: Thu, 4 Sep 2025 08:34:23 -0600 [thread overview]
Message-ID: <82fed98e-a4ee-45e1-a4ae-e9fc303a4f67@windriver.com> (raw)
Hi,
I'm not subscribed, please CC me on replies.
Is there any documentation available on how
/sys/kernel/debug/sched/fair_server/cpuX/period and
/sys/kernel/debug/sched/fair_server/cpuX/runtime are expected to be used
and what behaviour should result?
I'm especially curious about the interactions with SCHED_FIFO and
SCHED_DEADLINE tasks.
I had been using RT throttling to protect "regular" tasks from
SCHED_FIFO tasks trying to hog the entire CPU, and it seems that doesn't
work the same in 6.12.
What is the recommended way in 6.12 to have a realtime task that is
effectively a CPU hog, and non-realtime tasks that sometimes need to
run. I'd like the realtime task to have as much CPU as possible, but
not be able to totally starve out the non-realtime task.
Thanks,
Chris
reply other threads:[~2025-09-04 14:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=82fed98e-a4ee-45e1-a4ae-e9fc303a4f67@windriver.com \
--to=chris.friesen@windriver.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®