[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aEcL2Z42Krv0EEYt@slm.duckdns.org>
Date: Mon, 9 Jun 2025 06:29:13 -1000
From: Tejun Heo <tj@...nel.org>
To: Andrea Righi <arighi@...dia.com>
Cc: David Vernet <void@...ifault.com>, Changwoo Min <changwoo@...lia.com>,
Jonathan Corbet <corbet@....net>, Emily Soto <emilys@...dia.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sched_ext: Documentation: Clarify time slice handling in
task lifecycle
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@...dia.com>
Applied to sched_ext/for-6.17.
Thanks.
--
tejun
Powered by blists - more mailing lists