From: Andrea Righi <email@example.com>
To: "Rafael J . Wysocki" <firstname.lastname@example.org>, Pavel Machek <email@example.com>
Cc: Len Brown <firstname.lastname@example.org>,
Andrew Morton <email@example.com>,
Subject: [RFC PATCH 0/2] PM: hibernate: opportunistic memory reclaim
Date: Mon, 1 Jun 2020 18:06:34 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Here is the first attempt to provide an interface that allows user-space
tasks to trigger an opportunistic memory reclaim before hibernating a
Reclaiming memory in advance (e.g., when the system is idle) allows to
reduce the size of the hibernation image and significantly speed up the
time to hibernate and resume.
The typical use case of this feature is to allow high-priority cloud
instances to preempt low-priority instances (e.g., "spot" instances )
by hibernating them.
Opportunistic memory reclaim is very effective to quickly hibernate
instances that allocate a large chunk of memory and remain mostly idle
for the majority of the time, only using a minimum working set.
This topic has been mentioned during the OSPM 2020 conference .
See [RFC PATCH 2/2] for details about the proposed solution.
Feedbacks are welcome.
Andrea Righi (2):
mm: swap: allow partial swapoff with try_to_unuse()
PM: hibernate: introduce opportunistic memory reclaim
Documentation/ABI/testing/sysfs-power | 38 ++++++++++++++
include/linux/swapfile.h | 8 +++
kernel/power/hibernate.c | 94 ++++++++++++++++++++++++++++++++++-
mm/swapfile.c | 45 ++++++++++++++---
4 files changed, 176 insertions(+), 9 deletions(-)
next reply other threads:[~2020-06-01 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 16:06 Andrea Righi [this message]
2020-06-01 16:06 ` [RFC PATCH 1/2] mm: swap: allow partial swapoff with try_to_unuse() Andrea Righi
2020-06-01 16:06 ` [RFC PATCH 2/2] PM: hibernate: introduce opportunistic memory reclaim Andrea Righi
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).