From: Andrea Righi <arighi@nvidia.com>
To: Changwoo Min <changwoo@igalia.com>
Cc: tj@kernel.org, void@manifault.com, kernel-dev@igalia.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] sched_ext: Add a core event and update scx schedulers
Date: Fri, 7 Feb 2025 07:24:08 +0100 [thread overview]
Message-ID: <Z6WnCHiwkvahtdgR@gpd3> (raw)
In-Reply-To: <20250207031338.393045-1-changwoo@igalia.com>
Hi,
On Fri, Feb 07, 2025 at 12:13:36PM +0900, Changwoo Min wrote:
> This patchset introduces a new event, SCX_EV_ENQ_SLICE_DFL, and updates
> two scx schedulers -- scx_qmap and scx_central -- to print out the new
> event.
>
> SCX_EV_ENQ_SLICE_DFL counts how many times the tasks' time slice is set
> to the default value (SCX_SLICE_DFL) by the sched_ext core in the enqueue
> and pick_next paths.
>
> Scheduling a task with SCX_SLICE_DFL unintentionally would be a source
> of latency spikes because SCX_SLICE_DFL is relatively long (20 msec).
> Thus, soaring the SCX_EV_ENQ_SLICE_DFL value would be a sign of BPF
> scheduler bugs, causing latency spikes.
Not directly related to this patch set, but as a general thought: would it
be useful to introduce ops->slice_ms (in sched_ext_ops) to override
SCX_SLICE_DFL?
With that, schedulers that care about latency could set a smaller default
time slice to prevent potential spikes caused by the implicit use of
SCX_SLICE_DFL.
Opinions?
-Andrea
>
> Changwoo Min (2):
> sched_ext: Add an event, SCX_EV_ENQ_SLICE_DFL
> sched_ext: Print an event, SCX_EV_ENQ_SLICE_DFL, in scx_qmap/central
>
> kernel/sched/ext.c | 15 ++++++++++++++-
> tools/sched_ext/scx_central.bpf.c | 2 ++
> tools/sched_ext/scx_qmap.bpf.c | 2 ++
> 3 files changed, 18 insertions(+), 1 deletion(-)
>
> --
> 2.48.1
>
next prev parent reply other threads:[~2025-02-07 6:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 3:13 [PATCH 0/2] sched_ext: Add a core event and update scx schedulers Changwoo Min
2025-02-07 3:13 ` [PATCH 1/2] sched_ext: Add an event, SCX_EV_ENQ_SLICE_DFL Changwoo Min
2025-02-07 6:17 ` Andrea Righi
2025-02-07 6:28 ` Changwoo Min
2025-02-07 3:13 ` [PATCH 2/2] sched_ext: Print an event, SCX_EV_ENQ_SLICE_DFL, in scx_qmap/central Changwoo Min
2025-02-07 6:24 ` Andrea Righi [this message]
2025-02-07 6:49 ` [PATCH 0/2] sched_ext: Add a core event and update scx schedulers Changwoo Min
2025-02-07 6:53 ` Andrea Righi
2025-02-07 21:38 ` Tejun Heo
2025-02-07 21:45 ` Andrea Righi
2025-02-08 3:17 ` Changwoo Min
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=Z6WnCHiwkvahtdgR@gpd3 \
--to=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.