From: Cheng-Yang Chou <yphbchou0911@gmail.com>
To: Kuba Piecuch <jpiecuch@google.com>
Cc: Tejun Heo <tj@kernel.org>, 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,
Ching-Chun Huang <jserv@ccns.ncku.edu.tw>,
Chia-Ping Tsai <chia7712@gmail.com>
Subject: Re: [PATCH] sched_ext: Documentation: add note about multiple ops.enqueue() calls in a row
Date: Mon, 20 Apr 2026 23:23:59 +0800 [thread overview]
Message-ID: <20260420232245.Gc8ef@cchengyang.duckdns.org> (raw)
In-Reply-To: <DHY3280DLSAP.3PP7V3KZK618F@google.com>
Hi Kuba,
On Mon, Apr 20, 2026 at 03:21:59PM +0000, Kuba Piecuch wrote:
> Hi Cheng-Yang,
>
> On Mon Apr 20, 2026 at 3:12 PM UTC, Cheng-Yang Chou wrote:
> > Hi Kuba,
> >
> > On Mon, Apr 20, 2026 at 02:39:39PM +0000, Kuba Piecuch wrote:
> >> Commit 84b1a0ea0b7c
> >> ("sched_ext: Implement scx_bpf_dsq_reenq() for user DSQs")
> >> introduced the possibility of ops.enqueue() being called multiple times
> >> in a row for the same task without intervening calls to ops.dequeue().
> >> AFAIK this was not possible before that commit.
> > ^^^^^
> > Nit: Do we really need this line in the commit message?
> > Perhaps we can just drop this?
>
> I put it there just in case someone was actually aware of a scenario before
> that commit where we can have multiple ops.enqueue() calls in a row.
I see, thanks!
>
> Regarding removing the line: yeah, I guess it's a bit redundant.
> I'll send a v2.
>
> >
> >> Document this behavior as it may be surprising to some.
> >>
> >> Signed-off-by: Kuba Piecuch <jpiecuch@google.com>
> >> ---
> >> Documentation/scheduler/sched-ext.rst | 5 +++++
> >> 1 file changed, 5 insertions(+)
> >>
> >> diff --git a/Documentation/scheduler/sched-ext.rst b/Documentation/scheduler/sched-ext.rst
> >> index 03d595d178ea..fba09aa1cd4e 100644
> >> --- a/Documentation/scheduler/sched-ext.rst
> >> +++ b/Documentation/scheduler/sched-ext.rst
> >> @@ -339,6 +339,11 @@ The following briefly shows how a waking task is scheduled and executed.
> >> leaves (e.g., when ``ops.dispatch()`` moves it to a terminal DSQ, or
> >> on property change / sleep).
> >>
> >> + Note that ``ops.enqueue()`` can be called multiple times in a row without
> >> + an intervening call to ``ops.dequeue()``. This can happen, for example,
> >> + when a task on a user-created DSQ is re-enqueued using
> >> + ``scx_bpf_dsq_reenq()``. The task stays in BPF custody the entire time.
> >> +
> >
> > Thanks for adding and clarifying this. ^v^
> >
> > Acked-by: Cheng-Yang Chou <yphbchou0911@gmail.com>
> >
>
> Thanks,
> Kuba
--
Cheers,
Cheng-Yang
prev parent reply other threads:[~2026-04-20 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 14:39 [PATCH] sched_ext: Documentation: add note about multiple ops.enqueue() calls in a row Kuba Piecuch
2026-04-20 14:44 ` Andrea Righi
2026-04-20 15:12 ` Cheng-Yang Chou
2026-04-20 15:21 ` Kuba Piecuch
2026-04-20 15:23 ` Cheng-Yang Chou [this message]
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=20260420232245.Gc8ef@cchengyang.duckdns.org \
--to=yphbchou0911@gmail.com \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=chia7712@gmail.com \
--cc=jpiecuch@google.com \
--cc=jserv@ccns.ncku.edu.tw \
--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