From: Tejun Heo <tj@kernel.org>
To: Andrea Righi <arighi@nvidia.com>
Cc: David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
Jonathan Corbet <corbet@lwn.net>, Emily Soto <emilys@nvidia.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: Documentation: Clarify time slice handling in task lifecycle
Date: Mon, 9 Jun 2025 06:29:13 -1000 [thread overview]
Message-ID: <aEcL2Z42Krv0EEYt@slm.duckdns.org> (raw)
In-Reply-To: <20250609162342.18790-1-arighi@nvidia.com>
On Mon, Jun 09, 2025 at 06:23:42PM +0200, Andrea Righi wrote:
> It is not always obvious how a task's time slice can be refilled, either
> explicitly from ops.dispatch() or automatically by the sched_ext core,
> to skip subsequent ops.enqueue() and ops.dispatch() calls. This
> typically happens when the task is the only one running on a CPU.
>
> To make this behavior easier to understand, update the task lifecycle
> diagram to explicitly document how time slice handling works in such
> cases.
>
> Signed-off-by: Andrea Righi <arighi@nvidia.com>
Applied to sched_ext/for-6.17.
Thanks.
--
tejun
prev parent reply other threads:[~2025-06-09 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 16:23 Andrea Righi
2025-06-09 16:29 ` 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=aEcL2Z42Krv0EEYt@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=corbet@lwn.net \
--cc=emilys@nvidia.com \
--cc=linux-kernel@vger.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®