From: Kayra Cizmeci <kayracizmeci@gmail.com>
To: christian.loehle@arm.com
Cc: bsegall@google.com, dietmar.eggemann@arm.com, elif.topuz@arm.com,
juri.lelli@redhat.com, kayracizmeci@gmail.com,
kprateek.nayak@amd.com, linux-kernel@vger.kernel.org,
mgorman@suse.de, mingo@kernel.org, mingo@redhat.com,
peterz@infradead.org, rostedt@goodmis.org, sh@gentwo.org,
vincent.guittot@linaro.org, vschneid@redhat.com
Subject: Re: [PATCH] sched/eevdf: Fix vprot across reweighting
Date: Sun, 11 Oct 2026 13:06:37 +0300 [thread overview]
Message-ID: <20261011100637.60790-1-kayracizmeci@gmail.com> (raw)
In-Reply-To: <ed2c3c89-f556-4fad-b17b-cc08f2eab84a@arm.com>
Hi Christian,
> > Currently in reweighting, while a tasks vruntime changes dead protection
> > could go alive, or alive protection could decrease, increase and go dead.
> >
> > To fix this, implement rel_vprot similar to rel_deadline. Only
> Ah nice find, please allow me to look at this code for a bit if that's
> the best way to implement this, will review then, for now
> Tested-by: Christian Loehle <christian.loehle@arm.com>
Thanks for testing! And yeah, take your time.
> > major difference is that rel_vprot is not dependent on
> > PLACE_REL_DEADLINE, because there are no mechanisms (unlike deadline)
> > that recalculate vprot. So it gets carried.
> >
> > Fixes: 80390ead2080 ("sched/fair: Separate se->vlag from se->vprot")
> > Fixes: bcd74b2ffdd0 ("sched/fair: Only set slice protection at pick time")
> > Link: https://lore.kernel.org/all/20261001164609.244156-1-kayracizmeci@gmail.com/
> > Link: https://lore.kernel.org/all/e4700a93-ebd5-4c7e-88b5-d606437a13c0@arm.com/
> > Co-developed-by: Christian Loehle <christian.loehle@arm.com>
> > Signed-off-by: Christian Loehle <christian.loehle@arm.com>
> FWIW my SOB shouldn't be there anymore.
Right. I'll remove it on v2 aside with Co-developed-by.
Thanks!
Kayra
next prev parent reply other threads:[~2026-10-11 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 11:46 Kayra Cizmeci
2026-10-11 7:13 ` Christian Loehle
2026-10-11 10:06 ` Kayra Cizmeci [this message]
2026-10-12 4:39 ` K Prateek Nayak
2026-10-12 13:40 ` Vincent Guittot
2026-10-12 13:59 ` Kayra Cizmeci
2026-10-12 14:14 ` Vincent Guittot
2026-10-12 15:01 ` Kayra Cizmeci
2026-10-12 19:00 ` Kayra Cizmeci
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=20261011100637.60790-1-kayracizmeci@gmail.com \
--to=kayracizmeci@gmail.com \
--cc=bsegall@google.com \
--cc=christian.loehle@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=elif.topuz@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sh@gentwo.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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®