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, peterz@infradead.org,
mathieu.desnoyers@efficios.com, tglx@linutronix.de,
kprateek.nayak@amd.com, vineethr@linux.ibm.com
Subject: Re: [PATCH V5 1/6] Sched: Scheduler time slice extension
Date: Wed, 4 Jun 2025 16:54:33 +0200 [thread overview]
Message-ID: <20250604145433.KCPMF8zm@linutronix.de> (raw)
In-Reply-To: <20250604103106.1465f847@gandalf.local.home>
On 2025-06-04 10:31:06 [-0400], Steven Rostedt wrote:
> On Tue, 3 Jun 2025 23:36:49 +0000
> Prakash Sangappa <prakash.sangappa@oracle.com> wrote:
>
> > @@ -2249,6 +2251,20 @@ static inline bool owner_on_cpu(struct task_struct *owner)
> > unsigned long sched_cpu_util(int cpu);
> > #endif /* CONFIG_SMP */
> >
> > +#ifdef CONFIG_RSEQ
> > +
> > +extern bool rseq_delay_resched(void);
> > +extern void rseq_delay_resched_fini(void);
> > +extern void rseq_delay_resched_tick(void);
> > +
> > +#else
> > +
> > +static inline bool rseq_delay_resched(void) { return false; }
> > +static inline void rseq_delay_resched_fini(void) { }
> > +static inline void rseq_delay_resched_tick(void) { }
> > +
> > +#endif
> > +
>
> Can we add a config to make this optional. I don't want to allow any task
> to have an extended timeslice over RT tasks regardless of how small the
> delay is.
I asked to get RT tasks excluded from this extensions and it is ignored.
Maybe they were benefits mentioned somewhere…
> -- Steve
Sebastian
next prev parent reply other threads:[~2025-06-04 14:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 23:36 [PATCH V5 0/6] " Prakash Sangappa
2025-06-03 23:36 ` [PATCH V5 1/6] Sched: " Prakash Sangappa
2025-06-04 14:31 ` Steven Rostedt
2025-06-04 14:54 ` Sebastian Andrzej Siewior [this message]
2025-06-04 17:29 ` Prakash Sangappa
2025-06-04 19:23 ` Sebastian Andrzej Siewior
2025-06-09 20:55 ` Steven Rostedt
2025-06-09 21:33 ` Steven Rostedt
2025-06-10 16:31 ` Prakash Sangappa
2025-06-10 16:40 ` Steven Rostedt
2025-07-01 0:48 ` Prakash Sangappa
2025-06-09 21:52 ` Steven Rostedt
2025-06-09 22:06 ` Steven Rostedt
2025-06-10 15:40 ` Prakash Sangappa
2025-06-04 17:09 ` Prakash Sangappa
2025-06-03 23:36 ` [PATCH V5 2/6] Sched: Indicate if thread got rescheduled Prakash Sangappa
2025-06-03 23:36 ` [PATCH V5 3/6] Sched: Tunable to specify duration of time slice extension Prakash Sangappa
2025-06-03 23:36 ` [PATCH V5 4/6] Sched: Add scheduler stat for cpu " Prakash Sangappa
2025-06-03 23:36 ` [PATCH V5 5/6] Sched: Add tracepoint for sched " Prakash Sangappa
2025-06-04 14:36 ` Steven Rostedt
2025-06-04 17:10 ` Prakash Sangappa
2025-06-03 23:36 ` [PATCH V5 6/6] Add API to query supported rseq cs flags 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=20250604145433.KCPMF8zm@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=kprateek.nayak@amd.com \
--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 \
--cc=vineethr@linux.ibm.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®