mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Prakash Sangappa <prakash.sangappa@oracle.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: [PATCH 0/2] Scheduler time extension
Date: Tue, 15 Apr 2025 08:25:36 +0200	[thread overview]
Message-ID: <20250415062536.7tvr17qv@linutronix.de> (raw)
In-Reply-To: <20250414124149.2543d6c0@gandalf.local.home>

On 2025-04-14 12:41:49 [-0400], Steven Rostedt wrote:
> On Fri, 11 Apr 2025 20:54:14 +0000
> Prakash Sangappa <prakash.sangappa@oracle.com> wrote:
> 
> > > On Mar 22, 2025, at 3:14 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
> > > 
> > > On Tue, 18 Mar 2025 16:10:09 +0000
> > > Prakash Sangappa <prakash.sangappa@oracle.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

  parent reply	other threads:[~2025-04-15  6:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-15  0:54 Prakash Sangappa
2025-02-15  0:54 ` [PATCH 1/2] Sched: Scheduler time slice extension Prakash Sangappa
2025-02-15 19:34   ` kernel test robot
2025-02-15 20:16   ` kernel test robot
2025-02-15  0:54 ` [PATCH 2/2] Sched: Add scheduler stat for cpu " Prakash Sangappa
2025-02-17 17:00 ` [PATCH 0/2] Scheduler time extension Steven Rostedt
2025-03-18 16:10   ` Prakash Sangappa
2025-03-22 10:14     ` Steven Rostedt
2025-04-11 20:54       ` Prakash Sangappa
2025-04-14 16:41         ` Steven Rostedt
2025-04-14 17:21           ` Prakash Sangappa
2025-04-15  6:25           ` Sebastian Andrzej Siewior [this message]
2025-04-18 19:38             ` Prakash Sangappa

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=20250415062536.7tvr17qv@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=peterz@infradead.org \
    --cc=prakash.sangappa@oracle.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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®