[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250415062536.7tvr17qv@linutronix.de>
Date: Tue, 15 Apr 2025 08:25:36 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Prakash Sangappa <prakash.sangappa@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"peterz@...radead.org" <peterz@...radead.org>,
"mathieu.desnoyers@...icios.com" <mathieu.desnoyers@...icios.com>,
"tglx@...utronix.de" <tglx@...utronix.de>
Subject: Re: [PATCH 0/2] Scheduler time extension
On 2025-04-14 12:41:49 [-0400], Steven Rostedt wrote:
> On Fri, 11 Apr 2025 20:54:14 +0000
> Prakash Sangappa <prakash.sangappa@...cle.com> wrote:
>
> > > On Mar 22, 2025, at 3:14 AM, Steven Rostedt <rostedt@...dmis.org> wrote:
> > >
> > > On Tue, 18 Mar 2025 16:10:09 +0000
> > > Prakash Sangappa <prakash.sangappa@...cle.com> wrote:
> > >
> > >> How do we proceed on this feature?
> > >> Are we leaning towards enabling this feature for SCHED_OTHER only under PREEMPT_LAZY?
> > >
> > > The merge window is about to open and I'm way behind in what needs to go in.
> > >
> > > Let's continue this discussion after rc1 comes out.
> >
> > Can the API be finalized? We have an use case which will benefit from it. So like to see this feature
> > merged.
>
> I'm still not for SCHED_OTHER tasks being allowed to delay RT or deadline
> tasks, even for 5us. But if that's what Peter wants, I'm not going to nack
> it.
I tried to explain in
https://lore.kernel.org/all/20250206150152.-5Fauhtm@linutronix.de
that I don't see how this delay could work for PREEMPT_RT.
> Just keep it configurable so that it can be easily disabled, as I have no
> intentions of using it.
same here.
> -- Steve
Sebastian
Powered by blists - more mailing lists