From: Steven Rostedt <rostedt@goodmis.org>
To: Prakash Sangappa <prakash.sangappa@oracle.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"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>,
"kprateek.nayak@amd.com" <kprateek.nayak@amd.com>,
"vineethr@linux.ibm.com" <vineethr@linux.ibm.com>
Subject: Re: [PATCH V5 1/6] Sched: Scheduler time slice extension
Date: Tue, 10 Jun 2025 12:40:42 -0400 [thread overview]
Message-ID: <20250610124042.46b54b51@gandalf.local.home> (raw)
In-Reply-To: <7BA85550-4E33-4C5B-B855-716512D2105E@oracle.com>
On Tue, 10 Jun 2025 16:31:05 +0000
Prakash Sangappa <prakash.sangappa@oracle.com> wrote:
> Ok, adding load also seems to increase the max latency.
Right.
>
> It is up to Peter to decide if scheduler time extension should be restricted to non RT threads.
Peter was against restricting it to just non RT threads because he said it
wouldn't make a difference. He asked for benchmarks that says otherwise.
I'm now supplying the benchmarks that say it does make a difference.
Hopefully Peter will now change his mind.
-- Steve
next prev parent reply other threads:[~2025-06-10 16:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 23:36 [PATCH V5 0/6] Scheduler time slice extension 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
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 [this message]
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=20250610124042.46b54b51@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=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=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;
as well as URLs for NNTP newsgroup(s).