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>
---
 include/uapi/linux/sched/types.h | 16 ++++++++++++----
 1 file changed, 12 insertions(+), 4 deletions(-)

diff --git a/include/uapi/linux/sched/types.h b/include/uapi/linux/sched/types.h
index bf6e9ae03..b52850b24 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
  * ===========================
@@ -108,10 +114,12 @@ struct sched_attr {
 	__u32 sched_priority;
 
 	/* SCHED_DEADLINE */
-	__u64 sched_runtime;
 	__u64 sched_deadline;
 	__u64 sched_period;
 
+	/* SCHED_NORMAL, SCHED_BATCH, SCHED_DEADLINE */
+	__u64 sched_runtime;
+
 	/* Utilization hints */
 	__u32 sched_util_min;
 	__u32 sched_util_max;
-- 
2.34.1