From: Tejun Heo <tj@kernel.org>
To: Kuba Piecuch <jpiecuch@google.com>
Cc: Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>,
David Vernet <void@manifault.com>,
linux-kernel@vger.kernel.org, sched-ext@lists.linux.dev,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH sched_ext/for-7.1-fixes] sched_ext: Call wakeup_preempt() in local_dsq_post_enq()
Date: Fri, 24 Apr 2026 07:17:32 -1000 [thread overview]
Message-ID: <aeulrBs6ZAopfcHG@slm.duckdns.org> (raw)
In-Reply-To: <20260424092245.3212529-1-jpiecuch@google.com>
Hello, Kuba.
On Fri, Apr 24, 2026 at 09:22:44AM +0000, Kuba Piecuch wrote:
> @@ -1408,11 +1407,19 @@ static void local_dsq_post_enq(struct scx_sched *sch, struct scx_dispatch_q *dsq
> if ((enq_flags & SCX_ENQ_PREEMPT) && p != rq->curr &&
> rq->curr->sched_class == &ext_sched_class) {
> rq->curr->scx.slice = 0;
> - preempt = true;
> + resched_curr(rq);
> }
>
> - if (preempt || sched_class_above(&ext_sched_class, rq->curr->sched_class))
> - resched_curr(rq);
Hmm... I don't quite understand this part of the change. sched_class_above()
got separated out into its own case but why is it dropping resched_curr() on
SCX_ENQ_PREEMPT?
> + /*
> + * If @rq->next_class is currently idle, we need to bump it
> + * to &ext_sched_class using wakeup_preempt(). Otherwise, if we drop
> + * the rq lock later in the pick and an RT task wakes up on @rq,
> + * wakeup_preempt_idle() will be called during RT task wakeup and
> + * SCX won't have an opportunity to re-enqueue IMMED tasks from @rq's
> + * local DSQ.
As this was really subtle, I think it warrants documenting all cases here.
Thanks.
--
tejun
next prev parent reply other threads:[~2026-04-24 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 9:22 [PATCH sched_ext/for-7.1-fixes] sched_ext: Call wakeup_preempt() in local_dsq_post_enq() Kuba Piecuch
2026-04-24 17:17 ` Tejun Heo [this message]
2026-04-27 14:14 ` Kuba Piecuch
2026-04-27 17:01 ` 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=aeulrBs6ZAopfcHG@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=jpiecuch@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sched-ext@lists.linux.dev \
--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