From: Tejun Heo <tj@kernel.org>
To: zhidao su <soolaugust@gmail.com>
Cc: sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org,
arighi@nvidia.com
Subject: Re: [DISCUSSION] SCX_OPS_ALWAYS_ENQ_IMMED semantics clarification
Date: Wed, 25 Mar 2026 05:55:43 -1000 [thread overview]
Message-ID: <acQFf7iD66CpZGB-@slm.duckdns.org> (raw)
In-Reply-To: <20260325073920.758426-1-suzhidao@xiaomi.com>
Hello,
On Wed, Mar 25, 2026 at 03:39:20PM +0800, zhidao su wrote:
> 1. Is this behavior intentional? Should "all local DSQ enqueues" in the
> flag documentation be understood as "all BPF-path local DSQ enqueues"?
Yes.
> 2. Should the flag documentation be updated to clarify this exception?
Maybe? What the documentation is trying to say is that if the ALWAYS flag is
set it'd behave as if all dsq_insert / dsq_move calls that the BPF scheduler
makes have IMMED set, which is what it does.
Thanks.
--
tejun
prev parent reply other threads:[~2026-03-25 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 7:39 [DISCUSSION] SCX_OPS_ALWAYS_ENQ_IMMED semantics clarification zhidao su
2026-03-25 15:55 ` Tejun Heo [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=acQFf7iD66CpZGB-@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=soolaugust@gmail.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