From: Frederic Weisbecker <frederic@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Anna-Maria Behnsen <anna-maria@linutronix.de>,
Vincent Guittot <vincent.guittot@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"Gautham R. Shenoy" <gautham.shenoy@amd.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>
Subject: Re: Stopping the tick on a fully loaded system
Date: Wed, 26 Jul 2023 12:59:08 +0200 [thread overview]
Message-ID: <ZMD8fP36By1KYgkk@localhost.localdomain> (raw)
In-Reply-To: <CAJZ5v0gJj_xGHcABCDoX2t8aR+9kXr7fvRFF+5KBO5MJz9kFWQ@mail.gmail.com>
Le Tue, Jul 25, 2023 at 04:27:56PM +0200, Rafael J. Wysocki a écrit :
> On Tue, Jul 25, 2023 at 3:07 PM Anna-Maria Behnsen
> I'll let Frederic respond to the above, but from my perspective it all
> just means that the idle governors in use today are not perfect.
>
> However, they will never be perfect, because they only have a little
> time to make a decision, so it's a matter of balancing that with
> precision.
So, even without considering Anna-Maria's patchset, sparing
the next timer lookup if we already know we won't stop it would show
quite a benefit because that lookup involves locking and quite some
overhead walking through all levels.
Thanks.
next prev parent reply other threads:[~2023-07-26 10:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 6:51 Stopping the tick on a fully loaded system Anna-Maria Behnsen
2023-07-20 7:38 ` Vincent Guittot
2023-07-20 13:00 ` Anna-Maria Behnsen
2023-07-20 13:55 ` Vincent Guittot
2023-07-23 21:21 ` Frederic Weisbecker
2023-07-24 8:23 ` Rafael J. Wysocki
2023-07-25 13:07 ` Anna-Maria Behnsen
2023-07-25 14:27 ` Rafael J. Wysocki
2023-07-25 22:28 ` Peter Zijlstra
2023-07-26 15:10 ` Rafael J. Wysocki
2023-07-26 15:53 ` Rafael J. Wysocki
2023-07-26 16:14 ` Peter Zijlstra
2023-07-26 16:49 ` Peter Zijlstra
2023-07-26 21:26 ` Peter Zijlstra
2023-07-27 7:59 ` Peter Zijlstra
2023-07-27 20:10 ` Rafael J. Wysocki
2023-07-26 16:40 ` Anna-Maria Behnsen
2023-07-26 18:30 ` Rafael J. Wysocki
2023-07-26 20:09 ` Peter Zijlstra
2023-07-26 10:59 ` Frederic Weisbecker [this message]
2023-07-26 15:07 ` Rafael J. Wysocki
2023-07-26 10:47 ` Frederic Weisbecker
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=ZMD8fP36By1KYgkk@localhost.localdomain \
--to=frederic@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gautham.shenoy@amd.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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 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.