From: Tejun Heo <tj@kernel.org>
To: Juntong Deng <juntong.deng@outlook.com>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org,
memxor@gmail.com, void@manifault.com, arighi@nvidia.com,
changwoo@igalia.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH sched_ext/for-6.15 v3 2/5] sched_ext: Declare context-sensitive kfunc groups that can be used by different SCX operations
Date: Thu, 27 Feb 2025 09:19:07 -1000 [thread overview]
Message-ID: <Z8C6q2VxuclLiR4p@slm.duckdns.org> (raw)
In-Reply-To: <AM6PR03MB508018ABBD34FBAA089DD9F799C22@AM6PR03MB5080.eurprd03.prod.outlook.com>
On Wed, Feb 26, 2025 at 07:28:17PM +0000, Juntong Deng wrote:
> This patch declare context-sensitive kfunc groups that can be used by
^
declares
> different SCX operations.
...
> +/* 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,
nit: Any specific reason to skip bit 0?
> + 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,
Shouldn't this be SCX_OPS_KF_UNLOCKED?
Thanks.
--
tejun
next prev parent reply other threads:[~2025-02-27 19:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 19:24 [PATCH sched_ext/for-6.15 v3 0/5] bpf, sched_ext: Make kfunc filters support struct_ops context to reduce runtime overhead Juntong Deng
2025-02-26 19:28 ` [PATCH sched_ext/for-6.15 v3 1/5] bpf: Add struct_ops context information to struct bpf_prog_aux Juntong Deng
2025-02-26 19:28 ` [PATCH sched_ext/for-6.15 v3 2/5] sched_ext: Declare context-sensitive kfunc groups that can be used by different SCX operations Juntong Deng
2025-02-27 19:19 ` Tejun Heo [this message]
2025-02-28 21:57 ` Tejun Heo
2025-03-03 21:12 ` Juntong Deng
2025-03-04 18:00 ` Tejun Heo
2025-03-07 0:07 ` Juntong Deng
2025-02-26 19:28 ` [PATCH sched_ext/for-6.15 v3 3/5] sched_ext: Add scx_kfunc_ids_ops_context_sensitive for unified filtering of context-sensitive SCX kfuncs Juntong Deng
2025-02-27 20:25 ` Tejun Heo
2025-02-27 21:23 ` Juntong Deng
2025-02-27 21:32 ` Tejun Heo
2025-02-28 2:34 ` Alexei Starovoitov
2025-02-28 21:31 ` Tejun Heo
2025-02-28 23:06 ` Alexei Starovoitov
2025-02-28 18:42 ` Juntong Deng
2025-02-28 21:20 ` Tejun Heo
2025-02-28 2:38 ` Alexei Starovoitov
2025-02-28 21:14 ` Tejun Heo
2025-02-26 19:28 ` [PATCH sched_ext/for-6.15 v3 4/5] sched_ext: Removed mask-based runtime restrictions on calling kfuncs in different contexts Juntong Deng
2025-02-27 16:24 ` Andrea Righi
2025-02-27 16:49 ` Juntong Deng
2025-02-26 19:28 ` [PATCH sched_ext/for-6.15 v3 5/5] selftests/sched_ext: Update enq_select_cpu_fails to adapt to struct_ops context filter Juntong Deng
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=Z8C6q2VxuclLiR4p@slm.duckdns.org \
--to=tj@kernel.org \
--cc=andrii@kernel.org \
--cc=arighi@nvidia.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=changwoo@igalia.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=juntong.deng@outlook.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=void@manifault.com \
--cc=yonghong.song@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.