From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
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>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [POC][RFC][PATCH] sched: Extended Scheduler Time Slice
Date: Wed, 25 Oct 2023 11:12:47 -0400 [thread overview]
Message-ID: <20231025111247.64d7b653@gandalf.local.home> (raw)
In-Reply-To: <20231025054219.1acaa3dd@gandalf.local.home>
On Wed, 25 Oct 2023 05:42:19 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> I ran a traceeval tool on it (still work in progress, but I can post when
> it's done), and with the following trace, and the writes to trace-marker
> (tracefs_printf)
>
> trace-cmd record -e sched_switch ./extend-sched
>
> It showed that without the extend, each task was preempted while holding
> the lock around 200 times. With the extend, only one task was ever
> preempted while holding the lock, and it only happened once!
And looking at the trace, it was because it was preempted by an RT task.
extend-sched-3349 [007] 3309.320747: print: tracing_mark_write: Have lock!
extend-sched-3349 [007] 3309.320751: sched_switch: extend-sched:3349 [120] R ==> migration/7:68 [0]
migration/7-68 [007] 3309.320754: sched_switch: migration/7:68 [0] S ==> extend-sched:3349 [120]
extend-sched-3349 [007] 3309.320756: print: tracing_mark_write: released lock!
So we know that part of the code works. ;-)
-- Steve
next prev parent reply other threads:[~2023-10-25 15:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 9:42 [POC][RFC][PATCH] sched: Extended Scheduler Time Slice 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
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 [this message]
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=20231025111247.64d7b653@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.