From: Steven Rostedt <rostedt@goodmis.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ankur Arora <ankur.a.arora@oracle.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-mm@kvack.org, x86@kernel.org, akpm@linux-foundation.org,
luto@kernel.org, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, willy@infradead.org, mgorman@suse.de,
jon.grimm@amd.com, bharata@amd.com, raghavendra.kt@amd.com,
boris.ostrovsky@oracle.com, konrad.wilk@oracle.com,
jgross@suse.com, andrew.cooper3@citrix.com,
Joel Fernandes <joel@joelfernandes.org>,
Youssef Esmat <youssefesmat@chromium.org>,
Vineeth Pillai <vineethrp@google.com>,
Suleiman Souhlal <suleiman@google.com>,
Ingo Molnar <mingo@kernel.org>,
Daniel Bristot de Oliveira <bristot@kernel.org>
Subject: Re: [POC][RFC][PATCH] sched: Extended Scheduler Time Slice
Date: Wed, 25 Oct 2023 11:07:09 -0400 [thread overview]
Message-ID: <20231025110709.3e28861a@gandalf.local.home> (raw)
In-Reply-To: <48573a20-19d9-4400-a35e-86bf3dc043ad@efficios.com>
On Wed, 25 Oct 2023 10:53:38 -0400
Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
> I don't have an informed opinion on whether the proposed heuristic is a
> good idea or not, but it should definitely be implemented as an
If you want to get an informed opinion, you can start here: ;-)
Thomas's first reply that had me think about this solution:
https://lore.kernel.org/lkml/87cyyfxd4k.ffs@tglx/
My reply that started it:
https://lore.kernel.org/lkml/20231024103426.4074d319@gandalf.local.home/
> extension to rseq as suggested by Peter. I've even made the whole rseq
> ABI extensible to accommodate those additional use-cases.
>
> In the initial rounds of rseq implementation, I even called rseq "kTLS"
> because I expected it to be extended and eventually become an ABI that
> contains various per-thread fields which are shared between kernel and
> userspace.
>
> So don't let the specific naming of the rseq system call stop you from
> extending it for other purposes when per-thread shared memory between
> kernel and userspace is needed. Setting up various per-thread areas like
> this on thread creation is not free: it requires additional system calls
> on thread creation. It really makes no sense to have more than one.
Thanks for the feedback Mathieu. This may indeed be the interface I am
looking for.
-- Steve
next prev parent reply other threads:[~2023-10-25 15:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 9:42 Steven Rostedt
2023-10-25 9:46 ` Steven Rostedt
2023-10-25 10:29 ` Peter Zijlstra
2023-10-25 12:54 ` Steven Rostedt
2023-10-25 13:55 ` Peter Zijlstra
2023-10-25 14:31 ` Steven Rostedt
2023-10-25 14:53 ` Mathieu Desnoyers
2023-10-25 15:07 ` Steven Rostedt [this message]
2023-10-25 15:42 ` Mathieu Desnoyers
2023-10-25 16:24 ` Mateusz Guzik
2023-10-25 17:17 ` Steven Rostedt
2023-10-25 18:49 ` Mathieu Desnoyers
2023-10-25 19:19 ` Steven Rostedt
2023-10-25 21:56 ` Mathieu Desnoyers
2023-10-26 8:54 ` Peter Zijlstra
2023-10-26 13:40 ` Steven Rostedt
2023-10-26 15:49 ` Steven Rostedt
2023-10-26 16:31 ` Daniel Bristot de Oliveira
2023-10-26 17:26 ` Steven Rostedt
2023-10-26 8:44 ` Peter Zijlstra
2023-10-26 13:16 ` Steven Rostedt
2023-10-30 13:29 ` Peter Zijlstra
2023-10-30 13:52 ` Steven Rostedt
2023-10-26 5:03 ` Ankur Arora
2023-10-25 15:12 ` Steven Rostedt
2023-10-25 15:34 ` Rasmus Villemoes
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=20231025110709.3e28861a@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=ankur.a.arora@oracle.com \
--cc=bharata@amd.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=bristot@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=joel@joelfernandes.org \
--cc=jon.grimm@amd.com \
--cc=juri.lelli@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=raghavendra.kt@amd.com \
--cc=suleiman@google.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vincent.guittot@linaro.org \
--cc=vineethrp@google.com \
--cc=willy@infradead.org \
--cc=x86@kernel.org \
--cc=youssefesmat@chromium.org \
/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