From: Saravana Kannan <saravanak@google.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>
Cc: Saravana Kannan <saravanak@google.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Marek Vasut <marex@denx.de>,
Bird@google.com, Tim <Tim.Bird@sony.com>,
kernel-team@android.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 5/5] PM: sleep: Spread out async kworker threads during dpm_resume*() phases
Date: Thu, 14 Nov 2024 14:09:19 -0800 [thread overview]
Message-ID: <20241114220921.2529905-6-saravanak@google.com> (raw)
In-Reply-To: <20241114220921.2529905-1-saravanak@google.com>
As of today, the scheduler doesn't spread out all the kworker threads
across all the available CPUs during suspend/resume. This causes
significant resume latency during the dpm_resume*() phases.
System resume latency is a very user-visible event. Reducing the
latency is more important than trying to be energy aware during that
period.
Since there are no userspace processes running during this time and
this is a very short time window, we can simply disable EAS during
resume so that the parallel resume of the devices is spread across all
the CPUs.
On a Pixel 6, averaging over 100 suspend/resume cycles, the new logic
plus disabling EAS for resume yields significant improvements:
+---------------------------+-----------+------------+------------------+
| Phase | Old full sync | New full async | % change |
| | | + EAS disabled | |
+---------------------------+-----------+------------+------------------+
| Total dpm_suspend*() time | 107 ms | 62 ms | -42% |
+---------------------------+-----------+------------+------------------+
| Total dpm_resume*() time | 75 ms | 61 ms | -19% |
+---------------------------+-----------+------------+------------------+
| Sum | 182 ms | 123 ms | -32% |
+---------------------------+-----------+------------+------------------+
Signed-off-by: Saravana Kannan <saravanak@google.com>
---
kernel/power/suspend.c | 16 ++++++++++++++++
kernel/sched/topology.c | 13 +++++++++++++
2 files changed, 29 insertions(+)
diff --git a/kernel/power/suspend.c b/kernel/power/suspend.c
index 09f8397bae15..7304dc39958f 100644
--- a/kernel/power/suspend.c
+++ b/kernel/power/suspend.c
@@ -393,6 +393,12 @@ void __weak arch_suspend_enable_irqs(void)
local_irq_enable();
}
+/*
+ * Intentionally not part of a header file to avoid risk of abuse by other
+ * drivers.
+ */
+void sched_set_energy_aware(unsigned int enable);
+
/**
* suspend_enter - Make the system enter the given sleep state.
* @state: System sleep state to enter.
@@ -468,6 +474,15 @@ static int suspend_enter(suspend_state_t state, bool *wakeup)
Platform_wake:
platform_resume_noirq(state);
+ /*
+ * We do this only for resume instead of suspend and resume for these
+ * reasons:
+ * - Performance is more important than power for resume.
+ * - Power spent entering suspend is more important for suspend. Also,
+ * stangely, disabling EAS was making suspent a few milliseconds
+ * slower in my testing.
+ */
+ sched_set_energy_aware(0);
dpm_resume_noirq(PMSG_RESUME);
Platform_early_resume:
@@ -520,6 +535,7 @@ int suspend_devices_and_enter(suspend_state_t state)
Resume_devices:
suspend_test_start();
dpm_resume_end(PMSG_RESUME);
+ sched_set_energy_aware(1);
suspend_test_finish("resume devices");
trace_suspend_resume(TPS("resume_console"), state, true);
resume_console();
diff --git a/kernel/sched/topology.c b/kernel/sched/topology.c
index 9748a4c8d668..c069c0b17cbf 100644
--- a/kernel/sched/topology.c
+++ b/kernel/sched/topology.c
@@ -284,6 +284,19 @@ void rebuild_sched_domains_energy(void)
mutex_unlock(&sched_energy_mutex);
}
+void sched_set_energy_aware(unsigned int enable)
+{
+ int state;
+
+ if (!sched_is_eas_possible(cpu_active_mask))
+ return;
+
+ sysctl_sched_energy_aware = enable;
+ state = static_branch_unlikely(&sched_energy_present);
+ if (state != sysctl_sched_energy_aware)
+ rebuild_sched_domains_energy();
+}
+
#ifdef CONFIG_PROC_SYSCTL
static int sched_energy_aware_handler(const struct ctl_table *table, int write,
void *buffer, size_t *lenp, loff_t *ppos)
--
2.47.0.338.g60cca15819-goog
next prev parent reply other threads:[~2024-11-14 22:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 22:09 [PATCH v1 0/5] Optimize async device suspend/resume Saravana Kannan
2024-11-14 22:09 ` [PATCH v1 1/5] PM: sleep: Fix runtime PM issue in dpm_resume() Saravana Kannan
2024-11-16 7:43 ` Greg Kroah-Hartman
2024-11-16 21:06 ` Saravana Kannan
2024-12-04 12:53 ` Rafael J. Wysocki
2025-03-11 10:47 ` Rafael J. Wysocki
2025-03-13 1:49 ` Saravana Kannan
2025-03-13 10:58 ` Rafael J. Wysocki
2025-03-14 20:47 ` Pavel Machek
2025-03-14 20:49 ` Saravana Kannan
2024-11-14 22:09 ` [PATCH v1 2/5] PM: sleep: Remove unnecessary mutex lock when waiting on parent Saravana Kannan
2024-12-02 20:11 ` Rafael J. Wysocki
2024-12-02 20:16 ` Rafael J. Wysocki
2024-12-02 20:46 ` Saravana Kannan
2024-12-02 21:14 ` Rafael J. Wysocki
2024-12-02 23:27 ` Saravana Kannan
2024-12-04 12:21 ` Rafael J. Wysocki
2024-11-14 22:09 ` [PATCH v1 3/5] PM: sleep: Add helper functions to loop through superior/subordinate devs Saravana Kannan
2024-11-14 22:09 ` [PATCH v1 4/5] PM: sleep: Do breadth first suspend/resume for async suspend/resume Saravana Kannan
2025-03-11 11:25 ` Geert Uytterhoeven
2024-11-14 22:09 ` Saravana Kannan [this message]
2024-11-15 5:25 ` [PATCH v1 5/5] PM: sleep: Spread out async kworker threads during dpm_resume*() phases Saravana Kannan
2024-11-15 9:25 ` Geert Uytterhoeven
2024-11-15 15:30 ` Vincent Guittot
2024-11-15 16:12 ` Vincent Guittot
2024-11-15 18:33 ` Saravana Kannan
2024-11-17 0:34 ` kernel test robot
2024-11-17 1:17 ` kernel test robot
2024-11-17 13:34 ` kernel test robot
2024-11-18 9:52 ` Christian Loehle
2024-11-18 17:18 ` Saravana Kannan
2024-11-19 4:04 ` [PATCH v1 0/5] Optimize async device suspend/resume Saravana Kannan
2024-11-19 9:51 ` Greg Kroah-Hartman
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=20241114220921.2529905-6-saravanak@google.com \
--to=saravanak@google.com \
--cc=Bird@google.com \
--cc=Tim.Bird@sony.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@android.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marex@denx.de \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--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 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®