[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<AM6PR03MB50806C2E3C50BA1CF2A3257099FE2@AM6PR03MB5080.eurprd03.prod.outlook.com>
Date: Fri, 14 Feb 2025 20:09:26 +0000
From: Juntong Deng <juntong.deng@...look.com>
To: ast@...nel.org,
daniel@...earbox.net,
john.fastabend@...il.com,
andrii@...nel.org,
martin.lau@...ux.dev,
eddyz87@...il.com,
song@...nel.org,
yonghong.song@...ux.dev,
kpsingh@...nel.org,
sdf@...ichev.me,
haoluo@...gle.com,
jolsa@...nel.org,
memxor@...il.com,
tj@...nel.org,
void@...ifault.com,
arighi@...dia.com,
changwoo@...lia.com
Cc: bpf@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [RFC PATCH bpf-next v2 2/5] sched_ext: Declare context-sensitive kfunc groups that can be used by different SCX operations
This patch declare context-sensitive kfunc groups that can be used by
different SCX operations.
In SCX, some kfuncs are context-sensitive and can only be used in
specific SCX operations.
Currently context-sensitive kfuncs can be grouped into UNLOCKED,
CPU_RELEASE, DISPATCH, ENQUEUE, SELECT_CPU.
In this patch enum scx_ops_kf_flags was added to represent these groups,
which is based on scx_kf_mask.
SCX_OPS_KF_ANY is a special value that indicates kfuncs can be used in
any context.
scx_ops_context_flags is used to declare the groups of kfuncs that can
be used by each SCX operation. An SCX operation can use multiple groups
of kfuncs.
Signed-off-by: Juntong Deng <juntong.deng@...look.com>
---
kernel/sched/ext.c | 48 ++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
diff --git a/kernel/sched/ext.c b/kernel/sched/ext.c
index 8857c0709bdd..957a125b129f 100644
--- a/kernel/sched/ext.c
+++ b/kernel/sched/ext.c
@@ -689,6 +689,54 @@ struct sched_ext_ops {
char name[SCX_OPS_NAME_LEN];
};
+/* Each flag corresponds to a btf kfunc id set */
+enum scx_ops_kf_flags {
+ SCX_OPS_KF_ANY = 0,
+ SCX_OPS_KF_UNLOCKED = 1 << 1,
+ SCX_OPS_KF_CPU_RELEASE = 1 << 2,
+ SCX_OPS_KF_DISPATCH = 1 << 3,
+ SCX_OPS_KF_ENQUEUE = 1 << 4,
+ SCX_OPS_KF_SELECT_CPU = 1 << 5,
+};
+
+static const u32 scx_ops_context_flags[] = {
+ [SCX_OP_IDX(select_cpu)] = SCX_OPS_KF_SELECT_CPU | SCX_OPS_KF_ENQUEUE,
+ [SCX_OP_IDX(enqueue)] = SCX_OPS_KF_ENQUEUE,
+ [SCX_OP_IDX(dequeue)] = SCX_OPS_KF_ANY,
+ [SCX_OP_IDX(dispatch)] = SCX_OPS_KF_DISPATCH | SCX_OPS_KF_ENQUEUE,
+ [SCX_OP_IDX(tick)] = SCX_OPS_KF_ANY,
+ [SCX_OP_IDX(runnable)] = SCX_OPS_KF_ANY,
+ [SCX_OP_IDX(running)] = SCX_OPS_KF_ANY,
+ [SCX_OP_IDX(stopping)] = SCX_OPS_KF_ANY,
+ [SCX_OP_IDX(quiescent)] = SCX_OPS_KF_ANY,
+ [SCX_OP_IDX(yield)] = SCX_OPS_KF_ANY,
+ [SCX_OP_IDX(core_sched_before)] = SCX_OPS_KF_ANY,
+ [SCX_OP_IDX(set_weight)] = SCX_OPS_KF_ANY,
+ [SCX_OP_IDX(set_cpumask)] = SCX_OPS_KF_ANY,
+ [SCX_OP_IDX(update_idle)] = SCX_OPS_KF_ANY,
+ [SCX_OP_IDX(cpu_acquire)] = SCX_OPS_KF_ANY,
+ [SCX_OP_IDX(cpu_release)] = SCX_OPS_KF_CPU_RELEASE,
+ [SCX_OP_IDX(init_task)] = SCX_OPS_KF_UNLOCKED,
+ [SCX_OP_IDX(exit_task)] = SCX_OPS_KF_ANY,
+ [SCX_OP_IDX(enable)] = SCX_OPS_KF_ANY,
+ [SCX_OP_IDX(disable)] = SCX_OPS_KF_ANY,
+ [SCX_OP_IDX(dump)] = SCX_OPS_KF_DISPATCH,
+ [SCX_OP_IDX(dump_cpu)] = SCX_OPS_KF_ANY,
+ [SCX_OP_IDX(dump_task)] = SCX_OPS_KF_ANY,
+#ifdef CONFIG_EXT_GROUP_SCHED
+ [SCX_OP_IDX(cgroup_init)] = SCX_OPS_KF_UNLOCKED,
+ [SCX_OP_IDX(cgroup_exit)] = SCX_OPS_KF_UNLOCKED,
+ [SCX_OP_IDX(cgroup_prep_move)] = SCX_OPS_KF_UNLOCKED,
+ [SCX_OP_IDX(cgroup_move)] = SCX_OPS_KF_UNLOCKED,
+ [SCX_OP_IDX(cgroup_cancel_move)] = SCX_OPS_KF_UNLOCKED,
+ [SCX_OP_IDX(cgroup_set_weight)] = SCX_OPS_KF_UNLOCKED,
+#endif /* CONFIG_EXT_GROUP_SCHED */
+ [SCX_OP_IDX(cpu_online)] = SCX_OPS_KF_UNLOCKED,
+ [SCX_OP_IDX(cpu_offline)] = SCX_OPS_KF_UNLOCKED,
+ [SCX_OP_IDX(init)] = SCX_OPS_KF_UNLOCKED,
+ [SCX_OP_IDX(exit)] = SCX_OPS_KF_UNLOCKED,
+};
+
enum scx_opi {
SCX_OPI_BEGIN = 0,
SCX_OPI_NORMAL_BEGIN = 0,
--
2.39.5
Powered by blists - more mailing lists