From: Andrea Righi <arighi@nvidia.com>
To: Tejun Heo <tj@kernel.org>
Cc: sched-ext@lists.linux.dev, David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
Emil Tsalapatis <emil@etsalapatis.com>,
David Dai <david.dai@linux.dev>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] sched_ext: Factor out the rq lock switch of scx_dsq_move()
Date: Sun, 18 Oct 2026 00:52:51 +0200 [thread overview]
Message-ID: <atP8QzPqztLBm2PP@gpd4> (raw)
In-Reply-To: <20261017223738.993262-2-tj@kernel.org>
On Sat, Oct 17, 2026 at 12:37:36PM -1000, Tejun Heo wrote:
> Factor the rq lock switch on entry to scx_dsq_move() and its undo on exit
> out into kf_switch_rq_lock() and kf_restore_rq_lock() so that other kfuncs
> operating on a task from a DSQ iteration can share them. No functional
> change.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
Reviewed-by: Andrea Righi <arighi@nvidia.com>
Thanks,
-Andrea
> ---
> kernel/sched/ext/ext.c | 63 ++++++++++++++++++++++++------------------
> 1 file changed, 36 insertions(+), 27 deletions(-)
>
> diff --git a/kernel/sched/ext/ext.c b/kernel/sched/ext/ext.c
> index b9f80fb29255..3e707b00e78b 100644
> --- a/kernel/sched/ext/ext.c
> +++ b/kernel/sched/ext/ext.c
> @@ -9745,6 +9745,40 @@ static const struct btf_kfunc_id_set scx_kfunc_set_enqueue_dispatch = {
> .filter = scx_kfunc_context_filter,
> };
>
> +/*
> + * Lock @rq from a kfunc called either from ops.dispatch(), which holds the
> + * dispatched rq's lock, or from a context holding no rq lock. Under core
> + * scheduling, dispatch can run for a sibling rq, so the locked rq is not
> + * necessarily this CPU's. Return the rq locked on entry, NULL if none.
> + */
> +static struct rq *kf_switch_rq_lock(struct rq *rq, unsigned long *flags)
> +{
> + struct rq *entry_rq;
> +
> + local_irq_save(*flags);
> +
> + entry_rq = scx_locked_rq();
> + if (entry_rq) {
> + if (entry_rq != rq)
> + switch_rq_lock(entry_rq, rq);
> + } else {
> + raw_spin_rq_lock(rq);
> + }
> + return entry_rq;
> +}
> +
> +/* undo kf_switch_rq_lock(), @rq is the rq locked now */
> +static void kf_restore_rq_lock(struct rq *rq, struct rq *entry_rq, unsigned long flags)
> +{
> + if (entry_rq) {
> + if (entry_rq != rq)
> + switch_rq_lock(rq, entry_rq);
> + } else {
> + scx_rq_lock_drop(rq);
> + raw_spin_rq_unlock_irqrestore(rq, flags);
> + }
> +}
> +
> static bool scx_dsq_move(struct bpf_iter_scx_dsq_kern *kit,
> struct task_struct *p, u64 dsq_id, u64 enq_flags,
> bool priq)
> @@ -9779,27 +9813,8 @@ static bool scx_dsq_move(struct bpf_iter_scx_dsq_kern *kit,
> if (unlikely(READ_ONCE(sch->aborting)))
> return false;
>
> - /*
> - * Can be called from either ops.dispatch() holding the dispatched rq's
> - * lock or any context where no rq lock is held. If latter, lock @p's
> - * task_rq which we'll likely need anyway.
> - */
> src_rq = task_rq(p);
> -
> - local_irq_save(flags);
> -
> - /*
> - * Under core scheduling, dispatch can run for a sibling rq, so the
> - * locked rq is not necessarily this CPU's.
> - */
> - locked_rq = scx_locked_rq();
> -
> - if (locked_rq) {
> - if (locked_rq != src_rq)
> - switch_rq_lock(locked_rq, src_rq);
> - } else {
> - raw_spin_rq_lock(src_rq);
> - }
> + locked_rq = kf_switch_rq_lock(src_rq, &flags);
>
> p_rq = src_rq;
> raw_spin_lock(&src_dsq->lock);
> @@ -9838,13 +9853,7 @@ static bool scx_dsq_move(struct bpf_iter_scx_dsq_kern *kit,
> p_rq = move_task_between_dsqs(sch, p, enq_flags, src_dsq, dst_dsq);
> dispatched = true;
> out:
> - if (locked_rq) {
> - if (locked_rq != p_rq)
> - switch_rq_lock(p_rq, locked_rq);
> - } else {
> - scx_rq_lock_drop(p_rq);
> - raw_spin_rq_unlock_irqrestore(p_rq, flags);
> - }
> + kf_restore_rq_lock(p_rq, locked_rq, flags);
>
> kit->cursor.flags &= ~(__SCX_DSQ_ITER_HAS_SLICE |
> __SCX_DSQ_ITER_HAS_VTIME);
> --
> 2.56.0
>
next prev parent reply other threads:[~2026-10-17 22:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 22:37 [PATCHSET sched_ext/for-7.4] sched_ext: Add scx_bpf_dsq_reenq_task() Tejun Heo
2026-10-17 22:37 ` [PATCH 1/3] sched_ext: Factor out the rq lock switch of scx_dsq_move() Tejun Heo
2026-10-17 22:52 ` Andrea Righi [this message]
2026-10-17 22:37 ` [PATCH 2/3] sched_ext: Add scx_bpf_dsq_reenq_task() to re-enqueue single tasks from a DSQ iteration Tejun Heo
2026-10-17 23:01 ` Andrea Righi
2026-10-17 23:35 ` [PATCH v2 " Tejun Heo
2026-10-17 22:37 ` [PATCH 3/3] sched_ext: scx_qmap: Also re-enqueue stranded tasks with scx_bpf_dsq_reenq_task() Tejun Heo
2026-10-17 23:06 ` Andrea Righi
2026-10-17 23:35 ` Tejun Heo
2026-10-18 6:14 ` Andrea Righi
2026-10-17 23:43 ` [PATCHSET sched_ext/for-7.4] sched_ext: Add scx_bpf_dsq_reenq_task() Tejun Heo
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=atP8QzPqztLBm2PP@gpd4 \
--to=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=david.dai@linux.dev \
--cc=emil@etsalapatis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=tj@kernel.org \
--cc=void@manifault.com \
/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®