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 sched_ext/for-7.4] sched_ext: Drop the locks periodically while walking a user DSQ for re-enqueue
Date: Sun, 18 Oct 2026 08:07:33 +0200 [thread overview]
Message-ID: <atRiJSZfbaRunnkL@gpd4> (raw)
In-Reply-To: <20261017235840.1446655-1-tj@kernel.org>
On Sat, Oct 17, 2026 at 01:58:40PM -1000, Tejun Heo wrote:
> reenq_user() drops dsq->lock around each re-enqueue and its rq lock every
> SCX_TASK_ITER_BATCH re-enqueues. A walk filtered by SCX_REENQ_MARKED skips
> unmarked tasks without dropping either, so a long run of unmarked tasks is
> walked in one hold of both locks.
>
> Count the visited tasks instead of the re-enqueued ones and drop both locks
> every SCX_TASK_ITER_BATCH visits. An unfiltered walk drops the locks as
> often as before.
>
> Suggested-by: Andrea Righi <arighi@nvidia.com>
> Link: https://lore.kernel.org/all/atP-LIKpxPhR-Nuc@gpd4/
> Signed-off-by: Tejun Heo <tj@kernel.org>
Looks good!
Reviewed-by: Andrea Righi <arighi@nvidia.com>
Thanks,
-Andrea
> ---
> kernel/sched/ext/ext.c | 24 ++++++++++++++++--------
> 1 file changed, 16 insertions(+), 8 deletions(-)
>
> diff --git a/kernel/sched/ext/ext.c b/kernel/sched/ext/ext.c
> index 14fe63428036..07857039aee6 100644
> --- a/kernel/sched/ext/ext.c
> +++ b/kernel/sched/ext/ext.c
> @@ -5111,7 +5111,7 @@ static void reenq_user(struct rq *rq, struct scx_dispatch_q *dsq, u64 reenq_flag
> struct scx_sched *sch = dsq->sched;
> struct scx_dsq_list_node cursor = INIT_DSQ_LIST_CURSOR(cursor, dsq, 0);
> struct task_struct *p;
> - s32 nr_enqueued = 0;
> + s32 nr_visited = 0;
>
> lockdep_assert_rq_held(rq);
>
> @@ -5121,6 +5121,21 @@ static void reenq_user(struct rq *rq, struct scx_dispatch_q *dsq, u64 reenq_flag
> struct rq *task_rq;
> u32 reason;
>
> + /*
> + * Count skipped tasks too so that a long walk doesn't hold the
> + * locks throughout. The cursor keeps the position.
> + */
> + if (!(++nr_visited % SCX_TASK_ITER_BATCH)) {
> + raw_spin_unlock(&dsq->lock);
> + if (locked_rq) {
> + scx_rq_lock_drop(locked_rq);
> + raw_spin_rq_unlock(locked_rq);
> + locked_rq = NULL;
> + }
> + cpu_relax();
> + raw_spin_lock(&dsq->lock);
> + }
> +
> p = nldsq_cursor_next_task(&cursor, dsq);
> if (!p)
> break;
> @@ -5157,13 +5172,6 @@ static void reenq_user(struct rq *rq, struct scx_dispatch_q *dsq, u64 reenq_flag
>
> scx_do_enqueue_task(task_rq, p, SCX_ENQ_REENQ, -1);
>
> - if (!(++nr_enqueued % SCX_TASK_ITER_BATCH)) {
> - scx_rq_lock_drop(locked_rq);
> - raw_spin_rq_unlock(locked_rq);
> - locked_rq = NULL;
> - cpu_relax();
> - }
> -
> raw_spin_lock(&dsq->lock);
> }
>
> --
> 2.56.0
>
next prev parent reply other threads:[~2026-10-18 6:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 23:58 Tejun Heo
2026-10-18 6:07 ` Andrea Righi [this message]
2026-10-18 6:24 ` 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=atRiJSZfbaRunnkL@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®