From: Christian Loehle <christian.loehle@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
kayracizmeci@gmail.com, kprateek.nayak@amd.com,
elif.topuz@arm.com, sh@gentwo.org
Subject: Re: [PATCH v2 3/5] sched/eevdf: Cap protection when current has the shortest slice
Date: Thu, 1 Oct 2026 14:57:48 +0100 [thread overview]
Message-ID: <26c01ef8-03dc-4194-b7dc-68ae12c33560@arm.com> (raw)
In-Reply-To: <20261001135529.GS2009045@noisy.programming.kicks-ass.net>
On 10/1/26 14:55, Peter Zijlstra wrote:
> On Thu, Oct 01, 2026 at 02:40:14PM +0100, Christian Loehle wrote:
>> Changing a task slice preserves its remaining request. With
>> PLACE_REL_DEADLINE, the deadline can therefore extend beyond the new
>> slice after sched_setattr() reduces it.
>
> Or, the new slice is only effective after the current expires.
>
> Is there a reason we care about this? Changelog didn't mention.
Yeah I wasn't sure about this, it does make the tests a little more
hairy as this obviously races...
next prev parent reply other threads:[~2026-10-01 13:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 13:40 [PATCH v2 0/5] sched/eevdf: Keep slice protection boundaries consistent Christian Loehle
2026-10-01 13:40 ` [PATCH v2 1/5] sched/fair: Take slice protection into account when arming HRTICK Christian Loehle
2026-10-01 13:43 ` Peter Zijlstra
2026-10-01 14:01 ` Christian Loehle
2026-10-01 13:40 ` [PATCH v2 2/5] sched/eevdf: Share the slice protection calculation Christian Loehle
2026-10-01 13:40 ` [PATCH v2 3/5] sched/eevdf: Cap protection when current has the shortest slice Christian Loehle
2026-10-01 13:55 ` Peter Zijlstra
2026-10-01 13:57 ` Christian Loehle [this message]
2026-10-01 13:40 ` [PATCH v2 4/5] sched/eevdf: Keep expired protection expired across reweighting Christian Loehle
2026-10-01 16:46 ` Kayra Cizmeci
2026-10-01 21:51 ` Christian Loehle
2026-10-02 14:57 ` Kayra Cizmeci
2026-10-01 13:40 ` [PATCH v2 5/5] sched/eevdf: Update protection after restoring current Christian Loehle
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=26c01ef8-03dc-4194-b7dc-68ae12c33560@arm.com \
--to=christian.loehle@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=elif.topuz@arm.com \
--cc=kayracizmeci@gmail.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sh@gentwo.org \
--cc=vincent.guittot@linaro.org \
/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®