From: Yiwei Lin <s921975628@gmail.com>
To: peterz@infradead.org, mingo@redhat.com, juri.lelli@redhat.com,
linux-kernel@vger.kernel.org, vincent.guittot@linaro.org,
dietmar.eggemann@arm.com
Cc: Yiwei Lin <s921975628@gmail.com>
Subject: [PATCH v3] sched/uapi: Reflect the use of sched_runtime in fair scheduler
Date: Thu, 21 Nov 2024 01:07:49 +0800 [thread overview]
Message-ID: <20241120170749.23346-1-s921975628@gmail.com> (raw)
After the commit 857b158d, sched_attr::sched_runtime is used
to directly set a suggested request/slice length. Update the
comment and descriptions in sched/uapi to synchronize with this
change.
Signed-off-by: Yiwei Lin <s921975628@gmail.com>
---
Change-Logs in V3:
Minimalize the change by fixing the comment only. The fix is not applied
correctly in V2.
include/uapi/linux/sched/types.h | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/include/uapi/linux/sched/types.h b/include/uapi/linux/sched/types.h
index bf6e9ae03..3586d5ce7 100644
--- a/include/uapi/linux/sched/types.h
+++ b/include/uapi/linux/sched/types.h
@@ -66,9 +66,15 @@
* and policies, that can be used to ensure all the tasks will make their
* timing constraints.
*
- * As of now, the SCHED_DEADLINE policy (sched_dl scheduling class) is the
- * only user of this new interface. More information about the algorithm
- * available in the scheduling class file or in Documentation/.
+ * The SCHED_DEADLINE policy (sched_dl scheduling class) is the main
+ * user of this new interface. For SCHED_NORMAL and SCHED_BATCH tasks
+ * scheduled by the fair(EEVDF) scheduler, although not exactly the same
+ * as the sporadic time-constrained task we mentioned, some concepts are
+ * similar to the model. The period and deadline for SCHED_NORMAL/SCHED_BATCH
+ * task are decided by the scheduler algorithm. However, the user can still
+ * suggest the request/slice length using sched_runtime in this policy. More
+ * information about these algorithms is available in the scheduling class
+ * file or Documentation/.
*
* Task Utilization Attributes
* ===========================
@@ -107,8 +113,9 @@ struct sched_attr {
/* SCHED_FIFO, SCHED_RR */
__u32 sched_priority;
- /* SCHED_DEADLINE */
+ /* SCHED_NORMAL, SCHED_BATCH, SCHED_DEADLINE */
__u64 sched_runtime;
+ /* SCHED_DEADLINE */
__u64 sched_deadline;
__u64 sched_period;
--
2.34.1
reply other threads:[~2024-11-20 17:07 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=20241120170749.23346-1-s921975628@gmail.com \
--to=s921975628@gmail.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.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®