[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z8IxQy9bvanaiFq6@slm.duckdns.org>
Date: Fri, 28 Feb 2025 11:57:23 -1000
From: Tejun Heo <tj@...nel.org>
To: Juntong Deng <juntong.deng@...look.com>
Cc: 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, void@...ifault.com, arighi@...dia.com,
changwoo@...lia.com, bpf@...r.kernel.org,
linux-kernel@...r.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
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
> 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.
>
Can you merge this into the next patch? I don't think separating this out
helps with reviewing.
Thanks.
--
tejun
Powered by blists - more mailing lists